Group Policy

Specify Engaged restart transition and notification schedule for Updates

Specify Engaged restart transition and notification schedule for Updates

Engaged restart transition means that Windows 10 will not be forced to reboot, but it will request users to restart, pick a time or snooze manually. So when an update shows up, it prompts the users, and the end-user can choose what to do next.  For general consumers, they can delay it for a longer period, but in Enterprise, the IT admin can set up how long the user can delay. In this post, we will show you how to configure the Specify Engaged restart transition and notification schedule for updates setting.

Specify Engaged restart transition and notification schedule for updates

Enable this policy to control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule. The period can be set between 0 and 30 days from the time the restart becomes pending.
 
You can specify the number of days a user can snooze Engaged restart reminder notifications. The snooze period can be set between 1 and 3 days.
 
You can specify the deadline in days before automatically scheduling and executing a pending restart regardless of active hours. The deadline can be set between 2 and 30 days from the time the restart becomes pending. If configured, the pending restart will transition from Auto-restart to Engaged restart (pending user schedule) to automatically executed, within the specified period.
 
If you do not specify a deadline or if the deadline is set to 0, the PC won't automatically restart and will require the person to schedule it prior to restart.
 
If you disable or do not configure this policy, the PC will restart following the default schedule.
 
Enabling any of the following policies will override the above policy:

  1. No auto-restart with logged on users for scheduled automatic updates installations
  2. Always automatically restart at scheduled time
  3. Specify deadline before auto-restart for update installation.

IT admins can schedule the period from anywhere between 0 to 30 days after the update becomes available. As a safeguard, there is a Snooze period available which can be 1 and 3 days.  There is an additional setting called Deadline. The deadline means that after it is crossed, Windows Update will automatically execute a pending restart regardless of Active Hours.

You can setup engaged restart transition by following these two methods:

  1. Group Policy
  2. Registry Editor.

Before changing Registry entries, make sure to create a restore point. In case you end up doing something which causes a problem on the computer, you can always restore.

1] Set deadlines using Group Policy Editor

  1. Open Group Policy Editor
  2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update
  3. Open a policy with name Specify Engaged restart transition and notification schedule for updates, and enable it.

When you enable it, you have to configure the number of days for Transition, Snooze, and Deadline for Quality Updates and Feature Updates.

The number of days that can be set between 2 to 30. Value for snooze can be between 1 to 3. Here is what each of these means:

The last setting is what you need to change to specify the deadline before auto-restart for update installation. If you do not specify a deadline or if the deadline is set to 0, the PC won't automatically restart and will require the person to schedule it before restart.

Lastly, you should know that the below-mentioned policies will override the policy we mentioned above.

2] Set deadlines using Registry Editor

There is a reason why I have explained so many things in the Group Policy section. When you enable the setting, it creates Registry entries. You can change the value of these to achieve the same configuration.

So, if you want to do the same using Registry Editor, follow these steps:

If you want to configure Transition and Snooze, create the following DWORD at the same place, and set the value as you see in the Group Policy-

We hope the steps were easy to follow, and you were able to specify engaged restart transition to make the user to schedule update using Group Policy and Registry Editor.

How to Develop a Game on Linux
A decade ago, not many Linux users would predict that their favorite operating system would one day be a popular gaming platform for commercial video ...
Open Source Ports of Commercial Game Engines
Free, open source and cross-platform game engine recreations can be used to play old as well as some of the fairly recent game titles. This article wi...
Parhaat komentorivipelit Linuxille
Komentorivi ei ole vain suurin liittolainen Linuxia käytettäessä - se voi olla myös viihteen lähde, koska voit käyttää sitä pelaamaan monia hauskoja p...