WMI – BAFM

Displaying Windows Architecture with bginfo

June 18, 2010June 21, 2013 Christian Leave a comment

On all our servers in the basement, we do have bginfo installed, in order to quickly get certain information. Now as I was struggling with a big Service Pack roll out, I looked into making bginfo also display the OS architecture. But apparently it isn’t that easy … At least bginfo doesn’t provide it by default.

After (yet another hour in front of Google), I finally found what I was looking for. At first I didn’t limit the query on a specific CPU, but that turned out to be shitty (x32 being displayed twice, once for each CPU). But after limiting it to DeviceID=’CPU0′ it works like a charm 😉

VBscript: Query remote OS and SP info (continued)

February 15, 2010August 8, 2014 Christian Leave a comment

After some more crunching on my VBscript, I think I finally have a working script that runs through a csv-list I point it to and walk onto each system (by ip-address only sadly) and query the os and the Service Pack that is installed. The CSV may look like this:

Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority
epimetheus;10.0.0.2;VMware guest;File-Server
hades;10.0.0.1;VMware guest;Core-Router

Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority

epimetheus;10.0.0.2;VMware guest;File-Server

hades;10.0.0.1;VMware guest;Core-Router

After saving that one, and running a cscript //NoLogo win_sp_level.vbs you should find a completed list like this:

Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority
epimetheus;10.0.0.2;VMware guest;File-Server;Windows Server 2003 Standard x64 Edition; SP1;;
hades;10.0.0.1;VMware guest;Core-Router;Windows Server 2003 Enterprise Edition; SP0;;

Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority

epimetheus;10.0.0.2;VMware guest;File-Server;Windows Server 2003 Standard x64 Edition; SP1;;

hades;10.0.0.1;VMware guest;Core-Router;Windows Server 2003 Enterprise Edition; SP0;;

The final script looks like this:

On Error Resume Next

Set objFSO = CreateObject("Scripting.FileSystemOBject")

If objFSO.FileExists("Rollout_SP2.csv") = 0 Then
  CleanUp()
  Wscript.Quit
End If

Set CSVin = objFSO.OpenTextFile("Rollout_SP2.csv", 1)
CSVin_read = CSVin.ReadLine

Set objFile = objFSO.CreateTextFile("Rollout_SP2_result.csv")
Set objFile = nothing
Set CSVout = objFSO.OpenTextFile("Rollout_SP2_result.csv", 8)
CSVout.WriteLine("Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority")

Do While CSVin.AtEndofStream &lt;&gt; True

  Dim os, servicepack
  Dim user, password
  
  os = nothing
  servicepack = nothing
  user = vars(1) &amp; "chrischie"
  password = "hah-this-password-is-easy"
  
  current_line = CSVin.ReadLine
  vars = Split(current_line, ";")
  
  Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set objSWbemServices = objSWbemLocator.ConnectServer _
    (vars(1), "rootcimv2", user, password, "MS_409",, 128)

  objSWbemServices.Security_.ImpersonationLevel = 3

  Set colOperatingSystems = objSWbemServices.ExecQuery _
    ("Select * from Win32_OperatingSystem")

  ' The set returns an Err.Number of 91 on success
  ' Don't ask me why though.
  If Err.Number &lt;&gt; 91 Then
    CSVout.WriteLine(vars(0) &amp; ";" &amp; vars(1) &amp; ";" &amp; vars(2) &amp; ";" &amp; vars(3) &amp; ";NA;SP?;;")
  Else
    For Each objOperatingSystem in colOperatingSystems
      os = objOperatingSystem.Caption
      servicepack = objOperatingSystem.ServicePackMajorVersion
    Next
    CSVout.WriteLine(vars(0) &amp; ";" &amp; vars(1) &amp; ";" &amp; vars(2) &amp; ";" &amp; vars(3) _
	                 &amp; ";" &amp; os  &amp; "; SP" &amp; servicepack &amp; ";;")
  End If
Loop

On Error Resume Next

Set objFSO = CreateObject("Scripting.FileSystemOBject")

If objFSO.FileExists("Rollout_SP2.csv") = 0 Then

CleanUp()

Wscript.Quit

End If

Set CSVin = objFSO.OpenTextFile("Rollout_SP2.csv", 1)

CSVin_read = CSVin.ReadLine

Set objFile = objFSO.CreateTextFile("Rollout_SP2_result.csv")

Set objFile = nothing

Set CSVout = objFSO.OpenTextFile("Rollout_SP2_result.csv", 8)

CSVout.WriteLine("Hostname;IP;Model;Description;OS;Service-Pack;BL;Priority")

Do While CSVin.AtEndofStream <> True

Dim os, servicepack

Dim user, password

os = nothing

servicepack = nothing

user = vars(1) & "chrischie"

password = "hah-this-password-is-easy"

current_line = CSVin.ReadLine

vars = Split(current_line, ";")

Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")

Set objSWbemServices = objSWbemLocator.ConnectServer _

(vars(1), "rootcimv2", user, password, "MS_409",, 128)

objSWbemServices.Security_.ImpersonationLevel = 3

Set colOperatingSystems = objSWbemServices.ExecQuery _

("Select * from Win32_OperatingSystem")

' The set returns an Err.Number of 91 on success

' Don't ask me why though.

If Err.Number <> 91 Then

CSVout.WriteLine(vars(0) & ";" & vars(1) & ";" & vars(2) & ";" & vars(3) & ";NA;SP?;;")

Else

For Each objOperatingSystem in colOperatingSystems

os = objOperatingSystem.Caption

servicepack = objOperatingSystem.ServicePackMajorVersion

CSVout.WriteLine(vars(0) & ";" & vars(1) & ";" & vars(2) & ";" & vars(3) _

& ";" & os & "; SP" & servicepack & ";;")

End If

Loop

~~The only thing I still need to improve is the error handling (as in notify when a system is being skipped due to RPC being unavailable).~~

VBscript: Query remote OS and SP info

February 12, 2010August 8, 2014 Christian 1 Comment

As I wrote on Thursday, I am battling with Windows Server 2003. Now I got a list out of our change management database, which sadly ain’t that accurate. So in order to get reliable information about the target systems (in order to do some accurate planning), I ended up writing a small vbscript which simply takes the hostname on the command line (cscript //NoLogo win_sp_level.vbs 10.0.0.5) and returns a csv-like element.

We may have to tune the script a bit more for our use, but it should show the basic functions I need.

Dim hostname, os, servicepack

hostname = WScript.Arguments.Item(0)

strComputer = hostname
Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
Set objSWbemServices = objSWbemLocator.ConnectServer _
   (strComputer, "rootcimv2", hostname &amp;amp; "chrischie", "hah-this-password-is-easy")
objSWbemServices.Security_.ImpersonationLevel = 3

Set colOperatingSystems = objSWbemServices.ExecQuery _
   ("Select * from Win32_OperatingSystem")

For Each objOperatingSystem in colOperatingSystems
   os = objOperatingSystem.Caption
   servicepack = objOperatingSystem.ServicePackMajorVersion
Next

Wscript.Echo hostname &amp; ";" &amp; os &amp; "; SP" &amp; servicepack &amp; ";"

Dim hostname, os, servicepack

hostname = WScript.Arguments.Item(0)

strComputer = hostname

Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")

Set objSWbemServices = objSWbemLocator.ConnectServer _

(strComputer, "rootcimv2", hostname &amp; "chrischie", "hah-this-password-is-easy")

objSWbemServices.Security_.ImpersonationLevel = 3

Set colOperatingSystems = objSWbemServices.ExecQuery _

("Select * from Win32_OperatingSystem")

For Each objOperatingSystem in colOperatingSystems

os = objOperatingSystem.Caption

servicepack = objOperatingSystem.ServicePackMajorVersion

Wscript.Echo hostname & ";" & os & "; SP" & servicepack & ";"

VBscript & Active Directory and printers ? (continued)

October 25, 2007August 16, 2014 Christian 1 Comment

As I posted earlier, I tried working around some limitations in Microsoft’s Active Directory by teaching the script some intelligence.

But, since we recently started using Thin Clients, all the stuff I did with the fancy vbs was just a waste-of-time. Turns out, Windows XP Embedded doesn’t work quite the same as a “normal” Windows XP (that’s where I tested the script on), and it simply dies when running the WMI Query. Bollocks.

So I switched back, utilizing a shortcut in Startup, but pointing to the shortened vbs (see below) instead of the ugly batch file someone wrote.

Set WshNetwork = CreateObject("WScript.Network")

WshNetwork.AddWindowsPrinterConnection "\nas.barfoo.orgKyocera FS-9100DN KX"
' Set the default printer to something useful
WshNetwork.SetDefaultPrinter "\nas.barfoo.orgKyocera FS-9120DN KX"

Set WshNetwork = CreateObject("WScript.Network")

WshNetwork.AddWindowsPrinterConnection "\nas.barfoo.orgKyocera FS-9100DN KX"

' Set the default printer to something useful

WshNetwork.SetDefaultPrinter "\nas.barfoo.orgKyocera FS-9120DN KX"

But even that doesn’t work all the time, I still have to figure out why.

VBscript & Active Directory and printers ?

October 13, 2007June 21, 2013 Christian 1 Comment

Well, since our current solution for mapping printers is an ugly batch file, which needs to be put into Startup, I today poked at doing it in VBscript (I know, but it’s less ugly than the batch script, trust me).

As some of you know, printers are only applicable to users (as in you can’t put a startup script onto an OU, which is going to map the printers). So as we store users and the computes in different OU’s in our Active Directory (we do have about 15.000 students), I can’t apply the printer.vbs to the users OU directly either, unless I implement some intelligence into the script itself.

And that’s basically what I did. Since different pools at the university have different DNS suffixes (like pools.rz.barfoo.org, that our or pools.fmz.barfoo.org) and we only want them students to have our printers when they logon at our pool, I just made the script to get the DNS DomainName of the current active interface and compare it against a given pattern.

&#039; The problem is, if you apply something like this the users get the printers regardless whether they
&#039; are at our location or a different one. So we either need to look up the current AD object (this computer),
&#039; or just compare our current DNS suffix/DomainName against a known pattern.

&#039; Now, lets get the DomainName from the WMI-Interface
strComputer = &quot;.&quot;
Set objWMIService = GetObject(&quot;winmgmts:{impersonationLevel=impersonate}!\.rootcimv2&quot;)
Set colNicConfigs = objWMIService.ExecQuery (&quot;SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True&quot;)

For Each objNicConfig In colNicConfigs
strDNSDomain = objNicConfig.DNSDomain
Next

&#039; Apply some regexp foo, to see if we&#039;re at the computing center or not!
Dim regexp
Set regexp = New RegExp
regexp.Pattern = &quot;pools.rz.barfoo.org&quot;

if regexp.Test(strDNSDomain) Then
&#039;If so, then lets just connect the printers we need!
Set WshNetwork = CreateObject(&quot;WScript.Network&quot;)

WshNetwork.AddWindowsPrinterConnection &quot;\nas.barfoo.orgKyocera Mita FS-9100DN KX&quot;

&#039; Set the default printer to something useful
WshNetwork.SetDefaultPrinter &quot;\nas.barfoo.orgKyocera Mita FS-9100DN KX&quot;
End If

' The problem is, if you apply something like this the users get the printers regardless whether they

' are at our location or a different one. So we either need to look up the current AD object (this computer),

' or just compare our current DNS suffix/DomainName against a known pattern.

' Now, lets get the DomainName from the WMI-Interface

strComputer = "."

Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\.rootcimv2")

Set colNicConfigs = objWMIService.ExecQuery ("SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True")

For Each objNicConfig In colNicConfigs

strDNSDomain = objNicConfig.DNSDomain

' Apply some regexp foo, to see if we're at the computing center or not!

Dim regexp

Set regexp = New RegExp

regexp.Pattern = "pools.rz.barfoo.org"

if regexp.Test(strDNSDomain) Then

'If so, then lets just connect the printers we need!

Set WshNetwork = CreateObject("WScript.Network")

WshNetwork.AddWindowsPrinterConnection "\nas.barfoo.orgKyocera Mita FS-9100DN KX"

' Set the default printer to something useful

WshNetwork.SetDefaultPrinter "\nas.barfoo.orgKyocera Mita FS-9100DN KX"

End If