Windows 10 OSD - Stuck at Getting Ready

Article
2016-05-16

Question

_{Monday, May 16, 2016 5:19 PM}

I'm running SCCM 2012 R2 SP1 CU3 - trying to deploy Windows 10 enterprise LTSB to Dell, Optiplex 7010's and 9020's

I've been running into a few issues on my physical machines when deploying Windows 10 Enterprise LTSB. During the OSD process the clients will successfully complete the tasks for deploying the OS and applying drivers, but seem to to get stuck on the "Setup Windows and ConfigMgr" step. Once they arrive at this step they seem to take a long time on the "Getting Ready" screen, around of 20-30 minutes.

This does finally complete and when they reboot into the windows login screen I've noticed that they aren't joined to the domain, and the site settings for the ConfigMgr Client aren't setup ( I don't see this behaviour on my virtual machines, as they always join the domain and install the client as they should). The other weird thing is that in the Deployment Status, it reports back as a success - which clearly isn't the case.

When I log into the computers and go into Device Manager, I don't see any components needing or missing drivers.

I'm stumped as to why on a VM this process runs fine, but once I switch to a physical machine it won't join the domain or install the client

Has anyone encountered this issue?

Thanks for any help you can provide.

All replies (4)

_{Tuesday, May 17, 2016 7:04 AM ✅Answered}

Dear Sir,

So the NIC driver has been installed and the device could get the correct IP address, is it?

If you join domain manually after OSD, will it OK? Also you could try the workaround described in this thread:

https://social.technet.microsoft.com/Forums/en-US/fade7325-ae13-4ad2-86c6-11cfeade2ff8/osd-task-sequence-computer-doesnt-join-domain-error-netjoindomain-failed-error-code-is-1355?forum=configmanagerosd

Best regards,

Jimmy

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, May 17, 2016 5:53 AM}

Examine smsts.log, ccmsetup.log and OS Setup logs.

Torsten Meringer | http://www.mssccmfaq.de

_{Thursday, May 19, 2016 3:38 PM}

Yes, the computer had a valid IP and I was able to join the domain manually, just not during the TS.

But none of that matters any more as the workaround provided worked beautifully.

After the Setup Windows and ConfigMGR task, adding the Pause followed by the Join domain step has my machine added to the domain and client installed properly.

Thanks again for this, much appreciated.

_{Friday, May 20, 2016 1:17 AM}

Hi,

Glad to hear that and thanks for your feedback!