Skip to content

Commit 6ef8505

Browse files
committed
Updates to comanagement details
1 parent c844f27 commit 6ef8505

1 file changed

Lines changed: 12 additions & 2 deletions

File tree

memdocs/intune/protect/windows-10-feature-updates.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 10/04/2021
10+
ms.date: 12/07/2021
1111
ms.topic: how-to
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -102,7 +102,17 @@ The following are prerequisites for Intune's Feature updates for Windows 10 and
102102

103103
- If you co-manage devices with Configuration Manager, feature updates policies might not immediately take effect on devices when you newly configure the [Windows Update policies workload](../../configmgr/comanage/workloads.md#windows-update-policies) to Intune. This delay is temporary but can initially result in devices updating to a later feature update version than is configured in the policy.
104104

105-
To prevent this initial delay from impacting your co-managed devices, configure a [Feature updates for Windows 10 and later](../protect/windows-10-feature-updates.md) policy and target the policy to your devices before you configure them for co-management or you shift the Windows Update workload to Intune. You can validate whether a device is enrolled for the feature update profile by checking the [Windows feature update report](../protect/windows-update-compliance-reports.md#use-the-windows-10-and-later-feature-updates-organizational-report) under the Reporting node in the Microsoft Endpoint Management admin console.
105+
To prevent this initial delay from impacting your co-managed devices:
106+
107+
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
108+
2. Go to **Devices** > **Windows** > **Feature updates for Windows 10 and later** > **Create profile**.
109+
3. For **Deployment settings**, enter a meaningful name and a description for the policy. Then, Specify the feature update you want devices to be running.
110+
4. Complete the policy configuration, including assigning the policy to devices. The policy deploys to devices, though any device that already has the version you’ve selected, or a newer version, won’t be offered the update.
111+
112+
Monitor the report for the policy. To do so, go to **Reports** > **Windows Updates** > **Reports** Tab > **Feature Updates report**. Select the policy you created and then generate the report.
113+
114+
5. Devices that have a state of *OfferReady* or later, are enrolled for feature updates and protected from updating to anything newer than the update you specified in step 3. See, [Use the Windows 10 and later feature updates (Organizational) report](../protect/windows-update-compliance-reports#use-the-windows-10-and-later-feature-updates-organizational-report).
115+
6. With devices enrolled for updates and protected, you can safely change the *Windows Update policies* workload from Configuration Manager to Intune. See, [Switch workloads to Intune](../../configmgr/comanage/how-to-switch-workloads) in the co-management documentation.
106116

107117
- When the device checks in to the Windows Update service, the device's group membership is validated against the security groups assigned to the feature updates policy settings for any feature update holds.
108118

0 commit comments

Comments
 (0)