Merge pull request #7390 from MicrosoftDocs/main

Publish 04/18/2022 3:30 PM PT

Author: Angela Fleischmann

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

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 04/06/2022
+ms.date: 04/18/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -60,7 +60,7 @@ The actual time that a device starts to update depends on the device being onlin
 
   If a device doesn’t restart before the deadline, the restart can happen in the middle of the working day. For more information on restart behavior, see [Enforcing compliance deadlines for updates](/windows/deployment/update/wufb-compliancedeadlines).
 
-- Expedite is not recommended for normal monthly quality update servicing. Instead, consider using the *deadline settings* from an Update rings for Windows 10 and later policy. For information, see *Use deadline settings* under the user experience settings in [Windows update settings](../protect/windows-update-settings.md#user-experience-settings).  
+- Expedite is not recommended for normal monthly quality update servicing. Instead, consider using the *deadline settings* from an Update ring for Windows 10 and later policy. For information, see *Use deadline settings* under the user experience settings in [Windows update settings](../protect/windows-update-settings.md#user-experience-settings).  
 
 ## Prerequisites
 
@@ -81,6 +81,8 @@ In addition to a license for Intune, your organization must have one of the foll
 **Supported Windows 10/11 versions**:
 
 - Windows 10/11 versions that remain in support for Servicing, on x86 or x64 architecture
+- 
+Only update builds that are generally available are supported. Preview builds, including the Beta and Dev channels, are not supported with expedited updates.
 
 **Supported Windows 10/11 editions**:
 
@@ -132,7 +134,7 @@ To help avoid conflicts or configurations that can block installation of expedit
 
 | Update ring setting       | Recommended value        |
 |---------------------------|-------------------------------------|
-| Servicing channel         | **Semi-Annual Channel**  <br><br> Expedite doesn't support additional channels at this time. |
+| Enable pre-release builds | This setting should be set to **Not configured**. Preview builds, including the Beta and Dev channels, are not supported with expedited updates. |
 | Automatic update behavior | **Reset to default**  <br><br> Other values might cause a poor user experience and  slow the process to expedite updates. |
 | Change notification update level | Use any value other than **Turn off all notifications, including restart warnings** |
 

memdocs/intune/protect/windows-10-update-rings.md

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 11/16/2021
+ms.date: 04/18/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -58,7 +58,9 @@ The following prerequisites must be met to use Windows updates for Windows 10/11
     Windows Holographic for Business supports a subset of settings for Windows updates, including:
     - **Automatic update behavior**
     - **Microsoft product updates**
-    - **Servicing channel**: Supports **Semi-annual channel** and **Semi-annual channel (Targeted)** options. For more information, see [Manage Windows Holographic](../fundamentals/windows-holographic-for-business.md).
+    - **Servicing channel**: Any update build that is generally available.
+
+    For more information, see [Manage Windows Holographic](../fundamentals/windows-holographic-for-business.md).
 
   > [!NOTE]
   > **Unsupported versions and editions**:  

memdocs/intune/protect/windows-update-compliance-reports.md

@@ -8,7 +8,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 10/06/2021
+ms.date: 04/18/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -180,11 +180,11 @@ To use the report:
        - **Admin paused** – The update is on hold because the Deployment being paused by an explicit Administrator action.
        - **ServicePaused** – The update is on hold because of an automatic action by Windows Update.
      - **Canceled**:
-       - **Admin Cancelled** – The update offer was cancelled by explicit Administrator action.
-       - **Service Cancelled** – The update was cancelled by Windows Update for one of the following reasons:  
+       - **Admin Cancelled** – The update offer was canceled by explicit Administrator action.
+       - **Service Cancelled** – The update was canceled by Windows Update for one of the following reasons:  
            - The *end of service* for the selected content was reached and it’s no longer offered by Windows Update. For example, the device might have been added to a deployment after the content’s availability expired, or the content reached its end of service date before it could install on the device.
            - The deployment content has been superseded for the device. This can happen when the device is targeted by another deployment that deploys newer content. For example, one deployment targets the Windows 10 device to install version 2004 and a second deployment targets that same device with version 21H1. In this event, 2004 is superseded by the 21H1 deployment and Windows Update cancels the 2004 deployment to the device.
-       - **Removed from Deployment** – The update offer was cancelled because it was removed from the Deployment by explicit Administrator action.
+       - **Removed from Deployment** – The update offer was canceled because it was removed from the Deployment by explicit Administrator action.
      - **Offering**:
        - **OfferReady** – The update is currently being offered to the device by Windows Update.
 
@@ -209,8 +209,8 @@ To use the report:
        - **Update Uninstalled** – The update successfully uninstalled.
        - **Rollback complete** – A rollback has completed.
      - **Cancelled**:
-       - **User Cancelled** – A user cancelled the update.
-       - **Device Cancelled** – The device cancelled the update for a user. This action is usually because the update no longer applies.
+       - **User Cancelled** – A user canceled the update.
+       - **Device Cancelled** – The device canceled the update for a user. This action is usually because the update no longer applies.
 
    - **Other**:
      - **Needs attention**: The device has some issue and needs attention.
@@ -253,7 +253,7 @@ The following list identifies Alert Messages, and suggested remediation actions:
 
 |Alert Message |Description  |Recommendation |
 |----|----|----|
-| **CancelledByUser** | User cancelled the update. | Retry the installation. |
+| **CancelledByUser** | User canceled the update. | Retry the installation. |
 | **DamagedMedia**  | The update file or the hard drive is damaged. | Run **Chkdsk /F** on the device with administrator privileges, then retry the update. |
 | **DeploymentConflict** | Device is in more than one deployment of the same update type. Only the first deployment assigned is effective. | Remove the device from any deployments that shouldn't apply. |
 | **DeviceRegistrationInvalidAzureADDeviceId**|The device isn't able to register or authenticate properly with Windows Update  because of an invalid Azure AD Device ID. | Check that the device is joined to the Azure Active Directory tenant making the request. |
@@ -274,9 +274,9 @@ The following list identifies Alert Messages, and suggested remediation actions:
 | **FileNotFound**  | The downloaded update files cannot be found. The Disk Cleanup utility or a non-Microsoft software cleaning tool might have removed the files during cleanup. | Download the update again, and then retry the installation. |
 | **Incompatible**  | The system doesn't meet the minimum requirements to install the update. | Review the *ScanResult.xml* file for **Block Type=Hard**. |
 | **IncompatibleArchitecture**| This update is for a different CPU architecture. | Make sure the target operating system architecture matches the host operating system architecture. |
-| **IncompatibleServicingChannel** | Device is in a servicing channel that is incompatible with a deployment to which the device belongs. | Configure the device's servicing channel to the Semi-Annual Channel. |
+| **IncompatibleServicingChannel** | Device is in a servicing channel that is incompatible with a deployment to which the device belongs. | Configure the device's servicing channel to a retail (Generally Available) update channel. |
 | **InstallAccessDenied** | Installer doesn't have permission to access or replace a file. The installer might have tried to replace a file that an antivirus, antimalware, or a backup program is currently scanning. | Retry the installation. |
-| **InstallCancelled** | The installation was cancelled. | Retry the installation. |
+| **InstallCancelled** | The installation was canceled. | Retry the installation. |
 | **InstallFileLocked** | Installer couldn't access a file that is already in use. The installer might have tried to replace a file that an antivirus, antimalware, or backup program is currently scanning. | Check the files under the *%SystemDrive%\$Windows.~bt* directory. Retry the installation. |
 | **InstallIssue**  | There was an issue installing the update. | Run **dism /online /cleanup-image /restorehealth** on the device with administrator privileges, then retry the update. If the commands fail, a reinstall of Windows might be required. |
 | **InstallIssueRedirection**| A known folder that doesn't support redirection to another drive might have been redirected to another drive. | Report this issue to Microsoft if this error is encountered more than a once. |