deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-17 11:23:45 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #658 from MicrosoftDocs/autopilot

Browse Source 
Autopilot white glove update on network requirements
This commit is contained in:
jaimeo
2019-07-09 13:39:08 -07:00
committed by GitHub
parent 68907dfa34 f7faba404f
commit 49cfb485ee
3 changed files with 16 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.openpublishing.redirection.json
View File

@ -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",

3
windows/deployment/windows-autopilot/white-glove.md
View File

@ -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.