Altiris 7.1 and 7.5 Agents not initialized and/or talking to wrong NS
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?