[22h2] MDT and Windows 11

[Frazzle]

Is it true that MDT is not officially supported to deploy Windows 11? I have read this in several places now.

[jthompson]

I believe so. I've got it to deploy Win11 23H2 successfuly though, using the Win11 22H2 ADK (v10.1.2200.1) with a few tweaks to fix things. Happy to share my notes on that.

[Jcx500]

it deploys out perfect with MECM which uses mdt and the windows adk also

[jmak]

I've been using MDT and WDS to deploy Windows 11 for over a year. I needed a bit of help getting it working - which obviously I found on here [emoji4]

Since I got the first deployment working, I've just been able to load in updated ISOs for new versions.

[Olliedawg]

I've been using MDT and WDS to deploy Windows 11 for over a year. I needed a bit of help getting it working - which obviously I found on here [emoji4]

Since I got the first deployment working, I've just been able to load in updated ISOs for new versions.

 

Would you be so kind to share the changes you made? I haven't tried a windows 11 deployment/upgrade through MDT yet, but its on my list. might have a play around today if I get chance.

 

A while back I did try move to the latest ADK/WinPE versions, however they broke VBScript so I reverted back. I heavily rely on the task sequence to install apps/drivers etc..

 

I'm on -

ADK version 10.1.25398.1

ADK WinPE version 10.1.19041.1

[Frazzle]

I believe so. I've got it to deploy Win11 23H2 successfuly though, using the Win11 22H2 ADK (v10.1.2200.1) with a few tweaks to fix things. Happy to share my notes on that.

 

Would be great if you would share you notes. Thanks

 

- - - Updated - - -

 

it deploys out perfect with MECM which uses mdt and the windows adk also

 

MECM costs though right?

[jthompson]

Would be great if you would share you notes. Thanks

 

These are the tweaks I made after instlling the Windows 11 22H2 ADK (10.1.2200.1)

• Ensure that deployment shares have x86 disabled in their properties.
  
• Create the folder "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs". This prevents MDT crashing out when attempting to create boot images.
  
• To fix the scripting failures, modify "C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x64.xml" as per https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md#hta-applications-report-script-error-after-upgrading-to-adk-for-windows-11-version-22h2. An important thing to not miss here is to update the existing Order value from 1 to 2.
  

 

After that, you should be able to successfully recreate boot images when updating your deployment share(s).

 

I found that when using earlier ADKs, MDT clients couldn't connect to our MDT database without TLS 1.0 being enabled on the server. We have TLS 1.0 and 1.1 disabled on our servers. The later ADKs, like this one, support TLS 1.2 whereas the earlier ones didn't.

[jthompson]

I also have this in my notes too.

 

Later Windows ADKs don't properly detect BIOS, resulting in imaging failures on BIOS-based devices (yes, we still have a few). This hotfix replaces the relevant DLL to fix the issue:

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

[jmak]

Would be great if you would share you notes. Thanks

 

- - - Updated - - -

 

 

 

MECM costs though right?

Found it:

https://www.edugeek.net/showthread.php?t=229694

 

Apologies - I had planned to share my notes yesterday before you asked, but spent over an hour trawling through some of my >4500 posts without success.

 

Searching "jmak wds" on here brought up lots of posts - apparently I've been struggling with this for 11 years on and off! But not the relevant one.

 

Duck Duck Go search for "edugeek jmak wds" returned it as the top result [emoji2371]

[Olliedawg]

Hey all - would just like to say this post has been extremely useful to me - so thanks for that

 

I have followed the above steps & have been successful with using the latest ADK/ ADK winPE addons for Win11, with my previously created Windows 10 Task sequences. (woohoo!)

 

Coming across a strange issue when testing a Win11 in place upgrade using a Standard Client Upgrade Task Sequence. I create a new Task sequence, select upgrade , import a vanilla set of source files from the latest Win 11 ISO & leave everything in the TS as default. I regenerate the boot image and replace in WDS. If i boot into Litetouch, i am unable to see the newly created upgrade task sequence, containing the Win11 wim. It's just not there.

 

 

On my PC, if i browse to "\\MDTSERVER\Productionshare$\Scripts\litetouch.vbs" I am able to see the upgrade task sequence.

 

*edit* I have never used MDT to perform an in place upgrade, so is this normal behaviour? I found a MS KB for upgrading from 7 > 10, and this states to browse to the litetouch.vbs location and run the TS this way.

