Can no longer identify virtual machines using WBEM

[NJK-Work]

I have been using WBEM in SIM to identify virtual Windows 2003 servers running on ESX for at least a year now or longer, with 0 problems. Now, I am no longer able to do so. I am using the same WBEM administrator account with the same password and that account is a local administrator of the VM. When I do a manual discovery of the VM, it adds it to the inventory but the model is "unknown" instead of the normal "VMware Virtual Platform" that we are used to seeing. The only thing I think we have done new recently is upgrade to ESX 3.5 U2 and VC 2.5 U2. I am not sure how that would affect the discovery of WBEM information in a VM.

Is there anyway, outside of SIM, to test Windows 2003 for basic WBEM functionality? So that I can tell if it is the VM that is the problem or if it is SIM.

Thanks
Nelson

[David Claypool · Accepted solution]

Nelson, I generally use a thing from Microsoft called 'Scriptomatic' that will spit out scripts that will do WMI calls. By default, it refers to "." as the computer, the local host, so you can modify it for the remote instance. Make sure you can talk WMI between the CMS and the VM that's a target.

[NJK-Work]

Thanks.

Nelson