Jump to content

Recommended Posts

Posted

Anyone using MDT to roll out Windows 11 and the latest CUs? From what I've found, MS have changed the way cumulative updates work from the April '26 one onwards and it's now more difficult to include them in the build process, but I can't find how to actually do it. Anyone got any pointers please? I've never included them in the past so don't know how it used to work!

 

Stuart

Posted

I tried running up a new MDT instance here but it wasn't having it so I'm moving over to a combo of FOG for deployment and then Action1 Free (for 200 Endpoints) for patch management.

 

 

Posted (edited)
7 minutes ago, TechMonkey said:

Isn't MDT dead and not supported now? So, no new updates and won't support Win11.

That exactly. Unless you are using the SCCM version, you need to move to an alternative method of deployment. 

Edited by willtech
Posted

We still use MDT to deploy initial Windows 11 base image Not updated the included windows update version, as no need as updates are cumulative etc and use Intune to update, deploy apps etc.

 

The recent Hot Patch does now cause differing build version numbers even though clients may be on same monthly update - depending if cumulative update or hot patch was applied!

 

https://windowsforum.com/threads/windows-autopatch-hotpatch-default-may-2026-opt-out-guide.404702/

Posted

You can just download the latest ISO and put that into MDT.

 

It supports Windows 11, but not new versions. Still works fine though.

 

I do not miss FOG at all.

Posted

Still using MDT here, but have tested and deployed latest OS using OSDCloud, so at least we now have a backup plan should MDT fail us.

Posted
1 hour ago, 3s-gtech said:

You can just download the latest ISO and put that into MDT.

 

It supports Windows 11, but not new versions. Still works fine though.

 

I do not miss FOG at all.

 

That's what we do then have PDQ work its magic 

Posted (edited)

Using MDT with a build and capture TS based on 25H2 Nov 2025 (build 26200.7171) that installs the latest CU prior to capture. That still worked for the May updates, resulting in a 26200.8457 deployment image.

 

EDIT: I'm also working on getting OSDCloud into production, hopefully before MDT stops working for us.

Edited by jthompson

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...