RE: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'?

[Kevin Stone]

That way will work just fine,  I've used it many times myself.   I have also used TS to connect to a system then VNC directed to the loopback(127.0.0.1) to connect to the console.  This way I don't have to stop SA just to add, remove or change entries.   -Kevin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deadman, Phil Sent: Wednesday, July 28, 2004 11:07 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'? I have quite successfully used TS to maintain Servers Alive  - by stopping the SERVICE first, starting SA in the TS session, making and saving the necessary changes, quit SA, then restart the service. For quickly controlling SA and changing checks into Maintenance etc I use TELNET, and all stats etc are formatted nicely in an HTML page. Cheers, Phil.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: 28 July 2004 15:45 To: [EMAIL PROTECTED] Subject: RE: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'? If the service is running on the server and you're going to it via TS, then you won't see the tray icon of the service.  Probably what you do is start the app and that's then a 2nd "instance" of Servers Alive running. If you want to configure Servers Alive via a remote connection then you will need to have a view on the real desktop of the server not a virtual desktop.  And by default a TS session is a virtual desktop.  Only with TS of Win2003 you can see the real desktop by using the /console option of the TS client.     Dirk.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Jordan Sent: Wednesday, July 28, 2004 4:41 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'? How do you mean don’t run via Terminal Services session?  The service is set to start automatically on that server – and I TS to that box to look at it, create new rules, do my testing.  I don’t go and stand at that server’s console for ANY task I do on it, and definitely do not plan to make a habit of having to visit the server to work with monitoring software.  I also use monitoring software on servers at our client sites – where TS is our primary method of access. And I don’t stop or close the app, I just disconnect from a TS session …. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, July 28, 2004 1:26 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'?   Don't run it via a TS session, just run it directly on the system and IF the service is running it will keep running and the stats will be kept.  If the app (or service) is stopped you loose the stats.   Dirk.     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Jordan Sent: Wednesday, July 28, 2004 12:37 AM To: [EMAIL PROTECTED] Subject: [SA-list] Newbie Question - Why Doesn't It Stay 'Always On'? Have just been running an eval version for a few days now.  Like it a lot. But ….. why does it appear as if it ‘goes to sleep’ in effect if I don’t keep it running in the foreground or I log off / disconnect from a Terminal Service session to the server where SA is running?  What I mean by going to sleep is that when I next connect to that server, all the Statistics available for each check seem to be back down to zero on the number of cycles, and it seems as if it’s in ‘startup’ mode. I have all my groups and checks set to check all day and all night on the scheduling tabs, I have it running as a service and so on – what else do I need to do to make it ‘always on’? Thanks in advance for any replies and help ….     *********************************************************************************************** This E-mail and any files transmitted with it is intended for the use of the addressee only and may contain confidential information. If you are not the intended recipient you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately and delete this e-mail. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Signet Group plc or any of its subsidiaries. ***********************************************************************************************