Endpoint Protection Small Business Edition

Hello,

I can't seem to find a straight answer as to whether using the SylinkReplacer/dropper tools will force a reboot of a server. I recently fixed the communication packages for 2 servers through the SEPM client:

(http://www.symantec.com/business/support/index?page=content&id=TECH199124&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1422888464124NI88SHF1Xai0v00XCJW62M4X47zR5PzAy4j63)

When it completed the Sylink.xml was fixed but the servers both unexpectedly rebooted. Is it a coincidence or does that method force a reboot?

I have several servers that need their SyLink.xml fixed, but I can't afford a reboot. Is that do-able with SylinkReplacer?

It should not. Replacing the sylink does not need a reboot of the box, only the SEP service. Which the tool does automatically....

Exact version here?

sylink might have pushed the client to new group, did you see if there were any autoupgrade feature was applied to that new group? this might have reconfigured the product and rebooted the, can you echeck the eventviwer , see if there are any msi event before reboot?

I believe it could be coincident however I would suggest that instead of using tools replace Sylink.xml manually on critical servers.

Check this article: http://www.symantec.com/docs/TECH157585 

Is there any update?