mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into uc-wkbk
This commit is contained in:
Meghan Stewart
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Register your devices
|
||||
description: This article details how to register devices in Autopatch
|
||||
ms.date: 07/06/2022
|
||||
ms.date: 08/04/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: how-to
|
||||
@ -21,13 +21,14 @@ Before Microsoft can manage your devices in Windows Autopatch, you must have dev
|
||||
Windows Autopatch can take over software update management of supported devices as soon as an IT admin decides to have their tenant managed by the service. The Windows Autopatch software update management scope includes:
|
||||
|
||||
- [Windows quality updates](../operate/windows-autopatch-wqu-overview.md)
|
||||
- [Windows feature updates](../operate/windows-autopatch-fu-overview.md)
|
||||
- [Microsoft 365 Apps for enterprise updates](../operate/windows-autopatch-microsoft-365-apps-enterprise.md)
|
||||
- [Microsoft Edge updates](../operate/windows-autopatch-edge.md)
|
||||
- [Microsoft Teams updates](../operate/windows-autopatch-teams.md)
|
||||
|
||||
### About the use of an Azure AD group to register devices
|
||||
|
||||
You must choose what devices to manage with Windows Autopatch by either adding them through direct membership or by nesting other Azure AD dynamic/assigned groups into the **Windows Autopatch Device Registration** Azure AD assigned group. Windows Autopatch automatically runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices.
|
||||
You must choose what devices to manage with Windows Autopatch by either adding them through direct membership or by nesting other Azure AD dynamic/assigned groups into the **Windows Autopatch Device Registration** Azure AD assigned group. Windows Autopatch automatically runs its discover devices function every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices.
|
||||
|
||||
> [!NOTE]
|
||||
> Devices that are intended to be managed by the Windows Autopatch service **must** be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device ID. Windows Autopatch scans the Azure AD group hourly to discover newly added devices to be registered. You can also use the **Discover devices** button in either the Ready or Not ready tab to register devices on demand.
|
||||
@ -48,7 +49,7 @@ Azure AD groups synced up from:
|
||||
> The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.
|
||||
|
||||
> [!TIP]
|
||||
> You can also use the **Discover Devices** button in either the Ready or Not ready tab 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 tab to discover devices from the **Windows Autopatch Device Registration** Azure AD group on demand.
|
||||
|
||||
### Clean up dual state of Hybrid Azure AD joined and Azure registered devices in your Azure AD tenant
|
||||
|
||||
@ -78,7 +79,7 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
|
||||
> [!NOTE]
|
||||
> Windows Autopatch doesn't support device emulators that don't generate Serial number, Model and Manufacturer. Devices that use a non-supported device emulator fail the **Intune or Cloud-Attached** pre-requisite check. Additionally, devices with duplicated serial numbers will fail to register with Windows Autopatch.
|
||||
|
||||
See [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md) for more details.
|
||||
For more information, see [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md).
|
||||
|
||||
## About the Ready and Not ready tabs
|
||||
|
||||
@ -111,7 +112,7 @@ Registering your devices in Windows Autopatch does the following:
|
||||
|
||||
## Steps to register devices
|
||||
|
||||
### Physical devices
|
||||
Any device (either physical or virtual) that contains an Azure AD device ID can be added into the **Windows Autopatch Device Registration** Azure AD group to be registered with Windows Autopatch.
|
||||
|
||||
**To register physical devices into Windows Autopatch:**
|
||||
|
||||
@ -126,15 +127,9 @@ Registering your devices in Windows Autopatch does the following:
|
||||
|
||||
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices, and runs software-based prerequisite checks to try to register them with its service.
|
||||
|
||||
### Virtual devices
|
||||
### Windows Autopatch on Windows 365 Enterprise Workloads
|
||||
|
||||
#### Windows Autopatch on Windows 365 Enterprise Workloads
|
||||
|
||||
With Windows 365 Enterprise, you can include Windows Autopatch onboarding as part of your provision process providing a seamless experience for admins and users to ensure your Cloud PCs are always up to date.
|
||||
|
||||
#### Deploy Windows Autopatch on a Windows 365 Provisioning Policy
|
||||
|
||||
For general guidance, see [Create a Windows 365 Provisioning Policy](/windows-365/enterprise/create-provisioning-policy).
|
||||
With Windows 365 Enterprise, IT admins are given the option to register devices with the Windows Autopatch service as part of the Windows 365 provisioning policy creation. This option provides a seamless experience for admins and users to ensure your Cloud PCs are always up to date. When IT admins decide to manage their Windows 365 Cloud PCs with Windows Autopatch, the Windows 365 provisioning policy creation process calls Windows Autopatch device registration APIs to register devices on behalf of the IT admin.
|
||||
|
||||
**To deploy Windows Autopatch on a Windows 365 Provisioning Policy:**
|
||||
|
||||
@ -149,20 +144,22 @@ For general guidance, see [Create a Windows 365 Provisioning Policy](/windows-36
|
||||
1. Assign your policy accordingly and select **Next**.
|
||||
1. Select **Create**. Now your newly provisioned Windows 365 Enterprise Cloud PCs will automatically be enrolled and managed by Windows Autopatch.
|
||||
|
||||
For general guidance, see [Create a Windows 365 Provisioning Policy](/windows-365/enterprise/create-provisioning-policy).
|
||||
|
||||
#### Deploy Autopatch on Windows 365 for existing Cloud PC
|
||||
|
||||
All your existing Windows 365 Enterprise workloads can be registered into Windows Autopatch by leveraging the same method as your physical devices. For more information, see [Physical devices](#physical-devices).
|
||||
All your existing Windows 365 Enterprise workloads can be registered into Windows Autopatch by leveraging the same method for any other physical or virtual device. See [steps to register devices](#steps-to-register-devices) for more details.
|
||||
|
||||
#### Contact support
|
||||
### Contact support for device registration-related incidents
|
||||
|
||||
Support is available either through Windows 365, or Windows Autopatch for update related incidents.
|
||||
Support is available either through Windows 365, or the Windows Autopatch Service Engineering team for device registration-related incidents.
|
||||
|
||||
- For Windows 365 support, see [Get support](/mem/get-support).
|
||||
- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request).
|
||||
|
||||
## Device management lifecycle scenarios
|
||||
|
||||
There's a few more device lifecycle management scenarios to consider when planning to register devices in Windows Autopatch.
|
||||
There's a few more device management lifecycle scenarios to consider when planning to register devices in Windows Autopatch.
|
||||
|
||||
### Device refresh
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Prerequisites
|
||||
description: This article details the prerequisites needed for Windows Autopatch
|
||||
ms.date: 06/30/2022
|
||||
ms.date: 08/04/2022
|
||||
ms.prod: w11
|
||||
ms.technology: windows
|
||||
ms.topic: conceptual
|
||||
@ -41,7 +41,6 @@ Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. The fol
|
||||
|
||||
The following Windows OS 10 editions, 1809 builds and architecture are supported in Windows Autopatch:
|
||||
|
||||
- x64 architecture
|
||||
- Windows 10 (1809+)/11 Pro
|
||||
- Windows 10 (1809+)/11 Enterprise
|
||||
- Windows 10 (1809+)/11 Pro for Workstations
|
||||
@ -51,8 +50,9 @@ The following Windows OS 10 editions, 1809 builds and architecture are supported
|
||||
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).
|
||||
- Ensure ConfigMgr is connected to the internet and [cloud-attach with Intune](/mem/configmgr/cloud-attach/overview).
|
||||
- Ensure ConfigMgr is co-managed. For more information, see [Paths to co-management](/mem/configmgr/comanage/quickstart-paths).
|
||||
- Set the [Windows Update workload](/mem/configmgr/comanage/workloads#windows-update-policies) to Pilot Intune or Intune.
|
||||
- Set the [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration) to Pilot Intune or Intune.
|
||||
- Set the [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps) to Pilot Intune or Intune.
|
||||
- ConfigMgr must be [cloud-attached with Intune (Co-management)](/mem/configmgr/cloud-attach/overview) and must have the following Co-management workloads enabled:
|
||||
- Set the [Windows Update workload](/mem/configmgr/comanage/workloads#windows-update-policies) to Pilot Intune or Intune.
|
||||
- Set the [Device configuration workload](/mem/configmgr/comanage/workloads#device-configuration) to Pilot Intune or Intune.
|
||||
- Set the [Office Click-to-Run apps workload](/mem/configmgr/comanage/workloads#office-click-to-run-apps) to Pilot Intune or Intune.
|
||||
|
||||
For more information, see [paths to co-management](/mem/configmgr/comanage/quickstart-paths).
|
||||
|
||||
Reference in New Issue
Block a user