Upgrading 14.3.x to SEP 16 triggers a mandatory restart with a 60-minute timer

Products

• Endpoint Security Complete

Issue/Introduction

When upgrading clients from version 14.3.x to SEP 16 via an 'Auto Upgrade' System Policy, devices may trigger a mandatory 60-minute restart timer. This behavior occurs even when the System Policy is configured for 'No Reboot' or a 'Scheduled Reboot,' overriding the administrator's defined restart settings.

Environment

Upgrade from SEP 14.3.x to SEP 16. 

Cause

After you upgrade 14.3.x to SEP 16, the devices require a restart.

• The restart overrides

  Client Restart Settings

  in the System Policy.
• A mandatory restart occurs approximately 60 minutes after the upgrade.
• A restart is also required to enable the Custom Application Behavior policy.

Resolution

The reboot behavior observed when upgrading from 14.3.x to SEP 16 is an intentional design requirement and cannot be circumvented, paused, or modified by System Policy settings.

• Policy Override: This mandatory 60-minute timer will trigger immediately upon installation, even if your System Policy is set to "No Reboot" or "Scheduled Reboot."

• Hard Enforcement: The countdown is hard-coded into the upgrade logic to ensure system integrity; there is no administrative override available once the process begins.

Recommended Action: To avoid data loss or workflow interruption, administrators must plan deployments for maintenance windows or off-peak hours and notify end-users in advance of the 60-minute forced restart.