Hello,

24x7 Version: 2.4.9
OS Version: Windows NT SP 6a / Windows 2000 SP 1

I have created a job that will on a weekly schedule reboot a windows NT server on Sunday at 2 AM. That works fine. The problem is that while the job is submitted there is never a return because, my guess is, the remote agent is shutdown by the command. Also, and perhaps this is because I do not wait long enough, it appears that the Master server still thinks that it is connected to the remote agent.

Thank you for any insight into this query.

John

Here is a trick to avoid "shout yourself in a foot" issue: Create an asynchronous job on the Agent (stop the agent if it is running, run scheduler, create new job using the reboot() statement and save). Perhaps this new job name is "RebootAgent"

Create new program job on the Master that with the following command "24x7 /JOB RebootAgent" and schedule it to be run on the Agent. Let's say this new job name will be "Caller"

Therefore, in the run-time the Master will call the Agent and submit our "Caller" job. The Agent kicks off 24x7 with "RebootAgent" as a parameter and immediately returns control to the Master. After that the invoked 24x7 will restart the Agent

: Hello,

: 24x7 Version: 2.4.9
: OS Version: Windows NT SP 6a / Windows 2000 SP 1

: I have created a job that will on a weekly schedule reboot a windows NT
: server on Sunday at 2 AM. That works fine. The problem is that while the
: job is submitted there is never a return because, my guess is, the remote
: agent is shutdown by the command. Also, and perhaps this is because I do
: not wait long enough, it appears that the Master server still thinks that
: it is connected to the remote agent.

: Thank you for any insight into this query.

: John