The application is phenomenal, for being free. Thank you for supplying the public with your software - free of charge! With that being said, however, there are (as you're well aware) of a few issues still needing to be addressed.
1. I've tried The Dude's client-side application on a number of Windows platforms: XP, Vista, and Server 2003. The application hang still occurs and occurs frequently. Vista is actually able to recover from it without having to close the app and reopening it. The other 2 OSes, I've had to completely shut the client down. This behavior has been around since 2.2 or earlier.
2. When devices generate a notification alerting that a service/device is down and there is more than one client-side application open and connected to the server, if one disables that particular service/device from one client-side machine, server included, it still generates the notifications and sends out emails even though that service/device has been placed in somewhat of a "maintenance" mode configuration, meaning polling and notifications are no longer enabled.
Do the clients cache the server information? This behavior would lead one to believe so as once a device is disabled these notifications should stop being generated but only if the clients are running in real-time with the database.
Example: I was working from home and I got an email alert stating there was a NIC down on one of the servers. Upon logging in through the VPN and connecting to the server-side client that runs The Dude, I disabled polling and notifications on the device. Since my laptop was still at work and connected to The Dude server through the client-side application the notifications were still coming to me 20 mins after I disabled polling and notifications on that device.
Is this a misconfiguration error on my part, or could this actually be an issue? There may be times when 2-3 ppl have the client-side application open and may need to place devices in "maintenance" mode when alerts alarm. If someone disables polling on a device, all of the client-side apps should reflect that change.
3. When creating a new notification and clicking the "Advanced" tab, the program completely crashes.
4. When trying to submit the crash report via email, no details are included automatically as it did previously.
Windows Systems Administrator
- Building better business networks. Together.
- Killing the Alliance
since 2005. For the Horde