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

[IAMCloud_Curt]

Morning all,

 

Just a quick one I'd like to ask. Recently been setting up MDT 2013 Update 2 to push out Windows 10 Version 1511, build 10586.

 

I've created my capture image, which sysprepp'd and captured fine, then I imported the captured WIM file into my MDT share, created a task sequence..

 

Updated deployment share, replaced boot image in WDS and restarted the WDS service.

 

Then, PXE boot a machine, selected the Win10 Task Sequence, it installs the OS then reboots, logs in as Administrator as doesn't continue running any scripts and just sits on the desktop.

 

Had a look in the MDT monitoring and it always gets stuck at step 56 out of 93, then after a while the status changes to "Unresponsive"

 

Could anyone shed any light on this one for me?

[maark]

I have not got an answer but got similar problem - will let you know if I can fix it.

I can image a virtual machine ok - office 2016 and other applications install - this is with a pure operating system image not a capture.

On a physical machine it sticks at step 59 of 89 - no applications get installed.

It adds to domain ok and installs software from gpo but does not complete deployment.

[maark]

update on this - if I image a physical machine but give it a new name that does not exist in active directory then it images ok and installs applications such as office 2016. The machine joins domain ok and is created in computers folder.

So it does not like something in active directory probably - maybe the fact that I have classic shell allocated to the container machine was in.

[IAMCloud_Curt]

update on this - if I image a physical machine but give it a new name that does not exist in active directory then it images ok and installs applications such as office 2016. The machine joins domain ok and is created in computers folder.

So it does not like something in active directory probably - maybe the fact that I have classic shell allocated to the container machine was in.

This one isn't an Active Directory problem, it seems to not load the MDT scripts after installing the OS.

[IAMCloud_Curt]

https://www.youtube.com/watch?v=_OqKY9DUzCM

 

 

Hi guys, just bumping this thread. I've uploaded a video of the deployment process I am doing, could anyone let me know how to fix what's happening please?

 

I've also attached a screenshot from the MDT monitoring tool, and that is what happens everytime I try to deploy Windows 10.

 

Could this be my task sequence or answer file? If you need any information, just ask!

 

Much appreciated.

[themightymrp]

Is there a permissions error connecting to the deployment share maybe? Can you ping the server after you get into the desktop? Just wondering if it is struggling with network connectivity.

[IAMCloud_Curt]

Is there a permissions error connecting to the deployment share maybe? Can you ping the server after you get into the desktop? Just wondering if it is struggling with network connectivity.

I'll check this now mate

[IAMCloud_Curt]

Is there a permissions error connecting to the deployment share maybe? Can you ping the server after you get into the desktop? Just wondering if it is struggling with network connectivity.

 

 

Yeah ping is fine mate

[aj3094]

Anyone found the solution for this?

[IAMCloud_Curt]

Which bit you getting stuck on mate?

[aj3094]

when I deploy windows 10 the TS copies drivers, installing operating system, and restart and login to to local account after that TS wont continue it stops before state restore phase.Am I missing anything in WIndows 10 ? I went through BDD log(attached), but couldn't find anything.

[IAMCloud_Curt]

I think mine was NTFS permissions on the DeploymentShare$ - it's been a while. I did manage to fix it though, have you installed Windows 10 AIK kits and updated your deployment share, and put a new boot file into WDS?

[aj3094]

Yes I did. but no luck

[IAMCloud_Curt]

What are you deploying your TS too, a laptop or desktop?

[aj3094]

I tried both

[IAMCloud_Curt]

Ok, try injecting the net drivers into your WDS boot image.

 

You can use dism offline, you'll need to mount your image then inject the drivers that way. I'll try find a guide for you, but you can google

 

"Offline dism inject drivers wds"

[aj3094]

I know the process how to inject the drivers using DISM. But i have different hardware models, So I created selection profile.

But i will give a try.

[IAMCloud_Curt]

Not to do with MDT, you need to export your boot image from WDS, and inject the drivers into your WDS boot image then re-import it.

[Manny-Tech]

when I deploy windows 10 the TS copies drivers, installing operating system, and restart and login to to local account after that TS wont continue it stops before state restore phase.Am I missing anything in WIndows 10 ? I went through BDD log(attached), but couldn't find anything.

Where's your BDD log? I can't see it anywhere.

[DanArkless]

I had a similar issue, after completing our Windows 10 deployment it would sit on the local admin desktop and fail to continue to install anything more than the OS itself.

 

I rebuilt an entire new image, straight from an ISO from Volume Licensing site, installed all updates etc, and then created a unattend.xml by following the first section of this GUIDE under the ADK bit.

 

After this, my unattend file works perfectly and the task sequence handles the rest within MDT. My applications now install, the only thing I have different compared to my Windows 7 deployments is that I don't attach any profile to install drivers or packages under the task sequence.

 

Hope you've sorted it by now, let me know if you need anything more explaining.

[aj3094]

I am trying to capture Windows 10 image with MDT which is on Vm in HyperV. Capture task sequence is good. Also I used copy profile setting in MDT unattend.xml.

On VM:

Installed Windows 10 and created user account, did all the customization's and capture image.

When I deploy all the changes I made are gone.

So how can we make changes to default profile.

How did you capture the default settings?

[DanArkless]

It depends what settings you're changing, are they computer settings or personalised settings? Most settings which you may be changing may only be changeable via Group Policy afterwards with various different ways to do so.

 

--- I'm capturing my Win10 images on a physical machine with WDS and deploying through MDT so if there's any difference between the two I cannot give my opinion ---

[aj3094]

I am doing some personalized and uninstalling applications etc

[NetMan63]

Not sure if it helps, but we had the same original issue where MDT deployment (Win 10 EDU) would stall out after the OS installed. For us it was right after the joining the domain and the first restart. It would sit on the local admin desktop and you couldn't get it to launch LiteTouch to continue. Looked at all the logs and there were no errors anywhere.

 

Turns out the issue for us was that UAC was enabled and causing it not to launch. This was from our default workstation policy which had UAC enabled even for built-in administrator. I changed the policy settings up and restarted the machine and the imaging process picked right back up and finished! If yours isn't domain related, you can also try to disable UAC during your task sequence.

[THoege]

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?