Redirect NS6 Agents to a new NS7 server
Updated: 21 May 2010 | 3 comments
This issue has been solved. See solution.
I may have overlooked this, but I can't seem to find how to redirect the Altiris Agent from an NS6 server to a NS7 server. I have tried running a job via the DS on the clients: "C:\Program Files\Altiris\Altiris Agent\aexagentutil.exe" /server:new-ns7.domain.com
While the agent does change its server name, it doesn't appear to be checking in to get policies. I confirmed the Altiris Agent update policy is enabled on the NS7 server. Do I have to copy some keys from the NS6 to the NS7 or something for authentication? Any tips to avoid a re-install of the agent would be appreciated. Thanks.
discussion Filed Under:
Comments
Brandon, AFAIK
you could even use the redirect policy on the altiris agent settings policy. There are some helpful ideas here, but I guess I would check the client logs, or even their records on the NS7 box. Make sure they aren't disabled or retired or something strange. I remember seeing similar behavior occasionaly when moving from one v6 server to another, and never really had a good answer as to why it happened.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
NS6 Agents can only update
THe update Agent policy task needs to be enabled. The only thing a NS6 Agent can do w/ a NS7 server is upgrade to the newer version. So enable the poicy to upgrade/update the agent and your agents will check in and update to NS7
Jonathan Jesse Practice Principal ITS Partners
ID10T error
Jim,
Thank you for the link. That is exactly what I was looking for and couldn't find. I went to connect to the server today and it was not running any services I needed again. After looking into it further, I suspect this server was being hardened based on the OU it was in. As a result, SQL services and IIS services kept getting disabled. I have fixed them and moved the server out of this OU. Using the method I mentioned originally, this started working today. The machine has checked in, seen the update policy and is now waiting to download the new ver7 agent. Thank you.
Would you like to reply?
Login or Register to post your comment.