Just to run down the list of things to check:
The zWinUser and zWinPassword properties are set correctly. For your
setup, I assume it's either "domain\test" or ".\test", depending on if it's a
domain user versus a local user.
The zWinUser is in the local Administrators group (yes, it really only
needs WMI access, but let's get everything out of the way that could be
hindering success first).
The device is either in the /Devices/Server/Windows device class, or
the device class it is in has the zWmiMonitorIgnore zProperty set to "False".
For that fact, if it's in the Windows class check the zProperties on it just in
case. Also, check to make sure all these zProperties aren't being overridden
on the device itself, or if they are, that they are all set appropriately.
The Windows Firewall is either disabled, or has ports 135 and the RPC
high ports open. As you stated earlier, this seems to be the case.
On the heels of the above checkpoint, make sure there are no network
ACLs in the way. Our network security engineers just love themselves some
ACLs, so I had to make sure that they put exceptions in each VLAN ACL for my
zenoss server's IP.
Zenoss does not show any WMI events associated with the device. Just
like the modeler services will not model a device if there is an "IP is down"
event for the device, it is my understanding that zenwin / zeneventlog /
zenwinmodeler will skip the device if there are any "WMI error" events as well.
The zenwin* services are actually running, and have not gone out to
lunch. Mine do this on occasion; I have to `kill -9` them when they stop
responding. Of course I usually get heartbeat errors associated with them, so
unless you see those events you're probably ok.
Make sure you can manually run wmic from your zenoss server. The
command will look something like this:
Code:
wmic -U domain\test //xpmachine "SELECT * FROM Win32_ComputerSystem"
It should prompt you for the password and then, if it is successful, spit back
a bunch of information in what is probably supposed to be table format.
If all of those check out, then you can be fairly certain that the problem is
not with the XP machine or your setup, but that the issue is with the zenoss
services. I know you've mentioned in previous posts that you have checked some
of these things, but if you wouldn't mind going down the list once more in case
something was missed, I think that would be beneficial. Once you have verified
everything above, we can start working on the zenoss services, checking the
logs and such. Although, it does look like you have other Windows devices for
which WMI polling is working, so I would bet that the problem lies with this
specific device.
Thanks for humoring me ;-)
--seth
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=16302#16302
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
