deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 19:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Reviewing Andre's changes

Browse Source 
Reviewing Andre's changes. Made some corrections.
This commit is contained in:
Tiara Quan
2022-05-31 10:12:48 -07:00
committed by GitHub
parent 71e4ce24d1
commit 53fbd8b369
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
View File

@ -28,7 +28,7 @@ Windows Autopatch to take over software updates management of supported devices
You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service. You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
> [!TIP] > [!TIP]
> You can also use the **Discover Devices** button in either the Ready or Not Ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand. > You can also use the **Discover Devices** button in either the Ready or Not ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites: To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites:
@ -45,7 +45,7 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article. For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
## About Devices Ready and Not Ready tabs ## About Devices Ready and Not ready tabs
Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices. Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices.
@ -54,8 +54,8 @@ Windows Autopatch introduces a new user interface to help IT admins manage devic
| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. | | Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. |
| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.<p><p>Devices successfully registered and healthy don't show up in the Not ready tab. | | Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.<p><p>Devices successfully registered and healthy don't show up in the Not ready tab. |
> [!WARNING] > [!IMPORTANT]
> The **Not Ready** tab will not be available during the first week of the Public preview. > The **Not ready** tab will not be available during the first week of the public preview.
## Built-in roles required for device registration ## Built-in roles required for device registration