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

More changes

Browse Source
This commit is contained in:
Andre Della Monica 2023-04-24 18:19:50 -05:00
parent ba046962e7
commit ed9ac90bbf
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites.md
View File

@ -44,13 +44,16 @@ Windows Autopatch is included with Windows 10/11 Enterprise E3 or higher (user-b
| [Windows 10/11 Enterprise E5](/azure/active-directory/enterprise-users/licensing-service-plan-reference) | WIN10_VDA_E5 | 488ba24a-39a9-4473-8ee5-19291e71b002 | | [Windows 10/11 Enterprise E5](/azure/active-directory/enterprise-users/licensing-service-plan-reference) | WIN10_VDA_E5 | 488ba24a-39a9-4473-8ee5-19291e71b002 |
| [Windows 10/11 Enterprise VDA](/windows/deployment/deploy-enterprise-licenses#virtual-desktop-access-vda) | E3_VDA_only | d13ef257-988a-46f3-8fce-f47484dd4550 | | [Windows 10/11 Enterprise VDA](/windows/deployment/deploy-enterprise-licenses#virtual-desktop-access-vda) | E3_VDA_only | d13ef257-988a-46f3-8fce-f47484dd4550 |
The following Windows OS 10 editions, 1809+ builds and architecture are supported in Windows Autopatch: The following Windows 10 editions, build version and architecture are supported to be [registered](windows-autopatch-register-devices) with Windows Autopatch:
- Windows 10 (1809+)/11 Pro - Windows 10 (1809+)/11 Pro
- Windows 10 (1809+)/11 Enterprise - Windows 10 (1809+)/11 Enterprise
- Windows 10 (1809+)/11 Pro for Workstations - Windows 10 (1809+)/11 Pro for Workstations
> [!IMPORTANT] > [!IMPORTANT]
> While Windows Autopatch supports registering devices below the [minimum Windows OS version enforced by the service](windows-autopatch-windows-feature-update-overview#enforcing-a-minimum-windows-os-version), once registered, devices are automatically offered with the [minimum windows OS version](windows-autopatch-windows-feature-update-overview#enforcing-a-minimum-windows-os-version) as these devices must be on a [minimum Windows OS currently serviced](https://learn.microsoft.com/windows/release-health/release-information?msclkid=ee885719baa511ecb838e1a689da96d2) by the Windows servicing channels to keep receiving monthly quality updates that are critical to security and the health of the Windows ecosystem.
> [!NOTE]
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC. > Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC.
## Configuration Manager co-management requirements ## Configuration Manager co-management requirements
@ -58,9 +61,9 @@ The following Windows OS 10 editions, 1809+ builds and architecture are supporte
Windows Autopatch fully supports co-management. The following co-management requirements apply: Windows Autopatch fully supports co-management. The following co-management requirements apply:
- Use a currently supported [Configuration Manager version](/mem/configmgr/core/servers/manage/updates#supported-versions). - Use a currently supported [Configuration Manager version](/mem/configmgr/core/servers/manage/updates#supported-versions).
- ConfigMgr must be [cloud-attached with Intune (co-management)](/mem/configmgr/cloud-attach/overview) and must have the following co-management workloads enabled: - Configuration Manager must be [cloud-attached with Intune (co-management)](/mem/configmgr/cloud-attach/overview) and must have the following co-management workloads enabled and set to either **Pilot Intune** or **Intune**:
- Set the [Windows Update policies workload](/mem/configmgr/comanage/workloads#windows-update-policies) to Pilot Intune or Intune. - [Windows Update policies workload](/mem/configmgr/comanage/workloads#windows-update-policies)
- Set the [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration) to Pilot Intune or Intune. - [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration)
- Set the [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps) to Pilot Intune or Intune. - [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps)
For more information, see [paths to co-management](/mem/configmgr/comanage/quickstart-paths). For more information, see [paths to co-management](/mem/configmgr/comanage/quickstart-paths).