Remotely Change the Altiris Agent to Point to a Different Notification Server
Filed under:
Deployment Solution, Software Delivery Solution, Notification Server
Automation, Basics, Configuration, Software Delivery, Command Line
Submitted by Kinetic on Thu, 2008-05-15 11:31.
This is a small script to change the Notification Server an Agent is pointing to remotely. It's a very basic script. There is not any error checking nor arguments that can be passed.
In the future, I'd like to extend this to remotely change any property of the agent and maybe enumerate a list of machine names.
After you unzip the file, rename the .TXT to .VBS
Inside there are 2 variables at the top of the script:
- StrComputer - change this to the machine who's agent you want to change.
- NSsvr - The NS server you want the agent to point to.
NOTE #1: This is probably overstating the obvious, but make sure the account you are running the script with has admin rights to the machines you are hitting it with.
NOTE #2: This is not meant to be used as policy/task. This is not a DS tool, this is an NS tool. In large environments you will come across agents that are pointing to the wrong NS occasionally. This tool is for changing an agent instantly and remotely, without having to open ANY console.
| License: | AJSL By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License |
| Support: | User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab. |
(46 votes)
| Attachment | Size |
|---|---|
| remote_agent_server_set.zip | 361 bytes |
- Login or register to post comments
- 729 reads
- Printer-friendly version
Thanks!
No enough words to say how it can help me this tool, in fact I will migrate to different DS server next week.
Thanks again,
Paolo
Good for one-offs
This looks like it would be fine for one-off changes. I usually set up a DS job to call the agent util. That lets you run it on a number of machines without having to create a list or edit a file.
Just my 2 cents!
Why not just run the
Why not just run the command line itself within DS rather than a script?
c:\program files\altiris\altiris agent\aexagentutil.exe /server:new.server.com
Wouldn't it be a bit easier than embedding a script?
Just a thought.
or put a agent policy in place on the old server that points it to the new server....(if both servers are active and you can make a collection that would include the devices you want to move)
Not really meant to be a task/job
This really isnt meant for setting up a job or task in any console. It's just a utility when you need to change an agent's NS quickly and remotely.
We have a deployment team that notice a few machines pointing to the incorrect NS. In the middle of setting up large collections, they needed a way to change an agent instantly.
This usually seems to occur if machines were just set up for a department and someone pulled the wrong agent packages down. There are many other reasons an agent might be pointing to the wrong NS before the policy hits it. This just allows them to change the agent without waiting for the policy to come around.
Thanks for the comment!
Another option:
I've found the PSTools suite extremely useful for this job. Simply create batch file called "transfer.bat" and copy the following command into it:
psexec \\%1 "c:\program files\altiris\altiris agent\AeXAgentUtil.exe" /server:SERVERNAME
This batch file will allow you to type "transfer (computer name or IP)" into a command window on your PC and initiate a server transfer. As long as the target PC is online, of course. Be sure to check the program path, change the SERVERNAME value, ensure the batch file can see psexec.exe, and you'll be in remote transfer paradise!
Steve M.
Praxair, Inc.
Buffalo, NY
PC Applications Engineer
Use NS functionality
I use the functionality inherent to NS to do this:
Create a collection and apply a different Altiris Agent Configuration policy to it pointing to an alternate NS. The next time the NS Agent checks in, it will move on over to the NS of your choosing. The ideas above are good too, just shedding some light on an alternate method!
Nick Morea
Altiris Certified Engineer