Every time you launch the app from the TS session you are astarting a new session NOT connecting to the service.  You must log into the console session in order to manipulate Salive effectively.  I have heard you can make changes and then restart the service from the TS session but you can in no way view the service session without connecting ot the console session of the server.  This can be accomplished with other remote control software (VNC) or with TS by using ht e/console switch (only works on 2003 server).

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Jordan
Sent: Wednesday, July 28, 2004 9:41 AM
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 ….

 

 

Reply via email to