Apr 04 2022 07:30 AM
Hello,
Doing some searches on the web, it's not clear if there is an upgrade path from 2012R2 to 2022 Windows Server. From the link, I was wondering if there is an upgraded diagram, or if Microsoft has a recommendation on the path forward for this route? Is this upgrade not supported, and we should opt to then do a clean install?
https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-overview
Thank you
Apr 04 2022 12:10 PM - edited Jan 17 2024 10:13 PM
It is possible to upgrade from Windows 2012r2 to 2022, nice article about it here https://www.virtualizationhowto.com/2021/06/in-place-upgrade-windows-server-2008-r2-to-windows-serve... It's about 2008 R2 to 2012r2 and then to 2022 in one jump
Edit : You have to take a break first on Windows Server 2019 in between, jump is too big otherwise from 2012R2 to 2022
Apr 05 2022 08:48 PM
Apr 07 2022 01:16 AM
Apr 08 2022 05:59 AM
Apr 11 2022 06:49 AM
@Harm_Veenstra I appreciate the responses. My concern is that is there a official recommendation from Microsoft? Does Microsoft 'standby' that this upgrade path should work, or what I'm reading from other responses is that, it's better to do a clean install, or perform both routes just in case...
Thank you
Apr 11 2022 06:56 AM
SolutionApr 11 2022 07:02 AM
Apr 13 2022 04:51 AM - edited Apr 13 2022 07:12 AM
Actually migrating to Windows 11 needs much planning and considerations due to heavy changes to the underlying hardware security stack (TPM 2.0, UEFI, Secure Boot, VBS etc.).
Same is true for Windows Server 2022.
Just because it "works" doesn't mean it is properly configured, secured and optimized.
You certainly doesn't want your brand new Windows Server 2022 relying BIOS/MBR model by example.
Apr 13 2022 04:57 AM
Oct 19 2023 01:27 PM
"Avoid in-place upgrade whenever you can"
This is very difficult to do when the DC has hundreds of users and computers and other roles running, especially when you are a new sys admin with no connection to the prior sys admin of anything else the DC vm may be doing that is critical that you can't migrate by doing a fresh install.
Nov 03 2023 06:51 AM
@Chrisntps If is a Domain Controller the recomendation is to create a new Windows server 2022, add the roll of Domain Controller and move all the DC rolls to this new one, then "demote" the old one.
Nov 05 2023 01:40 AM
@Chrisntpsfor new domain controllers it's better just to spin up a new server 2022 and join it to the domain then make it a domain controller (DNS Server) I've removed all other roles from my domain controllers such as (DHCP, CERT, KMS, other roles) this way it's easier to upgrade domain controllers by adding a new DC already running the latest OS. if you haven't move the roles out of your DC I recommend you to first work on moving DHCP, KMS, Certificate of Authority or any roles you may be running on that DC aside from (DNS only) this role must stay in the DC imho.
Jan 17 2024 05:40 PM
Jan 17 2024 06:24 PM - edited Jan 17 2024 08:13 PM
@cespiritu @Zach_B635 it depends on the workloads and antivirus apps.
If this is a correctly setup server like "no Domain Controller + Certificate Authority at the same Server or VM it is a simple as
some general guidelines from my numerous migration projects:
Following this you will have a great success rate, better than other described.
Hope this helped! Good luck on the tasks to come!
Jan 17 2024 06:55 PM - edited Jan 17 2024 07:01 PM
Jan 17 2024 06:55 PM - edited Jan 17 2024 07:01 PM
Brief How-To:
- follow all guidance and details from this thread.
- Mount the ISO in File Explorer or provide it to the VM (Hyper-V, VMware etc)
- Start Setup (or automate using setup commandline arguments and PowerShell)
- Don't forget to optimize the VM post successful migration VM Generation for VMware and Hyper-V) etc.
- Convert Gen 1 VMs using Script from Altaro Hyper-V Dojo Post Migration (have a backup)
- Boot the ISO Convert from MBR to GPT using mbr2gpt tool (Gen 2 VM required for Hyper-V)
- do not delete the WinRE recovery at the end of the disk (right of the the OS partition)
- VMware: do not forget to change the "installed OS flag" in extended options)
- When on Windows Server 2022, consider VBS / Secured Core options via VMware + WAC security settings. GPT / UEFI is a requirement for this.
- Hyper-V Gen2, GPT and UEFI will become required with Windows Server vNext, as well as we can expect vTPM, equivalent to Windows 11 security requirements. You won't pay twice if your WS 2019 and later are already using GPT and UEFI + Secure Boot as a base.
Jan 17 2024 07:06 PM
Hi @Harm_Veenstra there is a small oversight in your otherwise correct statement. 2012R2 to 2022 is not possible (or supported).
https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-overview
Jan 17 2024 10:08 PM
Jan 17 2024 11:51 PM - edited Jan 17 2024 11:55 PM
No problem Harm.
Pardon me, I wasn't aware at the time of writing I am necroing a thread from 2021, yet as the topic is still hot and the guidance given can be used universally now, allow me to add the last one from my end.
Which is
1. A great explaination of ESU if an upgrade isn't technical possible
2. The one the OP @Zach_B635 asked for which is today available, in form of an official recommendation , but maybe less complete.
Jan 18 2024 10:37 PM
Apr 11 2022 06:56 AM
Solution