Jump to content

Recommended Posts

Posted

Our imaging process using WDS/MDT is based around 20H2 with crap stripped out.

 

Are there any real-world advantages of moving to a more recent build?

 

Anything coming in a future release that would make waiting the best option?

 

Cheers

Posted
Nothing major that I am aware of, there may be certain versions needed for specific things if your devices are hybrid Azure AD joined for instance. Obviously you have until May to move from 20H2, so you might as well test 22H2, that will see you through until just before Windows 10 EOL in Oct 25.
  • Thanks 1
Posted
I’ve just popped the first 22H2 build into our 20H2 estate. Nothing to report, all seems fine - will mean that the OS has support after May which is the most important bit!
  • Thanks 1
Posted
We're on 21H2 and I'll look at 22H2 within the coming months. There aren't really that many additional features. I mainly like to upgrade to keep us within the window for updates.
Posted
There's no real newsworthy features added but having the latest build means applying less updates on install and also it kicks the support dates down the road.
Posted

22h2.JPG

 

Been a while since I did this, but I've copied the existing 20H2 task sequence, imported the 22H2 image, updated the task sequence for the new OS - but do I also need to update the unattend.xml?

 

Cheers

Posted
Don't think so - anything in yours that is version specific?

 

I dug around and found this entry - so updated it.

 

Will try an do an image later to check all OK.

 

22h2a.JPG

Posted

Are there any real-world advantages of moving to a more recent build?

 

Security updates are a huge reason. 20H2 support ended May 2022.

Posted (edited)

We updated the base OS in MDT to 22H2 (from 21H2) recently purely for the longer support interval.

 

22H2 (Edu/Enterprise) EOL is 13th May 2025

21H2 (Edu/Enterprise) EOL is 11th June 2024

21H1 (Edu/Enterprise) EOL is 13th December 2022 (next week)

 

We went 1909 > 20H2 > 21H2 > 22H2, updating the build environment once we were happy so we were always imaging with an OS with maximum supported time.

Edited by pete
Posted

Originally deployed with 21H2, though using 'Feature Updates for Windows 10 and later' within Intune they were all automatically updated to 22H2 successfully.

 

We have since updated our base WIM (using WIMWitch to remove unwanted apps and apply latest updates etc.) to 22H2 combined with using the latest Administrative Templates (.admx) for Windows 10 2022 Update (22H2) to update some of the GPOs still in use; in addition to Intune policies.

 

As mentioned, 22H2 is supported until 13th May 2025, which means we can (or could) remain on this version until W10 goes EOL / we migrate to Windows 11 (once have supported hardware!)

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...