SuperUser
 
Posts:26
 |
| 10/27/2004 7:58 AM |
|
| Do you know a command that allows stop and start the status of all Agent Technology Services components on a remote machine?? (In differents windows domain). |
|
|
|
SuperUser
Posts:26
|
| 10/27/2004 9:19 AM |
|
Remote Command (rcmd) allows you to connect to the DOS shell of another computer, sort of like a telnet session. It comes on the NT/200x resource kits, but the downside is that you have to install the service on both computers, which you could easily do with Software Delivery or login scripts.
Once you have it working, you could either stop and start the agents on the other computer manually or write a batch script to start and stop the agents based on a shedule or an event.
HTH,
Don |
|
|
|
SuperUser
Posts:26
|
| 10/27/2004 9:20 AM |
|
Did you try the servicectrl command? More instructions are in the CA reference guide. (Start - programs - Unicenter TND - books online - CA Reference.)
servicectrl status --remote= servicectrl stop --name=hpaagent --remote= servicectrl start -m --name=hpaagent --remote=
You could also try the psexec utility from Sysinternals. |
|
|
|
SuperUser
Posts:26
|
| 10/27/2004 10:00 AM |
|
This is the bat file that we use to stop and restart agent remotely.
servicectrl stop --name=hpaagent --remote=%1 servicectrl stop --name=prfagent --remote=%1 servicectrl stop --name=cailoga2 --remote=%1 servicectrl stop --name=caiw2kos --remote=%1 servicectrl stop --name=Aws_snmp --remote=%1 servicectrl stop --name=aws_sadmin --remote=%1 servicectrl stop --name=aws_orb --remote=%1
servicectrl start --name=aws_orb --remote=%1 servicectrl start --name=aws_sadmin --remote=%1 servicectrl start --name=aws_snmp --remote=%1 servicectrl start --name=caiw2kos --remote=%1 servicectrl start --name=cailoga2 --remote=%1 servicectrl start --name=prfagent --remote=%1 servicectrl start --name=hpaagent --remote=%1 |
|
|
|
SuperUser
Posts:26
|
| 10/27/2004 10:10 AM |
|
I think the problem with using the servicectrl command is that if you use it to stop awservices, it stops the ORB and then the servicectrl command can not be used to start awservices. If you stop and start the agents individually, you will be ok without stopping the ORB. Another problem is there was a security issue in conjunction with the servicectrl command that CA released a fix for that restricted permissions for the use of the command back in either 3.0 0000 or 3.0 0211.
We talked about using a batch file to stop and then restart awservices and controlling it with workload when needed. |
|
|
|
SuperUser
Posts:26
|
| 10/27/2004 1:06 PM |
|
The Tom's Bat it's right for me, just only need that command only for the people who work at the "Monitoring Center" (emergency only).
I've checked it and work. I had to change the paremeter "-" by "+" in the access.cfg file. |
|
|
|
SuperUser
Posts:26
|
| 09/25/2005 4:59 AM |
|
| Or just use the Admin Services, connect to another computer, stop and restart thr unicenter services... |
|
|
|