Running it as service and as app. at the same time will give weird results. Also controlling it via a TS session isn't supported.
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Corey Horton Sent: Fri Jun 13 6:56 PM To: [EMAIL PROTECTED] Subject: [SA-list] Running As a Service One more question and I'm done for today. We run SA on a box in our server room that has Terminal Services installed.SA is set so that it reads the config info from the registry and it's pointing to the text file, etc. Ideally, once you receive an alert, you hope you can respond to the situation. However, some things are worth noting, but may be something that can wait until later (like in the morning back at the office). My question is, if SA is running as a service, and I launch it as an app simultaneously, put a machine into MAINTAINENCE (uncheck it) and save the config file, will SA running as a service (never stopped) pick up the changes? Or, do I have to stop and restart the service? The is no "front end" to SA when it is running as a service, so, I've got to launch it in app mode. Terminal Services allows me to do this from afar (like at my house). I want to do this to put certain machines in MAINTAINENCE mode to stop the alarms on things I can't fix right away. Hope this question makes sense. Thanx Again [EMAIL PROTECTED] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
<<attachment: winmail.dat>>
