4 votesHerman van Drie supported this idea ·
Updating this item as there’s support for Windows 10 In-place upgrade using the Cloud Management Gateway – see https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1802
Adding this in case some folks missed it or Win 10 In-place upgrade addresses their requirement.
I recognize this it not full OS Deployment as there’s no WinPE phase (WinPE has no wireless stack)Herman van Drie commented
I already achieved this item with 802.1x auth support:
Uses Network Access account for EAP-MSCHAPv2 authentication on the wireless connection.
Whenever I can I'll publish the required coding on GitHub.
- WinRE media
- WiFi drivers
- C# application
- Network Access account configured in ConfigMgr that allows access to wireless network
Allows deployments over 802.1x Enteprise wireless networks using "Access content directly from a distribution point when needed by the running task sequence" option in deployment.
708 votesHerman van Drie commented
I would rather see that WiFi support (Wlan AutoConfig service) introduced into WinPE, which is already present in WinRE for Windows 10.
Also, I would love to see that OSD status messages are able to be delayed when connectivity is not present (yet) using a TS variable.
I was able to utilize WinRE with some coding of my own to allow OSD to fully run over wireless with deployment set to "Access content directly from a distribution point when needed by the running task sequence" so it would not require pre-caching.
See my tweet here: https://twitter.com/hvandrie/status/875303380977164288
In the corporate environment I work for this resulted in bare-metal installations using USB media as start up to boot WinPE media to initiate the deployment in less than 70-80 minutes using a 802.11ac network. Which was faster than fast ethernet!