There are a couple of possibilities: * run the service as system account with desktop interaction and specify a username/password for the remote checks that need authentication
* run the servie as a domain account -> interface will NOT be loaded and can't be called (as you don't have desktop interaction) Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, March 26, 2007 10:31 PM To: Servers Alive Discussion List Subject: [SA-list] Running Servers Alive as a Service Can someone point me to a link that describes how to run Servers Alive as a service? I've been tinkering with this a bit today and not making much progress. I've tried setting the service up to start automatically using the local system account and enabling the service to interact with the desktop. That sort of worked. Unfortunatly, lots of remote checks failed since the local system account on this machine can't check things like disk space on other machines. I know I could include authentication information on each check but that is going to be a pain in the neck to setup. I've tried to run the service under a special account that we use to run services. While I see the sevice starting in the event viewer, Servers Alive never really seems to load up the host file and never seems to start running. Mart To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
