My only bad experience has been this: We leave WUG running at the console of our server. Occasionally, if I need to reboot the server remotely, I cannot launch WUG at the console due to no remote control software being installed, only Terminal Services. So I connect via TS and launch it there. This allows everything to work fine, and I leave the terminal session logged in. But the next day we get to the office, we log in the computer and start WUG again, so we can view it on screen. So at this point we have it running 2 times, 1 at the console and 1 in the terminal session. If we kill the WUG application running on the Terminal Server session, the web server stops working. So we have to close and open WUG at the console to get the web interface back up.
My guess is we will not have this problem once we set it to run as a service. Dan King - MCSE, CCNA, CNE Systems Administrator [EMAIL PROTECTED] -----Original Message----- From: Glatt, Robert [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 5:09 AM To: wug (E-mail) Subject: [WhatsUp Forum] terminal server Has anyone had any bad experience using terminal server on the WUG box?? Was thinking of using it to be able to use Terminal Service as a client to the console. 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/
