Moving SEPM management console to a new server
Hello! I recently tried to move SEPM management console to a new server as the old server is going to be decommissioned. I used the Disaster Recovery Method outlined in this article:
I met the criteria for the Replication Method but it was never able to connect to the old server. The old server's Endpoint service crashes often, that's one of the reasons the server is going away and the software is moving elsewhere.
The new machine has been set up as Priority 1 (and the old machine as Priority 2) since Friday, but none of the clients have moved.
When that didn't work, I thought I would use the Sylink replacement tool to update the clients instead, but I don't have a sylink.xml file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent. OK, no big deal, I thought, I'll re-export them from the new console.
So on the new server's Management Console I went to Clients, right clicked a group, and selected Export Communiations Settings, but inside the resultant XML file, the server listed is still the old server, not the new one.
If I could somehow force the new instance of the management console to claim all the client computers (or even one of them) then I could get a working sylink.xml file to use with the Sylink replacement utility, I think... just not sure how to do that. If I removed the endpoint protection client from one of my machines and added it back in using the new console, could I then replicate its sylink.xml out to all the other clients?
The other thought I had was to completely disable SEPM on the old server and see if, once that server is completely unreachable, the priority 1 server will kick in.
I'm sure I did something wrong somewhere. If anyone has any ideas how I could possbily get my clients to associate with the new server instead of the old that would be great.