mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 03:13:44 +00:00
Merge pull request #658 from MicrosoftDocs/autopilot
Autopilot white glove update on network requirements
This commit is contained in:
@ -6503,7 +6503,7 @@
|
|||||||
{
|
{
|
||||||
"source_path": "store-for-business/app-inventory-management-windows-store-for-business.md",
|
"source_path": "store-for-business/app-inventory-management-windows-store-for-business.md",
|
||||||
"redirect_url": "/microsoft-store/app-inventory-management-microsoft-store-for-business",
|
"redirect_url": "/microsoft-store/app-inventory-management-microsoft-store-for-business",
|
||||||
"redirect_document_id": true
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/manage/application-development-for-windows-as-a-service.md",
|
"source_path": "windows/manage/application-development-for-windows-as-a-service.md",
|
||||||
|
@ -26,20 +26,20 @@ Windows Autopilot is designed to simplify all parts of the Windows device lifecy
|
|||||||
|
|
||||||
Regardless of whether performing user-driven or self-deploying device deployments, the troubleshooting process is the mostly the same. It is useful to understand the flow for a specific device:
|
Regardless of whether performing user-driven or self-deploying device deployments, the troubleshooting process is the mostly the same. It is useful to understand the flow for a specific device:
|
||||||
|
|
||||||
- Network connection established. This can be a wireless (Wi-fi) or wired (Ethernet) connection.
|
- Network connection established. This can be a wireless (Wi-fi) or wired (Ethernet) connection.
|
||||||
- Windows Autopilot profile downloaded. Whether using a wired connection or manually establishing a wireless connection, the Windows Autopilot profile will be downloaded from the Autopilot deployment service as soon as the network connection is in place.
|
- Windows Autopilot profile downloaded. Whether using a wired connection or manually establishing a wireless connection, the Windows Autopilot profile will be downloaded from the Autopilot deployment service as soon as the network connection is in place.
|
||||||
- User authentication. When performing a user-driven deployment, the user will enter their Azure Active Directory credentials, which will be validated.
|
- User authentication. When performing a user-driven deployment, the user will enter their Azure Active Directory credentials, which will be validated.
|
||||||
- Azure Active Directory join. For user-driven deployments, the device will be joined to Azure AD using the specified user credentials. For self-deploying scenarios, the device will be joined without specifying any user credentials.
|
- Azure Active Directory join. For user-driven deployments, the device will be joined to Azure AD using the specified user credentials. For self-deploying scenarios, the device will be joined without specifying any user credentials.
|
||||||
- Automatic MDM enrollment. As part of the Azure AD join process, the device will enroll in the MDM service configured in Azure AD (e.g. Microsoft Intune).
|
- Automatic MDM enrollment. As part of the Azure AD join process, the device will enroll in the MDM service configured in Azure AD (e.g. Microsoft Intune).
|
||||||
- Settings are applied. If the [enrollment status page](enrollment-status.md) is configured, most settings will be applied while the enrollment status page is displayed. If not configured or available, settings will be applied after the user is signed in.
|
- Settings are applied. If the [enrollment status page](enrollment-status.md) is configured, most settings will be applied while the enrollment status page is displayed. If not configured or available, settings will be applied after the user is signed in.
|
||||||
|
|
||||||
For troubleshooting, key activities to perform are:
|
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.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)?
|
- 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?
|
- 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?
|
- 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)?
|
- MDM enrollment issues. Was the device able to enroll in Microsoft Intune (or an equivalent MDM service)?
|
||||||
|
|
||||||
## Troubleshooting Autopilot OOBE issues
|
## Troubleshooting Autopilot OOBE issues
|
||||||
|
|
||||||
|
@ -38,6 +38,9 @@ In addition to [Windows Autopilot requirements](windows-autopilot-requirements.m
|
|||||||
- Physical devices that support TPM 2.0 and device attestation; virtual machines are not supported. The white glove provisioning process leverages Windows Autopilot self-deploying capabilities, hence the TPM 2.0 requirements.
|
- Physical devices that support TPM 2.0 and device attestation; virtual machines are not supported. The white glove provisioning process leverages Windows Autopilot self-deploying capabilities, hence the TPM 2.0 requirements.
|
||||||
- Physical devices with Ethernet connectivity; Wi-fi connectivity is not supported due to the requirement to choose a language, locale, and keyboard to make that Wi-fi connection; doing that in a pre-provisioning process could prevent the user from choosing their own language, locale, and keyboard when they receive the device.
|
- Physical devices with Ethernet connectivity; Wi-fi connectivity is not supported due to the requirement to choose a language, locale, and keyboard to make that Wi-fi connection; doing that in a pre-provisioning process could prevent the user from choosing their own language, locale, and keyboard when they receive the device.
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>Because the OEM or vendor performs the white glove process, this <u>doesn’t require access to an end-user's on-prem domain infrastructure</u>. This is unlike a typical hybrid Azure AD-joined scenario because rebooting the device is postponed. The device is resealed prior to the time when connectivity to a domain controller is expected, and the domain network is contacted when the device is unboxed on-prem by the end-user.
|
||||||
|
|
||||||
## Preparation
|
## Preparation
|
||||||
|
|
||||||
Devices slated for WG provisioning are registered for Autopilot via the normal registration process.
|
Devices slated for WG provisioning are registered for Autopilot via the normal registration process.
|
||||||
|
Reference in New Issue
Block a user