Yes, I got WMI working even on Windows 2003 standalone servers (without AD) and on a XP SP2 box. XP needed the firewall to me modified to allow incoming WMI access.
The trick is to resolve the test IP address to the Netbios name of the box to be tested because the WMI implementation of Zenoss uses this resolved name to query the Windows box, even if you originally added the server to zenoss via IP address. I set up forward and backward DNS resolution, even though I am not sure whether both are actually necessary. There is a handy DNS resolution check function in the device menu of zenoss. My Zenoss 2.0.2 does collect windows services but (almost) no windows events, and listing them all brings a python crash if only one of the service names contains umlauts (non-ascii characters). Giving frequent false alarms of WMI not being available, this WMI implimentation is still in alpha state in my opinion. Martin geotek.de (http://geotek.de) ------------------------ unset -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9572#9572 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
