From ff49c2efa5c9a9efec80b02a708aa461b6b3d28c Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Thu, 26 Sep 2024 09:52:59 -0700 Subject: [PATCH 1/2] Updated Move devices between deployment rings --- .../windows-autopatch-register-devices.md | 20 +++++++++---------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md index a0a59d054a..c2b584ffa3 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -1,7 +1,7 @@ --- title: Register your devices description: This article details how to register devices in Autopatch. -ms.date: 09/16/2024 +ms.date: 09/26/2024 ms.service: windows-client ms.subservice: autopatch ms.topic: how-to @@ -66,7 +66,7 @@ Once a device is registered to the service, a readiness status is displayed. Eac #### Readiness statuses -| Autopatch readiness status in the Devices report | Sub-status description | +| Autopatch readiness status in the Devices report | Substatus description | | --- | --- | | Registered | | | Not registered | | @@ -82,7 +82,7 @@ You can view the excluded devices in the Not registered tab to make it easier fo ## Move devices in between deployment rings -If you want to move devices to different deployment rings after Windows Autopatch's deployment ring assignment, you can repeat the following steps for one or more devices from the **Devices report**. +If you want to move devices to different deployment rings after Windows Autopatch's deployment ring assignment, you can repeat the following steps for one or more devices. > [!IMPORTANT] > **You can only move devices in between deployment rings within the same Autopatch group**. You can't move devices in between deployment rings across different Autopatch groups. If you try to select a device that belongs to one Autopatch group, and another device that belongs to a different Autopatch group, you'll receive the following error message on the top right corner of the Microsoft Intune portal: **An error occurred. Please select devices within the same Autopatch group**. @@ -93,15 +93,13 @@ If you want to move devices to different deployment rings after Windows Autopatc > You can only move devices to other deployment rings when the device's Autopatch readiness status appears as **Registered** and the Update status is **Active**. 1. In the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** in the left pane. -1. Under **Manage updates** section, select **Windows updates**. -1. In the **Devices report**, select one or more devices you want to assign. All selected devices are assigned to the deployment ring you specify. -1. Select **Device actions** from the menu. -1. Select **Assign ring**. A fly-in opens. -1. Use the dropdown menu to select the deployment ring to move devices to, and then select **Save**. The Ring assigned by column changes to **Pending**. -1. When the assignment is complete, the **Ring assigned by** column changes to Admin (which indicates that you made the change) and the **Ring** column shows the new deployment ring assignment. +1. Navigate to **Windows updates** > **Monitor** > **Autopatch devices**. +1. Select one or more devices you want to assign and select **Assign ring**. +1. Use the dropdown menu to select the deployment ring to move devices to, and then select **Save**. All selected devices are assigned to the deployment ring you specify. The "1 devices scheduled for assignment" notification appears. +1. When the assignment is complete, the **Ring assigned by** column changes to Admin (which indicates that you made the change) and the **Ring** column shows the new deployment ring assignment. The **Ring assigned by** column is only visible in the fly-in menu. > [!WARNING] -> Moving devices between deployment rings through directly changing Microsoft Entra group membership isn't supported and might cause unintended configuration conflicts within the Windows Autopatch service. To avoid service interruption to devices, use the **Assign device to ring** action described previously to move devices between deployment rings. +> Moving devices between deployment rings through directly changing Microsoft Entra group membership isn't supported and might cause unintended configuration conflicts within the Windows Autopatch service. To avoid service interruption to devices, use the **Assign ring** action described previously to move devices between deployment rings. ## Register devices into Autopatch groups @@ -211,7 +209,7 @@ The device is rejoined to Microsoft Entra ID (either Hybrid or Microsoft Entra-o ### Device repair and hardware replacement -If you need to repair a device that was previously registered into the Windows Autopatch service, by replacing the motherboard, nonremovable network interface cards (NIC) or hard drive, you must re-register the device into the Windows Autopatch service, because a new hardware ID is generated when there are major hardware changes, such as: +If you need to repair a device that was previously registered into the Windows Autopatch service, by replacing the motherboard, nonremovable network interface cards (NIC), or hard drive, you must re-register the device into the Windows Autopatch service, because a new hardware ID is generated when there are major hardware changes, such as: - SMBIOS UUID (motherboard) - MAC address (nonremovable NICs) From f082262ed5f9b2c6ca00f844b1bd48d01e778cfb Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Thu, 26 Sep 2024 13:33:46 -0400 Subject: [PATCH 2/2] updated references across all WHfB docs --- .../hello-for-business/deploy/cloud-only.md | 2 +- .../hello-for-business/deploy/hybrid-cert-trust-enroll.md | 4 ++-- .../hello-for-business/deploy/hybrid-cloud-kerberos-trust.md | 2 +- .../hello-for-business/deploy/hybrid-key-trust-enroll.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/deploy/cloud-only.md b/windows/security/identity-protection/hello-for-business/deploy/cloud-only.md index d7e4822aaa..553251974a 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/cloud-only.md +++ b/windows/security/identity-protection/hello-for-business/deploy/cloud-only.md @@ -54,7 +54,7 @@ Follow the instructions below to configure your devices using either Microsoft I | Category | Setting name | Value | |--|--|--| -| **Windows Hello for Business** | Use Passport For Work | true | +| **Windows Hello for Business** | Use Windows Hello For Business | true | | **Windows Hello for Business** | Require Security Device | true | [!INCLUDE [intune-settings-catalog-2](../../../../../includes/configure/intune-settings-catalog-2.md)] diff --git a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cert-trust-enroll.md b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cert-trust-enroll.md index e2e4402d37..436f28fe2d 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cert-trust-enroll.md +++ b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cert-trust-enroll.md @@ -1,7 +1,7 @@ --- title: Configure and enroll in Windows Hello for Business in hybrid certificate trust model description: Learn how to configure devices and enroll them in Windows Hello for Business in a hybrid certificate trust scenario. -ms.date: 06/23/2024 +ms.date: 09/26/2024 ms.topic: tutorial --- @@ -73,7 +73,7 @@ If the Intune tenant-wide policy is enabled and configured to your needs, you ca | Category | Setting name | Value | |--|--|--| -| **Windows Hello for Business** | Use Passport For Work | true | +| **Windows Hello for Business** | Use Windows Hello For Business | true | | **Windows Hello for Business** | Use Certificate For On Prem Auth | Enabled | | **Windows Hello for Business** | Require Security Device | true | diff --git a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md index 136b0f615d..c547b535eb 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md +++ b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md @@ -83,7 +83,7 @@ If the Intune tenant-wide policy is enabled and configured to your needs, you on | Category | Setting name | Value | |--|--|--| -| **Windows Hello for Business** | Use Passport For Work | true | +| **Windows Hello for Business** | Use Windows Hello For Business | true | | **Windows Hello for Business** | Use Cloud Trust For On Prem Auth | Enabled | | **Windows Hello for Business** | Require Security Device | true | diff --git a/windows/security/identity-protection/hello-for-business/deploy/hybrid-key-trust-enroll.md b/windows/security/identity-protection/hello-for-business/deploy/hybrid-key-trust-enroll.md index de3ffd9240..c97ec8cde9 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/hybrid-key-trust-enroll.md +++ b/windows/security/identity-protection/hello-for-business/deploy/hybrid-key-trust-enroll.md @@ -38,7 +38,7 @@ If the Intune tenant-wide policy is enabled and configured to your needs, you ca | Category | Setting name | Value | |--|--|--| -| **Windows Hello for Business** | Use Passport For Work | true | +| **Windows Hello for Business** | Use Windows Hello For Business | true | | **Windows Hello for Business** | Require Security Device | true | [!INCLUDE [intune-settings-catalog-2](../../../../../includes/configure/intune-settings-catalog-2.md)]