This Vbs script will search the domain specified and list the machines name, DNS host name, and operating system version and service pack level to Excel
Note: Be sure to change Your_DC_Name to the DC that you want to query on the line that reads:
strLDAPQuery = "LDAP://DC=Your_DC_Name,DC=Com"
Vbs Script:
On Error GoTo 0
Const ADS_SCOPE_SUBTREE = 2
Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")
objConnection.Provider = "ADSDSOObject"
objConnection.Open "Active Directory Provider"
strScriptPath = replace(wscript.scriptfullname,wscript.scriptname,"")
Set objXL = wscript.CreateObject("Excel.Application")
objXL.Visible = True
objXL.WorkBooks.Add
outputFile = strScriptPath & "Computer Accounts.xls"
icount = 2
Set objCOmmand.ActiveConnection = objConnection
objCommand.CommandText = "Select Name, dnsHostName, operatingSystem, operatingSystemServicePack from '" _
& strLDAPQuery & "' Where objectClass='computer'"
objCommand.Properties("Page Size") = 1000
objCommand.Properties("Searchscope") = ADS_SCOPE_SUBTREE
Set objRecordSet = objCommand.Execute
objRecordSet.MoveFirst
objXL.ActiveSheet.Range("A1:D1").ColumnWidth = 20
ObjXL.ActiveSheet.Cells(1,1).Value = "Machine Name"
ObjXL.ActiveSheet.Cells(1,2).Value = "Dns Host Name"
ObjXL.ActiveSheet.Cells(1,3).Value = "Operating System Version"
ObjXL.ActiveSheet.Cells(1,4).Value = "Service Pack"
objXL.Range("A1:E1").Select
objXL.Selection.Font.Bold = True
objXL.Selection.Interior.ColorIndex = 1
objXL.Selection.Interior.Pattern = 1 'xlSolid
objXL.Selection.Font.ColorIndex = 2
Do Until objRecordSet.EOF
ObjXL.ActiveSheet.Cells(icount,1).Value = objRecordSet.Fields("Name").Value
ObjXL.ActiveSheet.Cells(icount,2).Value = objRecordSet.Fields("DnsHostName").Value
ObjXL.ActiveSheet.Cells(icount,3).Value = objRecordSet.Fields("OperatingSystem").Value
ObjXL.ActiveSheet.Cells(icount,4).Value = objRecordSet.Fields("operatingSystemServicePack").Value
icount = icount + 1
objRecordSet.MoveNext
Loop
The CCR (Client Configuration Request) Process is one of the processes in which an SMS client machine is installed to a site server. This article will provide you with a high level overview of the CCR process.
The process first begins with the SMS site server discovering the potential client machine and when it locates it the machine name and additional information about the client is written to the CCR log file. Next the SMS Client Configuration Manager (CCM) attempts to connect to the machines Admin$ share on the machine.
If the connection is successful CCM then attempts to connect to the client machines registry where it gathers additional information about the machine that is then written to the CCM log (Ccm.Log) file connection to the Inter-Process Communication (IPC$) share.
At this point if all the processes connect as expected core SMS component files are copied to the machine. The Ccmsetup.exe and MobileClient.tcf files are first copied to the %WinDir%\System32\CcmSetup folder on the client from the site servers SMS\Bin\I386\ folder. Then the CCM process attempts to verify that the CcmSetup service has successfully started on the machine and disconnects if the service has started as expected.
Then the completed client machines CCR file is placed in the SMS\Inboxes\CcrRetry.Box inbox to be verified that the installation has been successful. After this process has been verified a second verification is launched where the Agent Host file on the client is interrogated to ensure that is it running and then the original CCR file is deleted.
It is important to note here that if any failures or errors are detected by the CCM process the originally created CCR file for the client machine is renamed to the client machines NetBIOS name as ComputerName.Ccr and moved to the SMS\Inboxes\CcrRetry.Box directory. After the fie is placed in the CcrRetry.Box the CCM process attempts to process the CCR file to resolve any detected errors every hour (Sixty Minutes) for one week (Seven days) before the CCR file is deleted and the information’s written to the Ccm.Log file on the site server.
The ComputerName.Ccr file is a text based file and you can view the file using notepad or any other text based editor and see the number of processing attempts that have been attempted. A typical ComputerName.Ccr file will look like the following:
[NT Client Configuration Request]
Machine Name=Computer001
Domain=XXX
IP Address 1=192.168.100.200
Initial Request Date=02/20/2007 10:35:19
[IP Address ]
[Resource Names ]
Resource Names 1=Computer001
[Request Processing]
Latest Processing Attempt=02/21/2007 09:37:28
Last Error Code=5
Number of Processing Attempts=99
Error Event Created=02/21/2007 10:49:35
[IDENT]
TYPE=Client Config Request File
As you will notice in the example above you can look at the Last error code in the CCR file to gather information that will allow you to troubleshoot the SMS client installation process. The error 5 in this case is an access denied error and tells you that the required permissions for the SMS client install process to compete are not met.
This rather simple SQL query will allow you to gather the manufacturer, model and Processor Count for a specified machine.
SQL Query:
Select
Name0 'Machine Name',
Manufacturer00 Manufacturer,
Model0 Model,
NumberOfProcessors00 Processors
From Computer_System_Data
Where Name0 = 'MachineName'
Domain trees are not new to Windows Server 2003 because it was introduced to the Intel world with Windows 2000 server in 1996. It has however matured with the release of Windows 2003 server back in 2003 when it was released.
A Tree host or holds domains in a transitive trust hierarchy link where the domains are identified by their Domain Name System (DNS) names. When you have multiple domains they share the schema and the global catalog for the domain. As an example suppose you have domains in your infrastructure with the prefix: MyDomain.Com. In this situation all the domains belong to the MyDomain Domain Tree.
The first domain that you create when you bring up a Domain Controller (DC) for Active Directory (AD) is called the Root Domain and it holds the schema data for the domain Tree. A tree structure is created when you add child domains for Decentralized administration and management or to control or throttle your AD replication.
If you have a single domain that domain will contain a complete AD partition for all of the objects such as users and computers and is known as a complete domain tree. When additional domains or child domains are added to the tree AD partitions are replicated to the DC’s within the domain.
Salt or to be more precise, editable salt or table salt is a mineral in rock form. Since humans began using salt to improve the taste of food probably after watching animals such as deer lick or eat it has been until the early 1900’s rare and hard to come by. The Romans were said to have used it in part to pay their soldiers with and in China salt was even taxed.
The act of throwing a pinch of salt over your left shoulder after spilling some has its origins in the fact that since before modern times it was so hard to get it was considered bad luck or as Tarzan would say “Bad JuJu” to spill any. Therefore if you should happen to spill some you throw a pinch of it over your left shoulder to combat the bad luck.
This was also echoed by Leonardo da Vinci in his 15th century mural the last supper where Judas is depicted as spilling salt on the table before he denied Jesus. In the mural Judas is seated on the left of Jesus or as superstition would hold the evil or bad side. The reasoning behind this therefore goes that if you spill salt to break the bad luck you throw a pinch of it over your left or evil shoulder.
There are several ways in which you can find information on the various PowerShell Cmdlets that are available to you. There is the documentation that ships with PowerShell as well as the Microsoft PowerShell home page at:
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx
There are also ways from within the PowerShell console that you can get bare bones information on the Cmdlet(s) you want more info on as well. If you type into the PowerShell console using the following syntax you can get this bare bones information:
Get-Help CmdletName
Note: You can also use the Get-Help alias of Help as well as shown in the examples to follow.
For example if you want some basic information on the Get-Variable Cmdlet simply type in: Help Get-Variable.
If you want only examples of how to use a Cmdlet such as the Get-Variable Cmdlet type in: Help Get-Variable –Examples.
You can also get more detailed help on a specific Cmdlet by entering the following: Help CmdletName –Detailed. You can take this one step further by issuing the following that will provide you with the full help for the specified Cmdlet Help CmdletName –Full.
When you use the –Detailed or –Full command switches you will see the following displayed at the bottom of a buffer screen: -- More – To move through the screens press the space bar to continue through them one at a time as you would do if you issued the MS-DOS command | More.
Tip: If you want to have the results sent to a file rather than to the screen you can enter the following: Help Get-Variable –Full > C:\CmdletHelp.Txt or you can simply copy and paste the screen text from the PowerShell console. You can accomplish this by clicking the PowerShell icon on the top left corner of the console and from the menu select “Edit” and then choose “Select All” and then click the PowerShell icon again and select “Copy’ and then you can paste the text into your favorite editor.
The Microsoft Office SharePoint Server (MOSS) 2007 Management Pack (MP) for MOM 2005 was released the first of the year and provides you with the following features among others:
Note: I was surprised that this MOM 2005 MP did not include any reports so when you import this MP select “Import Management Packs Only”.
Microsoft Office SharePoint Server 2007 MP for MOM 2005:
http://www.microsoft.com/downloads/details.aspx?FamilyID=247c06ba-c599-4b22-b2d3-7bf88c4d7811&displaylang=en
The Fundamental Computer Investigation Guide for Windows available from Microsoft will provide you with information on how to investigate and then handle any suspicious or improper use of your organizations computers and network. This paper was developed by Microsoft’s security experts and customers to provide you with the information and resources you may need in order to pursue any criminal or civil lawsuits.
This solution accelerator will give you the tools necessary to conduct investigations in your organization as well as provide you with an investigation model and best practices for conducting your investigations. It will also give you information on how to perform your computer and network investigations via a fictions model and includes worksheets and contact information (US Only) for computer related crimes.
Fundamental Computer Investigation Guide for Windows Download:
http://go.microsoft.com/fwlink/?linkid=80345
Since Microsoft has release Service Pack 2 for SQL Server 2005 there are also updated Books on Line (BOL) as well as a new feature pack and updated samples and databases. There are also updates that will allow you to integrate and use Microsoft Office 2007 and SharePoint technologies as well.
Updated SQL Server 2005 Books Online
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
SQL Server 2005 Feature Pack
http://www.microsoft.com/downloads/details.aspx?familyid=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en
Updated Samples and Sample Databases
http://www.microsoft.com/downloads/details.aspx?familyid=e719ecf7-9f46-4312-af89-6ad8702e4e6e&displaylang=en
SQL Server 2005 Data Mining Add-ins for Microsoft Office 2007
http://go.microsoft.com/fwlink/?LinkId=82754
SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies
http://go.microsoft.com/fwlink/?LinkId=82753
To download Service Pack 2 for SQL server 2005 standard, advanced and workgroup editions see the link below:
SQL Server 2005 SP2
http://go.microsoft.com/fwlink/?LinkId=82758
This HTA script will take a machine name from an input box and write some basic machine information to the active window including the machine name, the machines primary owner name, the machines manufacturer and model.
HTA Script:
<Html>
<Head>
<HTA:Application
Caption = Yes
Border = Thick
ShowInTaskBar = No
MaximizeButton = Yes
MinimizeButton = Yes>
<Script Language = VBScript>
sub Window_OnLoad
Set objDocument = self.Document
objDocument.open
objDocument.writeln "Basic Machine Information: " & "<br>"
objDocument.writeln "<br>"
strComputer = InputBox ("Enter Machine Name")
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\Root\Cimv2")
Set colItems = objWMIService.ExecQuery ("Select * From Win32_ComputerSystem")
For Each objItem in colItems
objDocument.writeln("Machine Name: " & objItem.Name)
objDocument.writeln("PrimaryOwnerName: " & objItem.PrimaryOwnerName)
objDocument.writeln("Manufacturer: " & objItem.Manufacturer)
objDocument.writeln("Model: " & objItem.Model)
Next
End Sub
</script>
</Head>
<Body>
</Body>
</Html>
This by request script will allow you to enter an NT or Active Directory (AD) Domain Name and User Name and will change the corresponding user’s domain Password.
VBS Script:
strDomain = InputBox ("Enter Domain Name")
strUser = InputBox ("Enter User Name")
strPassword = InputBox ("Enter Password")
On Error Resume Next
Set objUser = GetObject("WinNT://" & strDomain & "/" & strUser & ",User")
objUser.SetPassword strPassword
objUser.SetInfo
If Err.Number <> 0 Then
MsgBox "Error: An Incorrect Domain Or User Name Was Entered!"
Err.Clear
Else
MsgBox "The Password Has Been Changed For " & UCase(strDomain) & "\" & UCase(strUser)
End If
The USA Test
http://www.lizardpoint.com/fun/geoquiz/usaquiz.html
Complete List Of Test
http://www.lizardpoint.com/fun/geoquiz
I ran across this page while I was doing some research the other day and found myself going back to it a few times throughout the day out of curiosity. My curiosity cost me a few backs but as the filthy rich say “It’s only money”.
My favorite purchase was the SQL Query T-Shirt that reads: SELECT * FROM users WHERE clue > 0 on the top line and on the bottom mine it reads: 0 rows returned. There is literally something for everyone in IT here and even a discount bargain bin for those looking for reduced price or close out items.
This Vbs script will prompt you for a domain name and then list all of the members of the “SMS Reporting Users” group by login name and full name in an excel spreadsheet.
Note: The script can also be modified to list the members of a group other than the SMS Reporting Users by changing the strGroup to the group that you want to enumerate. For example if you want to list all of the members of the SMS Admins group add the value “SMS Admins” in place of the “SMS Reporting Users”.
strGroup = "SMS Reporting Users"
Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True
objExcel.Workbooks.Add
intRow = 2
objExcel.Cells(1, 1).Value = "Domain Name"
objExcel.Cells(1, 2).Value = "Group Name"
objExcel.Cells(1, 3).Value = "Login Name"
objExcel.Cells(1, 4).Value = "Full Name"
Set Group = GetObject("WinNT://" & strDomain & "/" & strGroup & ",Group")
For Each Member in Group.Members
objExcel.Cells(intRow, 1).Value = UCase(strDomain)
objExcel.Cells(intRow, 2).Value = strGroup
objExcel.Cells(intRow, 3).Value = Member.Name
objExcel.Cells(intRow, 4).Value = Member.FullName
objExcel.Range("A1:D1").Select
objExcel.Selection.Interior.ColorIndex = 19
objExcel.Selection.Font.ColorIndex = 11
objExcel.Selection.Font.Bold = True
objExcel.Cells.EntireColumn.AutoFit
Wscript.Echo "Done"
The freely downloadable SMS 2003 custom reports documentation (SMS2003CustomReports.Chm) will provide you with information and techniques necessary to use SMS 2003 SQL views to create custom SMS reports. It also provides you with an overview of the WMI and SQL view schemas as well as shows you typical SQL statements that are used for SMS 2003 reports.
It is a great resource for those of you who want to begin creating customized SMS web reports or to provide you with additional information if you are already an old pro like Ron Crumbaker who is also not your ordinary Camaro owner.
The document also provides you with an overview of the built-in reports as well as provides you with information about the SMS views and their categories.
SMS 2003 Custom Reports Download
http://www.microsoft.com/downloads/details.aspx?familyid=9d6f3a2f-52c6-4574-b8b0-16846da2fc55&displaylang=en
This SQL query will return the last user name and IP address from a specified machine.
SQL Script:
SYS.Name0 'Machine Name',
SYS.User_Name0 'User Name',
IP.Ip_Addresses0 'IP Address'
From