WBEM woes continue

[James Spring_1]

Okay, so maybe I am too much of a perfectionist, but this drives me nuts!
I have a 250 server environmnet that I monitor with SIM. I tried setting WBEM usernames and passwords at the global level, and it worked on all my servers, except for some of the systems they showed as just "PROLIANT" in the product name and not the full product name (ie Proliant 8500). Annoying as I give reports to my management and they say "how can we tell what models are present blah blah blah..." So I disabled WBEM at the global level. The product name for the proliants returned but this wiped the product name from my VMWare servers, which used to show up as "VMWare Virtual Platform" with the OS type installed. Now nothing, no product or OS Name. While having 10 or so servers with no product name was better than having 30 or so with just PROLIANT, it still p's me off b/c hey, I'm a perfectionist. So I get crafty. I re-enable WBEM at the global level, but leave the passwords blank. I then go to my 10 VMWare devices and set WBEM username and password on each system in the SIM console. The problem I have now is that only 3 show "VMWare Virtual Platform." For the life of me I can't figure out why the other 7 don't show up. I was hoping someone could shed light on how CIM stored credentials for WBEM, so I could verify they are getting set appropriately. I still have some testing in mind, such as opening WMI wide open (security check, but the same account is used on the 3 servers that show and the 7 that don't, and yes, it is already in the administrators group on each box), and checking network traces. Any other WBEM tricks would be appreciated as well.

[Joel Rubenstein]

SIM stores SNMP and WBEM user names and passwords in the nodesecurity.xml file.

You can display the contents of this file using the command "mxnodesecurity -l" For security reasons the actual passwords are not displayed.