Video Screencast Help

Altiris 7.1 and 7.5 Agents not initialized and/or talking to wrong NS

Created: 11 Feb 2014 • Updated: 13 Feb 2014 | 6 comments

My remaining issue now is I have Windows XP stations running 7.5 agents that will for no reason switch from communicating with my 7.5 server, to the 6.9 server.  They get stuck there...

My original problem was our 7.1 Server died, and needed to be reinstalled. We decided to scrap that one and install 7.5 in it's place.  That discussion is here https://www-secure.symantec.com/connect/forums/altiris-71-server-corrupted-deploying-new-75-server-questions and went fine.

I have over 1000 machines connected and upgrading to the 7.5 client properly.  However I also have a lot of 7.1 clients that are stuck at "Agent not initialized".  The most troubling thing is I have 7.1 agents on Windows XP machines that are now trying to talk to our old 6.9 install when they were NEVER setup to do so!  If I install the 7.5 agent it does the same thing, it's bizzare.

I was almost ready to use an AD Policy to run AeXNSClientUninstall.exe on everything a few days and re-deploy the clean 7.5 clients.  But in testing I noticed some XP machines pointing to the wrong server after a few hours or restarts.  It does this with or without 6.9 AClient installed.

Has anyone seen this before!?  What could be causing my 7.1 and 7.5 agents to be targeting the old 6.9 server?  Is there a way to fix "Agent not initalized" without uninstall/reinstalling the agent?

Operating Systems:

Comments 6 CommentsJump to latest comment

SK's picture

Is there a dns alias pointing to the 6.0 NS?

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Solkre's picture

The 6.9 server is named ghsaltiris1, and there's an alias "altiris" that also points to it.

The 7.5 server is named gcsaltiris and the clients are told to go to exactly that.

I got ahold of support and he had me set an alternate NS address in the 6.9 system, and enable the legacy client service in 7.5  Silly me, I didn't assume 7.1 clients would be "legacy" to the 7.5 system.

Colin Walsh's picture

Are you now seeing those 7.1 agents communicating with the 7.5 Notification Server? If so, also make sure these machines are targeted by the 7.5 Management Agent Upgrade Policy found at 'Settings>Agent/Plug-ins>Symantec Management Agent'. You'll need to drill down a little further to 'Windows>Non Site Server>Symantec Management Agent for Windows x64 (Non-Site Server) - Upgrade to 64-bit Symantec Management Agent 7.5'.

*Or "Symantec Management Agent for Windows x86 (Non-Site Server) - Upgrade to 32-bit Symantec Management Agent 7.5" if you have 32-bit systems as well.*

Solkre's picture

Well I had made the incorrect assumption that the 7.1 client would work with the 7.5 server and upgrade.  While in a lot of cases it did, in others it didn't.  Turning on 'legacy agent communication' fixed those issues.  I already had my update and plug-in policies setup.

My remaining issue now is I have Windows XP stations running 7.5 agents that will for no reason switch from communicating with my 7.5 server, to the 6.9 server.  They get stuck there...

 

SK's picture

The only 6.9 server that is a Symantec product is deploment server, so I doubt the a sma would connect to it as it communicates with aclients and dagents only.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Colin Walsh's picture

Is the "NS" that these machines think they're connecting to actually the 6.9 DS server? I know that you mentioned an alias for that server before, so could it be possible there is a Notification Server out there we have forgotten about? Did you have a hierarchy at any point that could still have a 7.1 Notification Server still trying to take these agents back? Did you have an older 6.x Altiris Notification Server that could possibly be targeting these clients?

Like Solkre said, I don't think that the 6.9 Deployment Server would be able to communicate with the 7.1/7.5 Management Agents. Not in a way that would make them redirect to that server at least.