I haven't called Support yet but I think that I should report this one.
We're in the process of building out ~20 new Site (Task and Package) servers. Up until now we have one giant site service. I'm building sites as I build a site's new server but the new server starts servicing requests from clients outside of the new site. What's happening is that even after I move the new site server to the new site I have clients that are not part of the new site still using the new site server for their own. And they won't let go
I have the Reset Task Agent task running twice a day as part of an MSD policy (with the checkbox checked) but you can watch the task agent do a reset and still connect to the undesired server. Even running the Task directly has the same effect. Rebooting the client or restarting the Symantec Management Agent both result in the task agent still hanging on to the undesired server.
It's not until I either click Reset Agent from the agent GUI or from the RAAD tool does the task agent actually register with its proper server.
Has anyone else encountered this? I'm assuming the the clients are using the same site server for task and package requests but I can't be certain.
FWIW I'm running 7.1 SP2 MP1.1 with Rollup 2.
