Tim Farley said: > We use a newer Microsoft API called WMI to do this. This API comes built > into Win2K and XP, it must be installed on NT 4.0.
Nuzman said: > Is this also how you can monitor services now? Wanna explain a > little about this piece? Well, if there is a Trap, Syslog message or Windows Event Log message that corresponds directly to a particular service going up or down, then yes you can use this to monitor services too. We call that an "Association". When you apply an event to the device, there's a button that says "Association>>". Click that, and you can link that event to a particular service on that device, to make it go up or down. The advantage here of course is that the event happens immediately (or nearly so), but checking the service directly has to wait until the next poll. This can potentially allow you to lengthen your poll cycles but still maintain a close eye on things. The exact details of which events to use depend on the service you are monitoring, of course. In some cases there might be more than one event that indicates the service going up or down. If there are services that are impossible to directly poll, but you still have events that indicate their availability, you can handle that too in WUG 8. You set up a "dummy" service of type "Event State", and apply that to the host, then create the associations as you would for a polled service. --Tim Farley IPSWITCH Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
