MS Virtual Server 2005 Guest and SIM 4.2

[NJK-Work]

Hello,

I am unable to get SIM to recognize a Virtual Server 2005 guest OS (Windows 2003 SP1) on SIM 4.2. With VMWare, all I had to do is setup a WBEM user account and password with rights to the guest OS in SIM and it saw it as a VMWare Guest. But with VS 2005, is just sees it as unknown.

Has anyone done this already? Are there any tricks to getting this working?

Thanks
Nelson

[David Claypool · Accepted solution]

No tricks. First make sure the WMI Mapper is installed and running. Then make sure that you can communicate WMI between your HP SIM system and the guest. I typically download 'Scriptomatic' from the MS web site and modify the resulting script to reference the remote instance. Any chance that there are underscore ("_") characters in the host names? That will definitely break the WMI Mapper.

[NJK-Work]

Hi David,

Thanks for the info.

Maybe I am confusing myself, but I thought the WMIMapper was only for UNIX boxes (or something like that). I need that for Windows boxes as well?

THanks
Nelson

[NJK-Work]

I double-checked, and I guess I do already have the Pegasus WMI Mapper installed on my SIM box. I do not have any underscores in the name.

From the SIM server, I can connect to the VM using Script-o-matic, but I am not sure exactly what script I should be running to verify it. Any old script will do I would assume...I used a processor script and it was able to pull all data from the VM regarding its "virtual processor".

Any other suggestions?
Thanks
Nelson

[NJK-Work]

Got it!

I had to enable WBEM at the global level (but not apply a user and password - just enable it).

I did not want to enable WBEM at a global level because it incorrectly identifies some machines that SNMP correctly identifies. For example the Compaq Proliant 6400R gets messed up with WBEM.

So I had set a username and password just for the VM but not globally. I guess I had to just enable WBEM globally, but not provide a global user name and password (at least I hope to prevent it from messing up my other non-VM machines).

Thanks
Nelson

[David Claypool]

Just to set the record straight, HP SIM talks "pure" WBEM as defined by the DMTF. That means Common Information Model data from the CIMv2 namespace encoded into XML over secure HTTP.

WMI, on the other hand, uses objects from its own WMI namespace and the transport is DCOM.

The purpose of the WMI Mapper is to interoperate between the "pure" WBEM as spoken by HP SIM and the WMI implementation.