Mark, Since we rely heavily on the dependencies feature found in WUG, I decided not to upgrade to WUP2K5 since this feature does not work correctly in the WUP2k5 upgrade. Two questions...One of them related to this very topic:
1. Does this happen with upgrades going from WUG to WUP2k6 as well (I'll be backing up my WUG installation prior to testing this new version anyway so it won't really matter, but it is a concern I need to be aware of none the less)? 2. Has the 'broken' dependancies issue with WUP2k5 been resolved in WUP2k6?? For specific clarity, the issue I'm referring to here is where a device was considered "DOWN" if _ANY_ monitored service on the device should suddenly go down even though the device was in fact up and pingable- Where this becomes an issue is when a monitored service like a L3 switch/router interface, which someone had a server attached to it, went down because someone mistakenly or on purpose shut down/rebooted the server attached to that interface, that has nothing to do with a critical path thru the device which is important, or what is past it like other attached routers, switches and servers, the device was considered "down" per design of the programmers, and nothing past that device which was dependent on the L3 Switch/Router would be monitored until the down interface was brought back up (i.e. server was brought back on-line), or the interface was stopped from being monitored, even though there was nothing stopping the access to the rest of the critical devices as a result. In addition when an basic service on a server (HTTP or TELNET, FTP, etc) would go down due to purposeful or incidental activity, the server itself would be marked as down, even though the server itself was perfectly fine and accessible. Where this becomes critical is in two areas: Server and route availability alerting, and uptime reporting. Server operators would be alerted a server was down and dispatch the wrong team to fix the problem since it was a down service and not a down device or a L3 switch/router was alerted as being down instead of the server attached to it since there was no way to distinguish them apart and a lot of wasted time and effort results from this type of mis-reporting/alerting causing possible missed critical alerts just because someone needed to do maintenance on a server by taking it off-line (unplugging it from the switch/router interface). Thanks in advance for any official response to these two questions... ------------------------------------------------------------ Bryan Harrell, SPII Network Infrastructure - Tallahassee Fla. Dept of Revenue (850)-921-0700 SunCom 291-0700 ------------------------------------------------------------ >>> [EMAIL PROTECTED] 12/14/2005 2:00:10 PM >>> All, we have found a bug in the following scenario: For 2005 installs not in the standard C:\Program Files\.... directory upgrading to 2006 - if you have any custom icons, in the [drive]:\Program Files\Ipswitch\WhatsUp Professional 2005\Data\Icons directory, please make a copy of the "Icons" directory before the upgrade. We have found that the custom icons, are deleted during the upgrade. Again, this is only for installs in drives other than C: with custom icons. Once you have done the upgrade, just move the custom icons into the updated "Icons" folder. Thank you, Mark Singh Ipswitch, Inc. 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/ 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/
