Client Management Suite

We migrated our agents to a new Notifcation server.  The agents are workingfine, but they keep trying to talk to the old NS as well.  Ive cleared out the registry entries that reference the old NS on the client, but when the agent starts/restarts it populates those registry keys again.

We have 22,000 Endpoints doing this currently.

 

Any ideas?

Try stopping the Symantec agent service and deleting the LDB folder at c:\programdata\symantec\ldb. If this works the problem will be fixed in hot fix 1 for 8.0.

Does the new NS have an Alternate NS address set in an agent settings policy? Look in an agent log to see why it's changing. You could try aexagentutil /server:newservename on one and see if that sticks. Anyway I'd create a DNS entry for the old NS name pointing to the new NS IP once the old NS is turned off, 22,000 clients won't all get caught.