diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index cddcf257b4..1beb54d3f3 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -14983,6 +14983,56 @@ "redirect_document_id": true }, { +"source_path": "windows/deployment/windows-autopilot/windows-autopilot-requirements-network.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-requirements", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/windows-autopilot-requirements-licensing.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-requirements", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/windows-autopilot-requirements-configuration.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-requirements", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/user-driven-aad.md", +"redirect_url": "/windows/deployment/windows-autopilot/user-driven", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/user-driven-hybrid.md", +"redirect_url": "/windows/deployment/windows-autopilot/user-driven", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/intune-connector.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-requirements", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/windows-autopilot-reset-remote.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-reset", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/windows-autopilot-reset-local.md", +"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot-reset", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/configure-autopilot.md", +"redirect_url": "/windows/deployment/windows-autopilot/add-devices", +"redirect_document_id": true +}, +{ +"source_path": "windows/deployment/windows-autopilot/administer.md", +"redirect_url": "/windows/deployment/windows-autopilot/add-devices", +"redirect_document_id": true +}, +{ "source_path": "windows/hub/release-information.md", "redirect_url": "/windows/release-information", "redirect_document_id": true diff --git a/windows/deployment/windows-autopilot/profiles.md b/windows/deployment/windows-autopilot/profiles.md index 00c165f9cf..996f638c68 100644 --- a/windows/deployment/windows-autopilot/profiles.md +++ b/windows/deployment/windows-autopilot/profiles.md @@ -62,4 +62,4 @@ The following profile settings are available: ## Related topics -[Configure Autopilot deployment](configure-autopilot.md) +[Registering devices](add-devices.md) diff --git a/windows/deployment/windows-autopilot/troubleshooting.md b/windows/deployment/windows-autopilot/troubleshooting.md index d1afb698a0..258bab56a1 100644 --- a/windows/deployment/windows-autopilot/troubleshooting.md +++ b/windows/deployment/windows-autopilot/troubleshooting.md @@ -35,8 +35,8 @@ Regardless of whether performing user-driven or self-deploying device deployment For troubleshooting, key activities to perform are: -- Configuration. Has Azure Active Directory and Microsoft Intune (or an equivalent MDM service) been configured as specified in [Windows Autopilot configuration requirements](windows-autopilot-requirements-configuration.md)? -- Network connectivity. Can the device access the services described in [Windows Autopilot networking requirements](windows-autopilot-requirements-network.md)? +- Configuration. Has Azure Active Directory and Microsoft Intune (or an equivalent MDM service) been configured as specified in [Windows Autopilot configuration requirements](windows-autopilot-requirements.md)? +- Network connectivity. Can the device access the services described in [Windows Autopilot networking requirements](windows-autopilot-requirements.md)? - Autopilot OOBE behavior. Were only the expected out-of-box experience screens displayed? Was the Azure AD credentials page customized with organization-specific details as expected? - Azure AD join issues. Was the device able to join Azure Active Directory? - MDM enrollment issues. Was the device able to enroll in Microsoft Intune (or an equivalent MDM service)? @@ -85,7 +85,7 @@ On Windows 10 version 1703 and above, ETW tracing can be used to capture detaile ### Troubleshooting Azure AD Join issues -The most common issue joining a device to Azure AD is related to Azure AD permissions. Ensure [the correct configuration is in place](windows-autopilot-requirements-configuration.md) to allow users to join devices to Azure AD. Errors can also happen if the user has exceeded the number of devices that they are allowed to join, as configured in Azure AD. +The most common issue joining a device to Azure AD is related to Azure AD permissions. Ensure [the correct configuration is in place](windows-autopilot-requirements.md) to allow users to join devices to Azure AD. Errors can also happen if the user has exceeded the number of devices that they are allowed to join, as configured in Azure AD. Error code 801C0003 will typically be reported on an error page titled "Something went wrong". This error means that the Azure AD join failed. diff --git a/windows/deployment/windows-autopilot/user-driven.md b/windows/deployment/windows-autopilot/user-driven.md index 8ab5824c94..0b60714d75 100644 --- a/windows/deployment/windows-autopilot/user-driven.md +++ b/windows/deployment/windows-autopilot/user-driven.md @@ -67,7 +67,7 @@ To perform a user-driven hybrid AAD joined deployment using Windows Autopilot: - If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group. - The device must be running Windows 10, version 1809 or later. - The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user). -- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements-network.md). +- The device must be able to access the Internet, following the [documented Windows Autopilot network requirements](windows-autopilot-requirements.md). - The Intune Connector for Active Directory must be installed. - Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf. - If using Proxy, WPAD Proxy settings option must be enabled and configured.