Event banner
Event details
MicrosoftEdward, this is a great question! Windows 11 24H2 can absolutely be deployed as an in-place upgrade feature update. Simply follow the same process you used to upgrade 22H2 to 23H2. The transition should be smooth. If your users are expecting a short restart (like what they saw with an enablement package) you may want to provide some communications that the restart will take a bit longer this time around. Perform the upgrade on some test devices first to get a feel for how long the upgrade will take on your devices, as your mileage could vary based upon disk speed, processor speed, etc.
As long as you meet the prerequisites (Prerequisites | Microsoft Learn) you should strongly consider moving to Autopatch (What is Windows Autopatch? | Microsoft Learn) and get off SCCM for updates. We are going to continue investing in Autopatch features and capabilities and you don’t want to be left behind!
- Hello Eric, Thank you for your reply, however the upgrade from 22H2 to 23H2 was through an enablement update which was pushed through an ADR rule. If this is an in place upgrade, I am guessing there is much more involved. We used in place upgrades to upgrade Windows 10 workstations to Windows 11; should we expect the same process? Thank you for your help.
- EricMoe
Edward, sorry, I pasted the Intune link out of habit. Here's how to use SCCM to configure Windows as a Service in SCCM to deploy a Feature Update. Manage Windows as a Service - Configuration Manager | Microsoft Learn There are also resources online to do the same as a task sequence if you choose.
- EricMoe
Edward, check out using Update rings for Windows 10 and later to deploy the Feature Update as an In Place Upgrade, Configure Update rings for Windows 10 and later policy in Intune | Microsoft Learn
- Thank you for the SCCM guide, fortunately all our Windows client workstations are Windows 11 23H2; so we do not have any Windows 10 machines left.