Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Replication Error, Associate old clients with new Manager Install

Created: 15 Aug 2012 | 2 comments

In the process of migrating Endpoint Manager from one server to another I inadvertently copied the new installs database over the old one, did it backwards during the replication wizard. I did backup the database first but only by making a copy of it so I am not able to restore it apparently.  I have a clean install of Endpoint Manager on a new server that I would like to be able to communicate with the clients that I already have deployed.  I tried the sylinkreplacer utility and it finds all of the clients but they all fail for some reason.  My question is if I just re-deploy by doing a remote push to all of the clients will that install an additional copy of Endpoint Protection or will it overwrite the old one?  I'm open to any other suggestions as well, using the old database is not a huge deal starting fresh would be fine, just want to get the manager and clients talking again.  Thanks!

Comments 2 CommentsJump to latest comment

Jason1222's picture

Well, if you don't mind starting over...  You can simply redeploy to the clients and it will re-establish communication to the old clients and the new server.

The SylinkReplacer tool, you need to obtain from Support and there are different version depending on the version of SEPM you are running.

Lastly, there is always the Sylinkdrop tool - but that would involve client by client setup.

If you are in a jam, here is a link to a batch file I wrote up for Sylinkdrop at logon time...

https://www-secure.symantec.com/connect/forums/assistance-creating-batch-file-run-sylinkdropexe#comment-7213161

Chetan Savade's picture

Hi,

My question is if I just re-deploy by doing a remote push to all of the clients will that install an additional copy of Endpoint Protection or will it overwrite the old one?

--> No, it won't install additional copy of Endpoint Protection. It will overwrite the old one.

I would suggest to go with Sylink replacer tool, it would replace sylink.xml file & clients should start communication with new server. As you said it's not working then sylink.log file would required for further analysis.

For testing purpose manually replace sylink.xml file on 2-3 machines & check.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<