Enumerate the OS version and Service Pack

This VBScript utilizes WMI to discover the Service Pack and OS version. We utilized the Scriptomatic from the Microsoft Scripting Center(http://www.microsoft.com/technet/scriptcenter/default.mspx) to discover the correct object properties to script for.
First we issue the command On Error Resume Next to tell the script to continue executing even if an error is detected.
We then tell the script which computer to script against. This is done by setting a variable strComputer to “.”. this tells the script to execute on the local computer. By replacing the period with the name or IP address of a different computer, the script will execute against that computer. This asums the you have local administrative rights on that computer.
Line 3 will connect to the client.
Line 4 will gather a collection or all objects in the Win32_OperatingSystem on the target computer.
He For..Next loop will return the service pack and OS version.

On Error Resume Next

strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set colItems = objWMIService.ExecQuery("Select * from Win32_OperatingSystem",,48)

For Each objItem in colItems

Wscript.Echo "ServicePackMajorVersion: " & _
objItem.ServicePackMajorVersion

Wscript.Echo "ServicePackMinorVersion: " & _
objItem.ServicePackMinorVersion

Wscript.Echo "Version: " & objItem.Version

Next

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog