Tuesday, June 21, 2005

WMI Scripting with MSH

If MSH is to become the next best scripting thing, then its got to enable a number of different scenarios. One use of MSH is to do WMI scripting - using MSH get access to WMI objects, properties and methods.

I started by looking at the [truly amazing!] TechNet script centre, which has a large number of existing WMI scripts. As it turns out, it's surprisingly easy to write WMI scripts, once you master the differences between VBscript and Monad!

The first script I tackled is at: http://www.microsoft.com/technet/scriptcenter/scripts/desktop/logon/dmlgv b02.mspx

strComputer = "atl-ws-o1"
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colComputer = objWMIService.ExecQuery _ ("Select * from Win32_ComputerSystem")
For Each objComputer in colComputer
Wscript.Echo "Logged-on user: " & objComputer.UserName

In MSH this is just 3 lines:

$strComputer = "kapoho61"
$colComputer = get-wmiObject win32_computersystem -comp $strComputer
foreach ($comp in $colcomputer){"Logged-on user: " + $comp.username}

8 lines into 3 - not bad!

My second attempt was to reproduce http://www.microsoft.com/technet/scriptcenter/scripts/desktop/logon/dmlgv b01.mspx

'-------------- strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_LogonSession")
For Each objItem in colItems
Wscript.Echo "Authentication Package: " & objItem.AuthenticationPackage
Wscript.Echo "Logon ID: " & objItem.LogonId
Wscript.Echo "Logon Type: " & objItem.LogonType
Wscript.Echo "Start Time: " & objItem.StartTime


$strComputer = "kapoho61"
$colComputer = get-wmiObject win32_LogonSession -comp $strComputer
foreach ($comp in $colcomputer) {"Authentication Package: " + comp.AuthencationPackage
"Login ID: " + $comp.LogonId
"Login Type: " + =$comp.LogonType
"Start Time: " + $comp.StartTime}

11 lines into 6.

All in all - this WMI scripting stuff looks to be easy in MSH. What would be really cool now is for someone to create a msh-scriptomatic.hta (to mimic the scroptomatic.hta currently available). I just wish I was better at HTAs.

MSH Rocks!!

(submitted by email - apologies for layout!)


Mark-Allen said...


Let's match oranges to oranges, ok?

The WSH code is easier to read and to modify by someone else in the future. It has what I call "readability". Ok, given that I know the code base.

But your MSH code is multi-lined, which is harder to read and harder to debug by someone who is not familar with the code.

It appears the basis of your post is "less lines is better", which is what I call "old style programming". Good programmers moved out of this decades ago and into "readable code" as they learned better.

Ok, this is a small comment from an old programmer of 35-years of coding. But it does apply to today's world like it did years ago: write code for the person who has to fix/change/improve it later.

Just my 2 centimes. And BTW, I'm learning MSH now.

Love your blog. Keep it up.


Richard Anthony Hein said...

I think the MSH stuff is easier to read. YMMV.

shimrod said...


As an experienced shell programmer I too find the msh script example much easier to read. The wsh example is very 'busy'. I prefer brevity and logical naming.

Kelly Jones said...

I've got to say the msh script is *much* easier to read. The WSH code is painful to look at. But maybe I'm biased coming from the world of Perl and unix shells.