mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
update manager metadata
This commit is contained in:
Aaron Czechowski
@ -8,7 +8,7 @@ ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: hathind
|
||||
ms.collection:
|
||||
- tier2
|
||||
@ -41,6 +41,6 @@ Your admin contacts will receive notifications about support request updates and
|
||||
1. Under **Tenant administration** in the **Windows Autopatch** section, select **Admin contacts**.
|
||||
1. Select **+Add**.
|
||||
1. Enter the contact details including name, email, phone number and preferred language. For a support ticket, the ticket's primary contact's preferred language will determine the language used for email communications.
|
||||
1. Select an [Area of focus](#area-of-focus) and enter details of the contact's knowledge and authority in the specified area of focus.
|
||||
1. Select an [Area of focus](#area-of-focus) and enter details of the contact's knowledge and authority in the specified area of focus.
|
||||
1. Select **Save** to add the contact.
|
||||
1. Repeat for each area of focus.
|
||||
|
||||
@ -8,7 +8,7 @@ ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: andredm7
|
||||
ms.collection:
|
||||
- highpri
|
||||
@ -67,7 +67,7 @@ As described in **step #4** in the previous [Detailed device registration workfl
|
||||
During the tenant enrollment process, Windows Autopatch creates two different deployment ring sets:
|
||||
|
||||
- [Service-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#service-based-deployment-rings)
|
||||
- [Software update-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#software-based-deployment-rings)
|
||||
- [Software update-based deployment ring set](../deploy/windows-autopatch-groups-overview.md#software-based-deployment-rings)
|
||||
|
||||
The following four Microsoft Entra ID assigned groups are used to organize devices for the service-based deployment ring set:
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: andredm7
|
||||
ms.collection:
|
||||
- highpri
|
||||
@ -123,7 +123,7 @@ You **can’t** rename the Default Autopatch group. However, you can rename a Cu
|
||||
|
||||
## Delete a Custom Autopatch group
|
||||
|
||||
You **can’t** delete the Default Autopatch group. However, you can delete a Custom Autopatch group.
|
||||
You **can’t** delete the Default Autopatch group. However, you can delete a Custom Autopatch group.
|
||||
|
||||
**To delete a Custom Autopatch group:**
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: andredm7
|
||||
ms.collection:
|
||||
- highpri
|
||||
|
||||
@ -8,7 +8,7 @@ ms.topic: conceptual
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: andredm7
|
||||
ms.collection:
|
||||
- highpri
|
||||
@ -20,7 +20,7 @@ ms.collection:
|
||||
> [!IMPORTANT]
|
||||
> This feature is in "public preview". It is being actively developed, and may not be complete. They're made available on a “Preview” basis. You can test and use these features in production environments and scenarios, and provide feedback.
|
||||
|
||||
One of the most expensive aspects of the software update management process is to make sure devices are always healthy to receive and report software updates for each software update release cycle.
|
||||
One of the most expensive aspects of the software update management process is to make sure devices are always healthy to receive and report software updates for each software update release cycle.
|
||||
|
||||
Having a way of measuring, quickly detecting and remediating when something goes wrong with on-going change management processes is important; it helps mitigate high Helpdesk ticket volumes, reduces cost, and improves overall update management results.
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: dougeby
|
||||
manager: aaroncz
|
||||
ms.reviewer: andredm7
|
||||
ms.collection:
|
||||
- highpri
|
||||
@ -31,7 +31,7 @@ Windows Autopatch can take over software update management control of devices th
|
||||
|
||||
### Windows Autopatch groups device registration
|
||||
|
||||
When you either create/edit a [Custom Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-custom-autopatch-groups) or edit the [Default Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-the-default-autopatch-group) to add or remove deployment rings, the device-based Microsoft Entra groups you use when setting up your deployment rings are scanned to see if devices need to be registered with the Windows Autopatch service.
|
||||
When you either create/edit a [Custom Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-custom-autopatch-groups) or edit the [Default Autopatch group](../deploy/windows-autopatch-groups-overview.md#about-the-default-autopatch-group) to add or remove deployment rings, the device-based Microsoft Entra groups you use when setting up your deployment rings are scanned to see if devices need to be registered with the Windows Autopatch service.
|
||||
|
||||
If devices aren’t registered, Autopatch groups starts the device registration process by using your existing device-based Microsoft Entra groups instead of the Windows Autopatch Device Registration group.
|
||||
|
||||
@ -152,7 +152,7 @@ Windows 365 Enterprise gives IT admins the option to register devices with the W
|
||||
1. In the left pane, select **Devices**.
|
||||
1. Navigate to Provisioning > **Windows 365**.
|
||||
1. Select Provisioning policies > **Create policy**.
|
||||
1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types).
|
||||
1. Provide a policy name and select **Join Type**. For more information, see [Device join types](/windows-365/enterprise/identity-authentication#device-join-types).
|
||||
1. Select **Next**.
|
||||
1. Choose the desired image and select **Next**.
|
||||
1. Under the **Microsoft managed services** section, select **Windows Autopatch**. Then, select **Next**. If the *Windows Autopatch (preview) can't manage your Cloud PCs until a Global Admin has finished setting it up.* message appears, you must [enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md) to continue.
|
||||
@ -200,7 +200,7 @@ Support is available either through Windows 365, or the Windows Autopatch Servic
|
||||
|
||||
- For Windows 365 support, see [Get support](/mem/get-support).
|
||||
- For Azure Virtual Desktop support, see [Get support](https://azure.microsoft.com/support/create-ticket/).
|
||||
- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request).
|
||||
- For Windows Autopatch support, see [Submit a support request](/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request).
|
||||
|
||||
## Device management lifecycle scenarios
|
||||
|
||||
|
||||
Reference in New Issue
Block a user