Edited April 16, 2024 by Olliedawg

[jthompson]

Did you also restart WDS after importing the newly generated boot image? That might have a bearing on it, IDK.

[Olliedawg]

Did you also restart WDS after importing the newly generated boot image? That might have a bearing on it, IDK.

 

I did not - I will reboot the entire VM & try again this afternoon

[jthompson]

Yeah, I'm just wondering whether WDS would continue to serve up the earlier boot image until the WDS service is restarted. Restarting WDS from the WDS console should suffice for that.

[ITGuyNW]

I'm am currently redoing my MDT because of the VBScript stuff. I got a feeling they don't want us using this anymore...

 

What's the alternative? Configmgr?

[Olliedawg]

Still the same unable to see the upgrade TS when booting from the litetouch PE

 

I'm going to try a windows 10 iso to see if that makes any difference

 

I have also just tried to run the TS direct from the litetouch.vbs on a freshly imaged windows 10 machine. The OS ugprade to win11 starts & then fails with a load of errors. Most obvious thing i can see is

"Litetouch deployment failed, return code = -2147467259 0x80004005"

 

From what i've read this error can mean a multiple of things, from BIOS/UEFI related issues to the OS installing onto the wrong drive.. Going to dive into the logs and hopefully see something there.

[jthompson]

I'm am currently redoing my MDT because of the VBScript stuff. I got a feeling they don't want us using this anymore...

 

What's the alternative? Configmgr?

 

MCM (aka MECM, aka SCCM) or Autopilot/InTune, I guess. I looked at MCM at little back but was put off by how complex it was to put together. MDT seemed like the right tool for what we want (deploying an OS and drivers over the network and it only taking 20-30 minutes), despite being long in the tooth. I expect MCM would be an easier prospect for me now, having had to wrestle with MDT so much to streamline it to as near zero-touch as possible.

[Olliedawg]

I've got it working!!

 

It seemed to be because I was missing this parameter

 

"WindowsUpgradeAdditionalOptions"

Value : /eula accept

 

Added this to the upgrade TS & all is good.

 

Here is the link, if it helps anyone else MDT in place upgrade from Windows 10 to 11 failing 0x80004005 - Software - Spiceworks Community

[ITGuyNW]

MCM (aka MECM, aka SCCM) or Autopilot/InTune, I guess. I looked at MCM at little back but was put off by how complex it was to put together. MDT seemed like the right tool for what we want (deploying an OS and drivers over the network and it only taking 20-30 minutes), despite being long in the tooth. I expect MCM would be an easier prospect for me now, having had to wrestle with MDT so much to streamline it to as near zero-touch as possible.

 

Yeah if MCEM is going to be the long term way of doing this, I may have to use that instead. If they are going to slowly break bits of MDT then I may as well do something else otherwise I'm going to be continually chasing it.

 

Once we are A3 and are capable of doing so, I'll look at Intune too.

[Olliedawg]

Yeah if MCEM is going to be the long term way of doing this, I may have to use that instead. If they are going to slowly break bits of MDT then I may as well do something else otherwise I'm going to be continually chasing it.

 

Once we are A3 and are capable of doing so, I'll look at Intune too.

 

I'll be doing the same once we have A3 (hopefully this year..) InTune seems to be the way forward. MDT is a massive bodge job to get working with Win11, BUT it does work.. for now!

[NeoNebula]

Yes, it's really true. At the moment, MDT (Microsoft Deployment Toolkit) does not officially support Windows 11 deployment. However, you can expect Microsoft to release updates to deployment tools, including MDT, to provide support for new operating systems.

[ITGURU]

Inherited a site which used MDT for windows 10 deployment. No issues adding windows 11 to it. did an image ran the lite touch script from network share and captured no problem. no issues restoring either detects drivers and restores.

[ITGuyNW]

I have been playing with MECM for the last month or so and it feels so antiquated. How does anyone use this??

 

My current method of MDT+PDQ gets systems sorted with very little involvement. This feels like its adding overcomplicating my current process and it's starting to irritate me.

 

Looked into Intune but didn't get anywhere really. It just doesn't feel very user friendly or intuitive.

 

I'm conscious about having to continue with MDT because I feel we're a monthly CU away from it being ditched all together.