mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 04:43:37 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into mdt
This commit is contained in:
Greg Lindsay
@ -249,6 +249,7 @@
|
||||
### Use Windows Update for Business
|
||||
#### [Deploy updates using Windows Update for Business](update/waas-manage-updates-wufb.md)
|
||||
#### [Configure Windows Update for Business](update/waas-configure-wufb.md)
|
||||
#### [Enforcing compliance deadlines for updates](update/wufb-compliancedeadlines.md)
|
||||
#### [Integrate Windows Update for Business with management solutions](update/waas-integrate-wufb.md)
|
||||
#### [Walkthrough: use Group Policy to configure Windows Update for Business](update/waas-wufb-group-policy.md)
|
||||
#### [Walkthrough: use Intune to configure Windows Update for Business](https://docs.microsoft.com/intune/windows-update-for-business-configure)
|
||||
|
||||
@ -1,93 +1,89 @@
|
||||
---
|
||||
title: Creating a Custom Compatibility Mode in Compatibility Administrator (Windows 10)
|
||||
description: Windows® provides several compatibility modes, groups of compatibility fixes found to resolve many common application-compatibility issues.
|
||||
ms.assetid: 661a1c0d-267f-4a79-8445-62a9a98d09b0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Creating a Custom Compatibility Mode in Compatibility Administrator
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
Windows® provides several *compatibility modes*, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases.
|
||||
|
||||
## What Is a Compatibility Mode?
|
||||
|
||||
|
||||
A compatibility mode is a group of compatibility fixes. A compatibility fix, previously known as a shim, is a small piece of code that intercepts API calls from applications. The fix transforms the API calls so that the current version of the operating system supports the application in the same way as previous versions of the operating system. This can be anything from disabling a new feature in Windows to emulating a particular behavior of an older version of the Windows API.
|
||||
|
||||
## Searching for Existing Compatibility Modes
|
||||
|
||||
|
||||
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility mode, you can search for an existing application and then copy and paste the known fixes into your custom database.
|
||||
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
1. In the left-side pane of Compatibility Administrator, expand the **Applications** folder and search for your application name.
|
||||
|
||||
2. Click the application name to view the preloaded compatibility modes, compatibility fixes, or AppHelp messages.
|
||||
|
||||
## Creating a New Compatibility Mode
|
||||
|
||||
|
||||
If you are unable to find a preloaded compatibility mode for your application, you can create a new one for use by your custom database.
|
||||
|
||||
**Important**
|
||||
A compatibility mode includes a set of compatibility fixes and must be deployed as a group. Therefore, you should include only fixes that you intend to deploy together to the database.
|
||||
|
||||
|
||||
|
||||
**To create a new compatibility mode**
|
||||
|
||||
1. In the left-side pane of Compatibility Administrator, underneath the **Custom Databases** heading, right-click the name of the database to which you will apply the compatibility mode, click **Create New**, and then click **Compatibility Mode**.
|
||||
|
||||
2. Type the name of your custom-compatibility mode into the **Name of the compatibility mode** text box.
|
||||
|
||||
3. Select each of the available compatibility fixes to include in your custom-compatibility mode and then click **>**.
|
||||
|
||||
**Important**
|
||||
If you are unsure which compatibility fixes to add, you can click **Copy Mode**. The **Select Compatibility Mode** dialog box appears and enables you to select from the preloaded compatibility modes. After you select a compatibility mode and click **OK**, any compatibility fixes that are included in the preloaded compatibility mode will be automatically added to your custom-compatibility mode.
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
~~~
|
||||
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Creating a Custom Compatibility Mode in Compatibility Administrator (Windows 10)
|
||||
description: Windows® provides several compatibility modes, groups of compatibility fixes found to resolve many common application-compatibility issues.
|
||||
ms.assetid: 661a1c0d-267f-4a79-8445-62a9a98d09b0
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: appcompat
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Creating a Custom Compatibility Mode in Compatibility Administrator
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
Windows® provides several *compatibility modes*, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases.
|
||||
|
||||
## What Is a Compatibility Mode?
|
||||
|
||||
|
||||
A compatibility mode is a group of compatibility fixes. A compatibility fix, previously known as a shim, is a small piece of code that intercepts API calls from applications. The fix transforms the API calls so that the current version of the operating system supports the application in the same way as previous versions of the operating system. This can be anything from disabling a new feature in Windows to emulating a particular behavior of an older version of the Windows API.
|
||||
|
||||
## Searching for Existing Compatibility Modes
|
||||
|
||||
|
||||
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility mode, you can search for an existing application and then copy and paste the known fixes into your custom database.
|
||||
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
1. In the left-side pane of Compatibility Administrator, expand the **Applications** folder and search for your application name.
|
||||
|
||||
2. Click the application name to view the preloaded compatibility modes, compatibility fixes, or AppHelp messages.
|
||||
|
||||
## Creating a New Compatibility Mode
|
||||
|
||||
|
||||
If you are unable to find a preloaded compatibility mode for your application, you can create a new one for use by your custom database.
|
||||
|
||||
**Important**
|
||||
A compatibility mode includes a set of compatibility fixes and must be deployed as a group. Therefore, you should include only fixes that you intend to deploy together to the database.
|
||||
|
||||
|
||||
|
||||
**To create a new compatibility mode**
|
||||
|
||||
1. In the left-side pane of Compatibility Administrator, underneath the **Custom Databases** heading, right-click the name of the database to which you will apply the compatibility mode, click **Create New**, and then click **Compatibility Mode**.
|
||||
|
||||
2. Type the name of your custom-compatibility mode into the **Name of the compatibility mode** text box.
|
||||
|
||||
3. Select each of the available compatibility fixes to include in your custom-compatibility mode and then click **>**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are unsure which compatibility fixes to add, you can click **Copy Mode**. The **Select Compatibility Mode** dialog box appears and enables you to select from the preloaded compatibility modes. After you select a compatibility mode and click **OK**, any compatibility fixes that are included in the preloaded compatibility mode will be automatically added to your custom-compatibility mode.
|
||||
> If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
@ -90,7 +90,7 @@ With Windows 10, Microsoft will package new features into feature updates that c
|
||||
|
||||
Monthly updates in previous Windows versions were often overwhelming because of the sheer number of updates available each month. Many organizations selectively chose which updates they wanted to install and which they didn’t, and this created countless scenarios in which organizations deployed essential security updates but picked only a subset of non-security fixes.
|
||||
|
||||
In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and non-security fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment devicess contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates.
|
||||
In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and non-security fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment devices contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates.
|
||||
|
||||
**Figure 1**
|
||||
|
||||
|
||||
@ -1,100 +1,173 @@
|
||||
---
|
||||
title: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10)
|
||||
description: Learn how to enforce compliance deadlines using Windows Update for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 06/20/2018
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
# Enforcing compliance deadlines for updates
|
||||
|
||||
>Applies to: Windows 10
|
||||
|
||||
Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce patch compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer revisions. We offer two compliance flows that you can choose from:
|
||||
|
||||
- [Deadline only](#deadline-only)
|
||||
- [Deadline with user engagement](#deadline-with-user-engagement)
|
||||
|
||||
## Deadline Only
|
||||
|
||||
This flow only enforces the deadline where the device will attempt to silently restart outside of active hours before the deadline is reached. Once the deadline is reached the user is prompted with either a confirmation button or a restart now option.
|
||||
|
||||
### End User Experience
|
||||
|
||||
Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to reboot the device.
|
||||
|
||||
>[!NOTE]
|
||||
>Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update).
|
||||
|
||||
### Policy overview
|
||||
|
||||
|Policy|Description |
|
||||
|-|-|
|
||||
|Specify deadline before auto-restart for update installation|Governs the update experience once the device has entered pending reboot state. It specifies a deadline, in days, to enforce compliance (such as imminent install).|
|
||||
|Configure Auto-restart warning notification schedule for updates|Configures the reminder notification and the warning notification for a scheduled install. The user can dismiss a reminder, but not the warning.|
|
||||
|
||||
### Suggested Configuration
|
||||
|
||||
|Policy|Location|3 Day Compliance|5 Day Compliance|7 Day Compliance |
|
||||
|-|-|-|-|-|
|
||||
|Specify deadline before auto-restart for update installation| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline before auto-restart for update installation |State: Enabled <br>**Specify the number of days before pending restart will automatically be executed outside of active hours**: 2|State: Enabled <br>**Specify the number of days before pending restart will automatically be executed outside of active hours**: 3|State: Enabled <br>**Specify the number of days before pending restart will automatically be executed outside of active hours**: 4
|
||||
|
||||
### Controlling notification experience for deadline
|
||||
|
||||
|Policy| Location|Suggested Configuration |
|
||||
|-|-|-|
|
||||
|Configure Auto-restart warning notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart warning notifications schedule for updates |State: Enabled <br>**Reminder** (hours): 2<br>**Warning** (minutes): 60 |
|
||||
|
||||
### Notification experience for deadline
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
## Deadline with user engagement
|
||||
|
||||
This flow provides the end user with prompts to select a time to restart the device before the deadline is reached. If the device is unable to restart at the time specified by the user or the time selected is outside the deadline, the device will restart the next time it is active.
|
||||
|
||||
### End user experience
|
||||
|
||||
Before the deadline the device will be in two states: auto-restart period and engaged-restart period. During the auto-restart period the device will silently try to restart outside of active hours. If the device can't find an idle moment to restart, then the device will go into engaged-restart. The end user, at this point, can select a time that they would like the device to try to restart. Both phases happen before the deadline; once that deadline has passed then the device will restart at the next available time.
|
||||
|
||||
### Policy overview
|
||||
|
||||
|Policy| Description |
|
||||
|-|-|
|
||||
|Specify engaged restart transition and notification schedule for updates|Governs how the user will be impacted by the pending reboot. Transition days, first starts out in Auto-Restart where the device will find an idle moment to reboot the device. After 2 days engaged restart will commence and the user will be able to choose a time|
|
||||
|Configure Auto-restart required notification for updates|Governs the notifications during the Auto-Restart period. During Active hours, the user will be notified that the device is trying to reboot. They will have the option to confirm or dismiss the notification|
|
||||
|
||||
### Suggested configuration
|
||||
|
||||
|Policy| Location| 3 Day Compliance| 5 Day Compliance| 7 Day Compliance |
|
||||
|-|-|-|-|-|
|
||||
|Specify engaged restart transition and notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Engaged restart transition and notification schedule for updates|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 3|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 4|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 5|
|
||||
|
||||
### Controlling notification experience for engaged deadline
|
||||
|
||||
|Policy| Location |Suggested Configuration
|
||||
|-|-|-|
|
||||
|Configure Auto-restart required notification for updates |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Auto-restart required notification for updates|State: Enabled <br>**Method**: 2- User|
|
||||
|
||||
### Notification experience for engaged deadlines
|
||||
Notification users get for quality update engaged deadline:
|
||||
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
Notification users get for a feature update engaged deadline:
|
||||
|
||||
|
||||
---
|
||||
title: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10)
|
||||
description: Learn how to enforce compliance deadlines using Windows Update for Business.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
# Enforcing compliance deadlines for updates
|
||||
|
||||
>Applies to: Windows 10
|
||||
|
||||
Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce update compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer versions.
|
||||
|
||||
The compliance options have changed with the release of Windows 10, version 1903:
|
||||
|
||||
- [Starting with Windows 10, version 1903](#starting-with-windows-10-version-1903)
|
||||
- [Prior to Windows 10, version 1903](#prior-to-windows-10-version-1903)
|
||||
|
||||
|
||||
## Starting with Windows 10, version 1903
|
||||
|
||||
With a current version of Windows 10, it's best to use the new policy introduced in Windows 10, version 1903: **Specify deadlines for automatic updates and restarts**. In MDM, this policy is available as four separate settings:
|
||||
|
||||
- Update/ConfigureDeadlineForFeatureUpdates
|
||||
- Update/ConfigureDeadlineForQualityUpdates
|
||||
- Update/ConfigureDeadlineGracePeriod
|
||||
- Update/ConfigureDeadlineNoAutoReboot
|
||||
|
||||
This policy starts the countdown for the update installation deadline from when the update is published, instead of starting with the "restart pending" state as the older policies did.
|
||||
|
||||
The policy also includes a configurable grace period to allow, for example, users who have been away to have extra time before being forced to restart their devices.
|
||||
|
||||
Further, the policy includes the option to opt out of automatic restarts until the deadline is reached by presenting the "engaged restart experience" until the deadline has actually expired. At this point the device will automatically schedule a restart regardless of active hours.
|
||||
|
||||
|
||||
|
||||
### Policy setting overview
|
||||
|
||||
|Policy|Description |
|
||||
|-|-|
|
||||
| (starting in Windows 10, version 1903) Specify deadlines for automatic updates and restarts | Similar to the older "Specify deadline before auto-restart for update installation," but starts the deadline countdown from when the update was published. Also introduces a configurable grace period and the option to opt out of automatic restarts until the deadline is reached. |
|
||||
|
||||
|
||||
|
||||
### Suggested configurations
|
||||
|
||||
|Policy|Location|Quality update deadline in days|Feature update deadline in days|Grace period in days|
|
||||
|-|-|-|-|-|
|
||||
|(starting in Windows 10, version 1903) Specify deadlines for automatic updates and restarts | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadlines for automatic updates and restarts | 7 | 7 | 2 |
|
||||
|
||||
When **Specify deadlines for automatic updates and restarts** is set (starting in Windows 10, version 1903):
|
||||
|
||||
**While restart is pending, before the deadline occurs:**
|
||||
- For the first few days, the user receives a toast notification
|
||||
- After this period, the user receives this dialog:
|
||||
|
||||
|
||||
- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
|
||||
|
||||
|
||||
|
||||
**If the restart is still pending after the deadline passes:**
|
||||
- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
|
||||
|
||||
|
||||
- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Prior to Windows 10, version 1903
|
||||
|
||||
|
||||
Two compliance flows are available:
|
||||
|
||||
- [Deadline only](#deadline-only)
|
||||
- [Deadline with user engagement](#deadline-with-user-engagement)
|
||||
|
||||
### Deadline only
|
||||
|
||||
This flow only enforces the deadline where the device will attempt to silently restart outside of active hours before the deadline is reached. Once the deadline is reached the user is prompted with either a confirmation button or a restart now option.
|
||||
|
||||
#### End-user experience
|
||||
|
||||
Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to restart the device.
|
||||
|
||||
>[!NOTE]
|
||||
>Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update).
|
||||
|
||||
#### Policy overview
|
||||
|
||||
|Policy|Description |
|
||||
|-|-|
|
||||
|Specify deadline before auto-restart for update installation|Governs the update experience once the device has entered pending restart state. It specifies a deadline, in days, to enforce compliance (such as imminent installation).|
|
||||
|Configure Auto-restart warning notification schedule for updates|Configures the reminder notification and the warning notification for a scheduled installation. The user can dismiss a reminder, but not the warning.|
|
||||
|
||||
|
||||
|
||||
|
||||
#### Suggested configuration {OK}
|
||||
|
||||
|Policy|Location|3-day compliance|5-day compliance|7-day compliance|
|
||||
|-|-|-|-|-|
|
||||
|Specify deadline before auto-restart for update installation| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline before auto-restart for update installation |State: Enabled<br>**Specify the number of days before pending restart will automatically be executed outside of active hours:** 2| State: Enabled<br>**Specify the number of days before pending restart will automatically be executed outside of active hours:** 3 | State: Enabled<br>**Specify the number of days before pending restart will automatically be executed outside of active hours:** 4|
|
||||
|
||||
#### Controlling notification experience for deadline {OK}
|
||||
|
||||
|Policy| Location|Suggested Configuration |
|
||||
|-|-|-|
|
||||
|Configure Auto-restart warning notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart warning notifications schedule for updates |State: Enabled <br>**Reminder** (hours): 2<br>**Warning** (minutes): 60 |
|
||||
|
||||
#### Notification experience for deadline
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
### Deadline with user engagement
|
||||
|
||||
This flow provides the end user with prompts to select a time to restart the device before the deadline is reached. If the device is unable to restart at the time specified by the user or the time selected is outside the deadline, the device will restart the next time it is active.
|
||||
|
||||
#### End-user experience
|
||||
|
||||
Before the deadline the device will be in two states: auto-restart period and engaged-restart period. During the auto-restart period the device will silently try to restart outside of active hours. If the device can't find an idle moment to restart, then the device will go into engaged-restart. The end user, at this point, can select a time that they would like the device to try to restart. Both phases happen before the deadline; once that deadline has passed then the device will restart at the next available time.
|
||||
|
||||
#### Policy overview
|
||||
|
||||
|Policy| Description |
|
||||
|-|-|
|
||||
|Specify engaged restart transition and notification schedule for updates|Governs how the user will be impacted by the pending restart. Transition days, first starts out in Auto-Restart where the device will find an idle moment to restart the device. After 2 days engaged restart will commence and the user will be able to choose a time|
|
||||
|Configure Auto-restart required notification for updates|Governs the notifications during the Auto-Restart period. During Active hours, the user will be notified that the device is trying to restart. They will have the option to confirm or dismiss the notification|
|
||||
|
||||
#### Suggested configuration
|
||||
|
||||
|Policy| Location| 3-day compliance| 5-day compliance| 7-day compliance |
|
||||
|-|-|-|-|-|
|
||||
|Specify engaged restart transition and notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Engaged restart transition and notification schedule for updates|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 3|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 4|State: Enabled<br>**Transition** (Days): 2<br>**Snooze** (Days): 2<br>**Deadline** (Days): 5|
|
||||
|
||||
#### Controlling notification experience for engaged deadline
|
||||
|
||||
|Policy| Location |Suggested Configuration
|
||||
|-|-|-|
|
||||
|Configure Auto-restart required notification for updates |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Auto-restart required notification for updates|State: Enabled <br>**Method**: 2- User|
|
||||
|
||||
#### Notification experience for engaged deadlines
|
||||
|
||||
Notification users get for quality update engaged deadline:
|
||||
|
||||
|
||||
|
||||
Notification users get for a quality update deadline:
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update engaged deadline:
|
||||
|
||||
|
||||
|
||||
Notification users get for a feature update deadline:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user