Revisions

Author: v-tappelgate

support/windows-server/installing-updates-features-roles/known-issue-rollback.md

@@ -48,46 +48,46 @@ To find out if KIR can mitigate your regression issue, see [Ways for enterprises
 
 For the purpose of KIR activation, Windows devices belong to two different categories. Each category has its own process for activating KIR.
 
-- **Enterprise-managed devices:** Enterprise-managed devices are [update-managed Windows devices](/windows/deployment/update/update-managed-unmanaged-devices#what-are-update-managed-windows-devices). Microsoft provides a Group Policy (GP) template to the organization's IT administrator to activate KIR.
-- **Retail/consumer devices:** Retail/consumer devices refer to the devices not covered under [update-managed Windows devices](/windows/deployment/update/update-managed-unmanaged-devices#what-are-update-managed-windows-devices).These are typically the devices not managed by an IT admin. These devices receive policy changes for activating KIR through Microsoft managed Windows Update cloud service.
+- **Enterprise-managed devices:** Enterprise-managed devices are [update-managed Windows devices](/windows/deployment/update/update-managed-unmanaged-devices#what-are-update-managed-windows-devices). Microsoft provides a Group Policy template for the organization's IT administrator. To activate KIR, the IT administrator applies the template to the organization's Group Policy infrastructure.
+- **Retail and consumer devices:** Retail and consumer devices are devices that aren't considered update-managed Windows devices. Typically, these are devices that aren't managed by an IT admin. These devices receive policy changes for activating KIR through the Microsoft-managed Windows Update cloud service.
 
 ### KIR for Enterprise-managed devices
 
-As an enterprise IT admin for these devices, you're in control. In accordance with Microsoft policy, for enterprise-managed devices, Microsoft publishes a specific Group Policy (GP) template on the Download Center. You can download this Group Policy to configure and apply a rollback policy to activate KIR.
+As an enterprise IT admin for these devices, you're in control. In accordance with Microsoft policy, for enterprise-managed devices, Microsoft publishes a specific Group Policy template on the Download Center. You can download this Group Policy template, and then configure and apply the template to activate KIR.
 
-:::image type="content" source="media/known-issue-rollback/group-policy-download.png" alt-text="Screenshot of download group policy." lightbox="media/known-issue-rollback/group-policy-download.png":::
+:::image type="content" source="media/known-issue-rollback/enterprise-admin-downloads-kir-gp-template.png" alt-text="Diagram that shows how an administrator downloads a K.I.R. group policy template, integrates it into Group Policy for the enterprise, and then deploys the change to enterprise devices." lightbox="media/known-issue-rollback/enterprise-admin-downloads-kir-gp-template.png":::
 
 > [!NOTE]  
 > [Group Policy](/windows-server/identity/ad-ds/manage/group-policy/group-policy-overview) is a feature in Microsoft Windows that allows IT admins to centrally manage and configure operating system settings, applications, and user settings across devices in an Active Directory environment.
 
-The following steps describe the process to request a KIR activation for your organization:
+If you experience an issue that's related to a feature update, check the Download Center for a related KIR policy template. If you don't find one, follow these steps to request a KIR activation for your organization.
 
 1. Report the issue or regression to [Microsoft Support](https://support.serviceshub.microsoft.com/supportforbusiness/onboarding), the customer-facing arm of Microsoft, and request the Group Policy to activate KIR.
-1. Microsoft Support works with product teams to identify the applicable Group Policy, uploads it to the Download Center (DLC), and provides you with the link to download the same.
+1. Microsoft Support works with product teams to identify the applicable Group Policy settings, uploads an appropriate Group Policy template to the Download Center, and then provides you with the link to download the template.
 
-Once you receive the KIR Group Policy link, follow the steps in [How to use Group Policy to deploy a Known Issue Rollback](/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback).
+Download the template, and then follow the steps in [How to use Group Policy to deploy a Known Issue Rollback](/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback).
 
-For enterprise-managed devices that are domain joined, the Group Policy refresh happens at certain regular intervals. Choose one of the following actions to ensure the Group Policy takes effect:
+For enterprise-managed devices that are domain joined, the Group Policy refresh happens at certain regular intervals. Choose one of the following actions to make sure that the Group Policy settings take effect:
 
-- Wait for Group Policy to refresh in the background, then restart your device.
-- Run '**gpupdate /force**' from a command prompt, then restart your device.
+- Wait for Group Policy to refresh in the background, then restart the affected devices.
+- To force a single device to update its Group Policy settings, open a Command Prompt window on the device, and then run 'gpupdate /force'. After the command runs, restart the device.
 
-For more information on a Group Policy refresh, see [Group Policy processing for Windows](/windows-server/identity/ad-ds/manage/group-policy/group-policy-processing).
+For more information about refreshing Group Policy, see [Group Policy processing for Windows](/windows-server/identity/ad-ds/manage/group-policy/group-policy-processing).
 
-Additionally, for information on how to mitigate regressions on Intune or endpoint management service managed devices, see how to [Use Group Policy to deploy a Known Issue Rollback](/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback).
+Additionally, for information about how to mitigate regressions on Intune or endpoint management service managed devices, see [Use Group Policy to deploy a Known Issue Rollback](/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback).
 
-### KIR for Retail/consumer devices
+### KIR for retail and consumer devices
 
-For these devices, Microsoft activates KIR through Windows Update, and no action is needed from the user.
+For these devices, Microsoft activates KIR by using Windows Update. Users don't have to take any action.
 
 > [!NOTE]  
-> Any device that is not connected to Windows Update won't get Windows updates or KIR.
+> Any device that's not connected to Windows Update won't get Windows updates or KIR.
 
 When an issue or regression is identified in retail devices, Microsoft product teams gather detailed information about the problem and its impact, determine the root cause, and report the incident internally. Then based on the results of this analysis, Microsoft decides whether to roll back a regressing change. If required, Microsoft activates KIR through cloud services.
 
-:::image type="content" source="media/known-issue-rollback/retail-kir-activate.png" alt-text="Screenshot of KIR activation for retail." lightbox="media/known-issue-rollback/retail-kir-activate.png":::
+:::image type="content" source="media/known-issue-rollback/retail-kir-propagates-through-windows-update-service.png" alt-text="Diagram that shows how Microsoft distributes a K.I.R. by using the Windows Update infrastructure." lightbox="media/known-issue-rollback/retail-kir-propagates-through-windows-update-service.png":::
 
-Once Microsoft qualifies a regression for KIR activation, it makes a configuration update change in the cloud. All devices that get updates through **Settings** > **Windows Update** (WU) get notice of this change and receive the configuration update within 24 hours. Upon receiving and installing the update, the code causing the issue is disabled. In some cases, a device reboot might be required to disable the code.
+After Microsoft qualifies a regression for KIR activation, it makes a configuration update change in the cloud. All devices that get updates through **Settings** > **Windows Update** (WU) get notice of this change and receive the configuration update within 24 hours. Upon receiving and installing the update, the code causing the issue is disabled. In some cases, a device reboot might be required to disable the code.
 
 In accordance with Microsoft's safe deployment practices, in most cases, Microsoft identifies and publishes a rollback before user devices have the chance to even install the update containing the issue. Hence, most users never see the regression.