Endpoint Protection Small Business Edition

I am in the process of switching my clients over from one server to another and wish to use the remote push of communication settings in the SEP manager. Previously I had done my servers with Sylink drop and it caused all of the servers to restart in the middle of a work day which of course caused multiple problems. Now I am switching user computers over. My one concern is that the user will forced to restart unexpectedly and lose unsaved work. I have not found this answer and where else and wish to know from others if this is the case or not.

Assuming you're on 12.1.2 or higher, you can follow this:

Restoring client-server communications with Communication Update Package Deployment

No restart should take place as you're simply replacing the communication file.

Just ensure that the group you're moving them to does not have the restart setting configured

Go to the Group that you're using the sylink.xml file from and click on the Policies tab >> General Settings

Than check the Restart Settings tab and edit as you see fit

What about logging the user off? I only ask this because when it gets to testing the connection is uses the admin user name and password.

I've never this type of behaviour when replacing the sylink. The actual act of replacing the sylink should not cause a restart or logoff. It should be an invisible action to the end user.

The only thing I can think of is making sure to configure the restart setting properly.

Brian is right - there is no reason that simply changing the sylink on a client will cause a restart - the only reason why that would restart the system is two reasons:

1) Under Restart Settings (Clients>{GROUP NAME}>Policies>Settings (blue box)>General Settings> Restart Settings tab) - this is there if a threat remediation requires restart/or an engine update that was pushed via LU/SEPM

2) Assigned install packages to the group (also not only platform version but also feature sets as well) - if you are using the default client install settings (very common) this will cause machines to have a delayed restart between 1AM-5AM next occurance - for 12.1.x, if it is 11.x, I believe restarts happen sooner, but I do not recall)

However, there are policies that won't engage completely unless the system has been restarted, such as Application and Device control - some policies do require restarts to full enable the policy itself (however I think it pulls into condition 1 up top)

Check those before you push a sylink to any machines if they can't be restarted