Endpoint Protection

Hi All,

One of our customers installed SEP version 12.1 RU4 and the client is asking for a restart of the machine. I wanted to understand what triggers a restart requirement? Also if no restart was chosen in which conditions would it still ask for a restart?

Thanks.

Did a box come up or does it just show on the GUI?

You can configure these options to be silent:

A description of the Symantec Endpoint Protection 12.1 client Restart Settings

If installing NTP, or upgrading from 11.x, a reboot is always needed.

Hi,

Thank you for posting in Symantec community.

If it's a fresh install firewall components need reboot to get it activated.

If it's an upgrade, SEP 12.1 employs a side-by-side, replace on reboot installation strategy. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot.

The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.

This technique enables you to change the normal portion of the installation path during a migration, when applicable.   

Hi,

It is not necessary to restart the computer in order to complete the installation or migration, then SEP will not reboot the computer even if Forced restart, Delayed restart, or Custom restart is chosen. SEP only restarts the computer when a restart is needed in order to finish the upgrade or migration process. This behavior is by design in order to minimize unnecessary restarts.

Is there any update?

I was just curious as to some technical details of why it asks for a restart and it wouldn't in earlier versions in some cases.

If the content updates are being pushed then I'm happy with waiting for a restart.

Hi,

SEP 12.1 employs a side-by-side, replace on reboot installation strategy. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot.

The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.

This technique enables you to change the normal portion of the installation path during a migration, when applicable.   

Thank You. This is a perfect answer that I was looking for.

You are welcome!