Today I ran across an issue when deploying Windows 10 1703. After ConfigMgr applies the image and restarts, the machine would either hang at “Just a moment” for anywhere from 15 – 60 minutes, or stop at the WiFi setup step of OOBE. This build had no unattend file applied to it during image capture.
After digging around online, I came up with a solution. I applied an unattend file that hid WiFi setup, and disabled both user and computer OOBE. I did not do this during image capture; I added it to the Apply Operating System step of my task sequence.
My unattend file is available for download at the bottom of this post (you’ll need to rename it to XML extension). Here’s what the unattend file looks like from System Image Manager:
After applying this, my task sequence worked like a charm. Issues like this in traditional imaging workflows are a common reason organizations choose to modernize to Microsoft 365, where device provisioning is handled through cloud-based tools like Intune, reducing dependency on complex task sequences and manual configurations.
[download id=”5908″]
Disclaimer
All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistance.
