The time-out of the actual entry should be set higher then the time-out for the agent.
Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ray VanVelsen Sent: Wednesday, March 26, 2008 2:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] remote agents - any instructions? Dirk thanks. After reading your answer I realized that I was running a 6.0.xxxx version. I upgraded to 6.1 and now have this setup. I also have the pdf with the documentation for remote agents. In Setup-General-Remote Agents, is the timeout in seconds? How does that timeout work vs. the timeout in the actual check entry? Ray VanVelsen Porter Hills Retirement Communities -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, March 25, 2008 5:36 PM To: Servers Alive Discussion List Subject: RE: [SA-list] remote agents - any instructions? http://www.woodstone.nu/salive/woap_general.asp (http://www.woodstone.nu/salive/woap_general.asp) gives info on the remote agents. The Windows agent install is simply running the setup of the remote system and within SA (enteprise edition only) you have to "create" the agent via the setup-general-remote agents. Then you can via the add/edit screen, create a check on the remote agent. The installation instruction for the *nix agent: http://www.woodstone.nu/salive/woap_nix.asp (http://www.woodstone.nu/salive/woap_nix.asp) Both for the *nix agent and the Windows agent, the defaults are: username: woap password: heslo port:20012 Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ray VanVelsen Sent: Tuesday, March 25, 2008 9:46 PM To: Servers Alive Discussion List Subject: [SA-list] remote agents - any instructions? Greetings One of Dirk's discussion list post mentioned remote agents. Do you have instructions on how to use a remote agent? or to setup a check in SA to utilize the remote agent? Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities and Services 4450 Cascade Rd SE Suite 200 Grand Rapids MI 49546-8330 616-301-6200 (direct) 616-949-4975 (main) 616-633-9410 (cell) 616-954-1795 (fax) [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) www.porterhills.org (http://www.porterhills.org/) One of "West Michigan's 101 Best and Brightest Companies to Work For" E-mail Confidentiality Notice: The transmitted material is intended only for the use of the addressee. It may contain information that is covered by the confidentiality policies applicable to directors, committee members, and management of Porter Hills Retirement Communities and Services. If you are not the intended recipient, please be aware that any review, use, dissemination, distribution, or copying of this communication, in whole or in part, is prohibited. If you received this communication in error, please notify us immediately by e-mail reply or by phone (616-949-4975, extension 20411), delete the communication and destroy any copies. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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.
