deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Being nit-picky.

Browse Source
This commit is contained in:
tiaraquan 2022-07-28 08:04:12 -07:00
parent 6e5559c925
commit a9265b070a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md
View File

@ -72,7 +72,7 @@ See the following detailed workflow diagram. The diagram covers the Windows Auto
3. **Pro Workstation** 3. **Pro Workstation**
5. If the device meets the operating system requirements, Windows Autopatch checks whether the device is either: 5. If the device meets the operating system requirements, Windows Autopatch checks whether the device is either:
1. **Only managed by Intune** 1. **Only managed by Intune**
1. If the device is only managed by Intune, the device is marked as **passed all prerequisites**. 1. If the device is only managed by Intune, the device is marked as **Passed all prerequisites**.
2. **Co-managed by both Configuration Manager and Intune** 2. **Co-managed by both Configuration Manager and Intune**
1. If the device is co-managed by both Configuration Manager and Intune, an additional prerequisite check is evaluated to determine if the device satisfies the co-management-enabled workloads required by Windows Autopatch to manage devices in a co-managed state. 1. If the device is co-managed by both Configuration Manager and Intune, an additional prerequisite check is evaluated to determine if the device satisfies the co-management-enabled workloads required by Windows Autopatch to manage devices in a co-managed state.
1. The required co-management workloads evaluated in this step are: 1. The required co-management workloads evaluated in this step are:
@ -93,7 +93,7 @@ See the following detailed workflow diagram. The diagram covers the Windows Auto
1. This group has all devices managed by Windows Autopatch. 1. This group has all devices managed by Windows Autopatch.
2. **Modern Workplace Devices Dynamic - Windows 10** 2. **Modern Workplace Devices Dynamic - Windows 10**
1. This group has all devices managed by Windows Autopatch and that have Windows 10 installed. 1. This group has all devices managed by Windows Autopatch and that have Windows 10 installed.
3. M**odern Workplace Devices Dynamic - Windows 11** 3. **Modern Workplace Devices Dynamic - Windows 11**
1. This group has all devices managed by Windows Autopatch and that have Windows 11 installed. 1. This group has all devices managed by Windows Autopatch and that have Windows 11 installed.
4. **Modern Workplace Devices - Virtual Machine** 4. **Modern Workplace Devices - Virtual Machine**
1. This group has all virtual devices managed by Windows Autopatch. 1. This group has all virtual devices managed by Windows Autopatch.
@ -103,8 +103,8 @@ See the following detailed workflow diagram. The diagram covers the Windows Auto
3. The Azure AD device ID of the device successfully registered is added into the Microsoft Cloud Managed Desktop Extension’s allowlist. Windows Autopatch installs the Microsoft Cloud Managed Desktop Extension agent once devices are registered, so the agent can communicate back to the Microsoft Cloud Managed Desktop Extension service. 3. The Azure AD device ID of the device successfully registered is added into the Microsoft Cloud Managed Desktop Extension’s allowlist. Windows Autopatch installs the Microsoft Cloud Managed Desktop Extension agent once devices are registered, so the agent can communicate back to the Microsoft Cloud Managed Desktop Extension service.
1. The agent is the **Modern Workplace - Autopatch Client setup** PowerShell script that was created during the Windows Autopatch tenant enrollment process. The script is executed once devices are successfully registered into the Windows Autopatch service. 1. The agent is the **Modern Workplace - Autopatch Client setup** PowerShell script that was created during the Windows Autopatch tenant enrollment process. The script is executed once devices are successfully registered into the Windows Autopatch service.
9. IT admins review the device registration status in both the **Ready** and **Not ready** tabs. 9. IT admins review the device registration status in both the **Ready** and **Not ready** tabs.
1. If the device was successfully registered, it shows up in the **Ready** tab. 1. If the device was successfully registered, the device shows up in the **Ready** tab.
2. If not, in the **Not ready** tab. 2. If not, the device shows up in the **Not ready** tab.
10. This is the end of the Windows Autopatch device registration workflow. 10. This is the end of the Windows Autopatch device registration workflow.
## Detailed prerequisite check workflow diagram ## Detailed prerequisite check workflow diagram