[mdt] Windows 10 Deployment (Getting stuck after OS Install)

[IAMCloud_Curt]

In your bootstrap/mdt.ini files does your service account you are using have permissions to put workstations on the domain?

 

I created a MDT_SVC user in my domain and made it a domain admin, had no problems after that..

 

Just make sure you tick "password never expires"

 

Let me know

[themightymrp]

This might help with the deployment stopping just after the OS install:

 

https://community.spiceworks.com/how_to/140735-mdt-8443-windows-10-1703-auto-login-bug-fix

[IAMCloud_Curt]

I am having a similar issue with no resolution so far. Ever since we started pushing Win10 the newly deployed machines refuse to join the domain, accept their assigned name and usually ignore the timezone. When I look at the monitoring in MDT it appears that all Win10 deployments stop at step 53 of 89, just after the OS install. I have tried modifying the Unattend file in different ways, with no luck. I tried recreating the image with the UAC just in case that was stopping something but no change. Does anyone have an idea about this?

Just had a thought - when naming your PC at the start of the Task Sequence, does that PC already belong in your domain? If so it will need deleted prior to running your MDT task.

 

Just remembered we had issues where PC existed it domain and caused task to freeze half way through.

 

Let me know if this sorts.

[Arthur]

This might help with the deployment stopping just after the OS install:

Alternative fix...

 

https://twitter.com/LordVacano/status/873652898214932482

 

It looks the workaround to the auto logon issue in 1703 is to add the "Admin Password" variable to the CS.ini file.

 

Add the 'AdminPassword' setting to MDTs CustomSettings.ini file (or better still set the admin password through a task sequence variable).

[THoege]

I was kind of thrown into this whole situation when our Engineer left, so this is all new to me, but I'll do my best to keep up with you all.

CBlunt: We use WDS with MDT, so as far as I know we don't input an administrative password until after the PXE. As for your other question, every name that I give a machine is also done with WDS and they have been brand new names.

themightymrp and Arthur: I will try giving the powershell script a shot. I did try adding the admin login to the unattend file to test but that didn't seem to change anything.

Sorry for leaving out the WDS information, I'm just piecing all this together as I go.

Thanks all.

 

UPDATE:

Tried creating the Auto Logon script but no change.

Edited June 12, 2017 by THoege

[maark]

Add the 'AdminPassword' setting to MDTs CustomSettings.ini file - this worked for me

[THoege]

Still no luck. The AdminPassword setting was already in the file which hasn't worked yet, though I was able to add the Time Zone setting into it which has fixed the smallest part of my problem. The only other thing I haven't messed with yet is creating a new WinPE boot image. Would that possibly make a difference?