From 3b0cfd0adb5aa87780fdf2eff07e78da1153990b Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Thu, 2 Jun 2022 09:27:55 -0700 Subject: [PATCH] Changed FAQ format, updated FAQ cross-references, word clarity, updated hardware link. --- windows/deployment/windows-autopatch/TOC.yml | 2 +- .../windows-autopatch-register-devices.md | 21 ++-- .../deployment/windows-autopatch/index.yml | 2 +- .../windows-autopatch-support-request.md | 2 +- .../overview/windows-autopatch-faq.md | 65 ----------- .../overview/windows-autopatch-faq.yml | 106 ++++++++++++++++++ 6 files changed, 120 insertions(+), 78 deletions(-) delete mode 100644 windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md create mode 100644 windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index 871a52e791..97e466d258 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -7,7 +7,7 @@ - name: What is Windows Autopatch? href: overview/windows-autopatch-overview.md - name: FAQ - href: overview/windows-autopatch-faq.md + href: overview/windows-autopatch-faq.yml - name: Prepare href: prepare/index.md items: diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md index 31f250df19..bc01a30400 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -36,9 +36,10 @@ You must choose what devices to manage with Windows Autopatch by either adding t Windows Autopatch also supports the following Azure AD nested group scenarios: -- Azure AD groups synced up from: - - On-premises Active Directory groups (Windows server type). - - [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync). +Azure AD groups synced up from: + +- On-premises Active Directory groups (Windows server type). +- [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync). > [!IMPORTANT] > The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups. @@ -52,17 +53,17 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set - Windows 10/11 64-bit Enterprise edition 1809+. - Either hybrid or Azure AD joined (personal devices aren't supported). -- Managed by Microsoft Endpoint Manager - - Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management. - - Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune). - - Windows Updates policies - - Device configuration - - Office Click-to-run +- Managed by Microsoft Endpoint Manager. + - Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management. + - Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune). + - Windows updates policies + - Device configuration + - Office Click-to-run - Last Intune device check-in completed within the last 28 days. For more details on each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article. -## About Devices Ready and Not ready tabs +## About the Ready and Not ready tabs Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices. diff --git a/windows/deployment/windows-autopatch/index.yml b/windows/deployment/windows-autopatch/index.yml index 888ce01b0c..b99aeb0317 100644 --- a/windows/deployment/windows-autopatch/index.yml +++ b/windows/deployment/windows-autopatch/index.yml @@ -27,7 +27,7 @@ landingContent: - text: What is Windows Autopatch? url: ./overview/windows-autopatch-overview.md - text: Windows Autopatch FAQ - url: ./overview/windows-autopatch-faq.md + url: ./overview/windows-autopatch-faq.yml # Card (optional) - title: Articles and blog posts diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md index f6e0614363..06eeae4e4d 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md @@ -64,7 +64,7 @@ Once a support request is mitigated, it can no longer be edited. If a request ha ## Microsoft FastTrack -[Microsoft FastTrack](https://www.microsoft.com/en-us/fasttrack) offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. FastTrack Specialists can help customers work through the Windows Autopatch technical prerequisites described in the [FAQ](../overview/windows-autopatch-faq.md). For more information, visit the [FastTrack website](https://www.microsoft.com/en-ca/fasttrack?rtc=1). +[Microsoft FastTrack](https://www.microsoft.com/en-us/fasttrack) offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. FastTrack Specialists can help customers work through the Windows Autopatch technical prerequisites described in the [FAQ](../overview/windows-autopatch-faq.yml). For more information, visit the [FastTrack website](https://www.microsoft.com/en-ca/fasttrack?rtc=1). Customers who need help with Microsoft 365 workloads can sign in to https://fasttrack.microsoft.com/ with a valid Azure ID and submit a Request for Assistance. diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md deleted file mode 100644 index f42d4e4606..0000000000 --- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: FAQ -description: This article answers frequently asked questions about Windows Autopatch -ms.date: 05/30/2022 -ms.prod: w11 -ms.technology: windows -ms.topic: troubleshooting -ms.localizationpriority: medium -author: tiaraquan -ms.author: tiaraquan -manager: dougeby -msreviewer: hathind ---- - -# FAQ - -## General - -| Question | Answer | -| ----- | ----- | -| What Windows versions are supported? | Windows Autopatch works with all [supported versions of Windows 10 and Windows 11 Enterprise edition](/windows/release-health/supported-versions-windows-client). | -| What is the difference between Windows Update for Business and Windows Autopatch? | Windows Autopatch is a service that removes the need for organizations to plan and operate the update process.

Windows Autopatch moves the burden from your IT to Microsoft. Windows Autopatch uses [Windows Update for Business](/windows/deployment/update/deployment-service-overview) and other service components to update devices. Both are part of Windows Enterprise E3. | -| Is Windows 365 for Enterprise supported with Windows Autopatch? | Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.| -| Does Windows Autopatch support Windows Education (A3) or Windows Front Line Worker (F3) licensing? | Autopatch isn't available for 'A' or 'F' series licensing. | -| Will Windows Autopatch support local domain join Windows 10? | Windows Autopatch doesn't support local (on-premise) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Azure AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid). | -| Will Windows Autopatch be available for state and local government customers? | Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers. | - -## Requirements - -| Question | Answer | -| ----- | ----- | -| What are the prerequisites for Windows Autopatch? |

| -| What are the licensing requirements for Windows Autopatch? | | -| Are there hardware requirements for Windows Autopatch? | No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/whats-new/windows-11-requirements). Windows devices must be supported by your hardware OEM. | - -## Device registration - -| Question | Answer | -| ----- | ----- | -| Can Autopatch customers individually approve or deny devices? | No you can't individually approve or deny devices. Once a device is registered with Windows Autopatch, updates are rolled out to the devices according to its ring assignment. Individual device level control isn't supported. | - -## Update management - -| Question | Answer | -| ----- | ----- | -| What systems does Windows Autopatch update? |