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

Update windows-autopatch-groups-manage-autopatch-groups.md

Browse Source
This commit is contained in:
Tiara Quan 2023-05-08 07:32:03 -07:00 committed by GitHub
parent 15902826a4
commit 22df2b9514
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md
View File

@ -191,10 +191,10 @@ The Windows Autopatch team is aware that all device conflict scenarios listed be
- Custom to Cstom Autopatch group device conflict detection.
> [!TIP]
> Follow these two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview:
> Use the following two best practices to help minimize device conflict scenarios when using Autopatch groups during the public preview:
>
> - Review your software update deployment requirements thoroughly, and if your deployment requirements allow, try using the default Autopatch group as much as possible, instead of start creating custom Autopatch groups. You can customize the default Autopatch to have up to 15 deployment rings, and you can use your existing device-based Azure AD groups with custom update deployment cadences.
> - If creating custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with the Windows Autopatch service, and already belong to the default Autopatch group.
> - Review your software update deployment requirements thoroughly. If your deployment requirements allow, try using the Default Autopatch group as much as possible, instead of start creating Custom Autopatch groups. You can customize the Default Autopatch to have up to 15 deployment rings, and you can use your existing device-based Azure AD groups with custom update deployment cadences.
> - If creating Custom Autopatch groups, try to avoid using device-based Azure AD groups that have device membership overlaps with the devices that are already registered with Windows Autopatch, and already belong to the Default Autopatch group.
### Autopatch group Azure AD group remediator