Files
windows-itpro-docs/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
Tiara Quan 6f477dd589 Update windows-autopatch-fix-issues.md
Updated the date.
2022-11-16 11:29:39 -08:00

6.5 KiB
Raw Blame History

title, description, ms.date, ms.prod, ms.technology, ms.topic, ms.localizationpriority, author, ms.author, manager, msreviewer
title description ms.date ms.prod ms.technology ms.topic ms.localizationpriority author ms.author manager msreviewer
Fix issues found by the Readiness assessment tool This article details how to fix issues found by the Readiness assessment tool 11/17/2022 windows-client itpro-updates how-to medium tiaraquan tiaraquan dougeby hathind

Fix issues found by the Readiness assessment tool

Seeing issues with your tenant? This article details how to remediate issues found with your tenant.

If you need more assistance with tenant enrollment, you can submit a tenant enrollment support request.

Check results

For each check, the tool will report one of four possible results:

Result Meaning
Ready No action is required before completing enrollment.
Advisory Follow the steps in the tool or this article for the best experience with enrollment and for users.

You can complete enrollment, but you must fix these issues before you deploy your first device.

Not ready You must fix these issues before enrollment. You wont be able to enroll into Windows Autopatch if you don't fix these issues. Follow the steps in the tool or this article to resolve them.
Error The Azure Active Directory (AD) role you're using doesn't have sufficient permission to run this check or your tenant isn't properly licensed for Microsoft Intune.

Note

The results reported by this tool reflect the status of your settings only at the time that you ran it. If you make changes later to policies in Microsoft Intune, Azure Active Directory (AD), or Microsoft 365, items that were "Ready" can become "Not ready". To avoid problems with Windows Autopatch operations, review the specific settings described in this article before you change any policies.

Microsoft Intune settings

You can access Intune settings at the Endpoint Manager admin center.

Unlicensed admins

This setting must be turned on to avoid a "lack of permissions" error when we interact with your Azure Active Directory (AD) organization.

Result Meaning
Not ready Allow access to unlicensed admins should be turned on. Without this setting enabled, errors can occur when we try to access your Azure AD organization for service. You can safely enable this setting without worrying about security implications. The scope of access is defined by the roles assigned to users, including our operations staff.

For more information, see Unlicensed admins.

Update rings for Windows 10 or later

Your "Windows 10 update ring" policy in Intune must not target any Windows Autopatch devices.

Result Meaning
Not ready You have an "update ring" policy that targets all devices, all users, or both.

To resolve, change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.

For more information, see Manage Windows 10 software updates in Intune.

Advisory Both the Modern Workplace Devices - All and Modern Workplace - All Azure AD groups are groups that we create after you enroll in Windows Autopatch.

You can continue with enrollment. However, you must resolve the advisory prior to deploying your first device. To resolve the advisory, see Maintain the Windows Autopatch environment.

Azure Active Directory settings

You can access Azure Active Directory (AD) settings in the Azure portal.

Co-management

Co-management enables you to concurrently manage Windows 10 or later devices by using both Configuration Manager and Microsoft Intune.

Result Meaning
Advisory To successfully enroll devices that are co-managed into Windows Autopatch, it's necessary that the following co-managed workloads are set to Intune:
  • Device configuration
  • Windows update policies
  • Office 365 client apps

If co-management doesn't apply to your tenant, this check can be safely disregarded, and it won't block device deployment.

Licenses

Windows Autopatch requires the following licenses:

Result Meaning
Not ready Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, and Microsoft Intune are required. For more information, see more about licenses.

Submit a support request

Important

Make sure you've added and verified your admin contacts. The Windows Autopatch Service Engineering Team will contact these individuals for assistance with troubleshooting issues.

If you need more assistance with tenant enrollment, you can submit support tickets to the Windows Autopatch Service Engineering Team in the Windows Autopatch enrollment tool. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.

To submit a new support request:

  1. If the Readiness assessment tool fails, remediation steps can be found by selecting View details under Management settings and then selecting the individual check. The Contact Support button will be available below remediation instructions in the fly-in-pane.
  2. Enter your question(s) and/or a description of the problem.
  3. Review all the information you provided for accuracy.
  4. When you're ready, select Create.

Manage an active support request

The primary contact for the support request will receive email notifications when a case is created, assigned to a service engineer to investigate, and mitigated. If you have a question about the case, the best way to get in touch is to reply directly to one of the emails. If we have questions about your request or need more details, we'll email the primary contact listed in the support request.

To view all your active pre-enrollment support requests:

  1. Sign into the Endpoint Manager admin center and navigate to the Tenant Administration menu.
  2. In the Windows Autopatch section, select Tenant Enrollment.
  3. Select the Support history tab. You can view the list of all support cases, or select an individual case to view the details.