MDT error - windows 10 20h2

[steveg]

I've had MDT / WDS working well for a couple of years deploying a fat image (primary school, lots of awkward software). Recently I have updated the image to windows 10 20H2 and re-captured a new wim. When i try and deploy this now it consistently fails, with the same error message.

 

I have tried deploying to a physical machine and a test VM. The image seems ok, if I manually deploy it using DISM from a usb stick it works fine (just no drivers obviously)

 

The error I'm getting is:

 

ERROR - Unable to map a network drive to \\DEPLOY1\Deploymentshare

Unable to connect to the deployment share \\DEPLOY1\Deploymentshare

Connection OK. Possible cause: invalid credentials.

FAILURE ( 5624 ): 5 Run DISMM: /Apply-Image /ImageFile:"\\DEPLOY1\CLientDeploymentShare$\Operating Systems\20h2customfat\newcap.wim" /index:1 /ApplyDir:D:

Litetouch deployment failed, Return Code = -2147467259 0x80004005

FAILURE (5206 ): The Deployment Wizard was cancelled or did not complete successfully. The Deployment will not proceed.

 

At this point I can open up a command prompt and check I have an ip and map a network drive to the paths mentioned above with no problems. I don't think it is a communications issue.

 

I have installed the latest version of adk, adk PE and MDT. I have update the deployment shares and re-generated the boot images. When i import these into WDS they are showing as OS version 10.0.18362 I don't think this is the latest version.

 

Other than just re-building the deployment server again from scratch i'm starting to run out of ideas.

[kennysarmy]

What version of Windows are you successfully deploying?

 

I also tried to get our MDT to deploy 20H2 and gave up - constant errors.

 

I was going to look at it again in the summer when I've more time without distractions.

 

Will be a thread on here somewhere with the issues I was having - maybe related?

[steveg]

Previous image is 1809, this old image still deploys fine onto new machines so I'm fairly happy that my deployment server is working as it should

 

I'll have a search for your previous thread.

 

Nice to know i'm not the only one with problems I suppose!

[kidpressingbuttons]

There is a fix you need to apply to deploy 20H2:

 

https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7

[steveg]

There is a fix you need to apply to deploy 20H2:

 

https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7

 

Thanks, sadly tried that one and still not working - machines I've been testing it on have been UEFI as well.

[kennysarmy]

Thanks, sadly tried that one and still not working - machines I've been testing it on have been UEFI as well.

 

I found the same!

[Boredguy]

you can add a step to your task sequence to fix the issue.

MDT, ADK and Failure (5616): 15299: Verify BCDBootEx - Blogs - EduGeek.net has the step to add the new entry into the PreInstall -> New Computer Only to fix the UEFI detection so that 20H2 builds regardless of BIOS or UEFI

[Lilmaca]

i got MDT 20H2 working perfectly fine!

[3s-gtech]

Without the fix above I couldn't deploy BIOS images, but MS's hotfix didn't work for me and I still needed the step in my task sequence.

[steveg]

i got MDT 20H2 working perfectly fine!

 

Good to know it can work at least! Was this an upgrade from an earlier version or fresh install?

 

- - - Updated - - -

 

you can add a step to your task sequence to fix the issue.

MDT, ADK and Failure (5616): 15299: Verify BCDBootEx - Blogs - EduGeek.net has the step to add the new entry into the PreInstall -> New Computer Only to fix the UEFI detection so that 20H2 builds regardless of BIOS or UEFI

 

Sadly a different error to the one I am experiencing, hotfix didnt change anything either.

[Lilmaca]

i upgraded from 1909, i had the 2004 ADK pack already installed though, make sure in your task sequence that fixuefidetection is not on Continue on error as that was making it fail for me, also try deploying 1909 and if it works just edit the task sequence to 2009 if that makes sense

[highsky]

The suggestion above, on the existing task sequence, for 1809, under install OS, change the image to your current one.

On the error, are you using the same domain user as with the old ts for the deployment?

Is this a new share?

Any rules under the share properties?

 

An alternative if your new one doesn't come with software updates, use a task sequence for an in place upgrade.

[steveg]

i upgraded from 1909, i had the 2004 ADK pack already installed though, make sure in your task sequence that fixuefidetection is not on Continue on error as that was making it fail for me, also try deploying 1909 and if it works just edit the task sequence to 2009 if that makes sense

 

I will check that in the task sequence, but the error i'm getting doesn't refer the the uefi issue at all.

[steveg]

The suggestion above, on the existing task sequence, for 1809, under install OS, change the image to your current one.

On the error, are you using the same domain user as with the old ts for the deployment?

Is this a new share?

Any rules under the share properties?

 

An alternative if your new one doesn't come with software updates, use a task sequence for an in place upgrade.

 

I tried changing the OS on an existing task sequence for the new one with the same error, also tried a new task sequence a few times after various upgrades etc.

 

Same domain and username for both - task sequence prompts for it. Even after the error I can manually map a network drive at the command prompt to the deployment share using the same user account. I even temporarily changed permissions on the deployment share to full control for everyone.

 

I'm going to try creating a new deployment share this morning and see if that does anything.

 

I appreciate all the suggestions from everyone.

[steveg]

Created a new deployment share, same issue with image.

 

Imported windows 20h2 from iso and tried deploying that. Worked fine.

 

This implies there is something wrong with the image I have, but I can manually deploy it from a usb boot disk using dism, which implies the image is ok?

 

Rapidly heading towards building master image again from scratch, it's just a pain because of some of the software we have on it.

[dmason2]

managed to get 20h2 out no problems, needed to update the ADK first for it to work. Captured the wim and imported it to sccm

[Lilmaca]

its not the image, technically 20H2 isnt supported, its not easy to get it deploying, i recommend using 2004 until 21H1 ADK pack comes out (later this year), then you will get 21H1 (better than 20H2) and it will deploy fine.