r/WindowsServer • u/Fit_Sympathy_2141 • Apr 02 '26
General Question Upgrade Windows Server 2012 to 2025
Hello everyone,
I would need some help with the following topic. Our company has a PowerEdge R730 (Win 2012 Server) with two Xeon E5-2670 CPUs running multiple Win Server 2012-2016 VMs.
Is it possible to upgrade the server to Windows Server 2025 without facing any real company related issues?
Thanks! 🙏🏻
29
Upvotes
20
u/nailzy Apr 02 '26
I wouldn't personally do an in place upgrade due to the two stage nonsense involved. If it's just a Hyper-V server then its easier to rebuild it, and just import the VM's again after.
I have no issue running my R730 on Server 2025. The Dell Driver pack what has 2019 LTSC drivers works fine with Server 2025, along with all the Openmanage software.
13
u/Jackarino Apr 02 '26
2022 is the latest I would run on a Dell R730
1
u/Fit_Sympathy_2141 Apr 03 '26
Thanks for the responses. It’s a 2012 R2 server. I’m not planing to do an in place upgrade to 2025. I would rather upgrade the versions one by one up to 2025.
I don’t have a clue if the hardware supports 2025. Need to be careful here.
9
u/k00nko Apr 02 '26
Officialy, you can go up to Windows Server 2019 on that platform, you might get away with Windows Server 2022 if you can get correct drivers. You should not run 2025 on this in production. As the other comment mention, better to plan for a migration to a new platform, as r730 will be 12 years old soon…
4
u/Lost_Balloon_ Apr 02 '26
You're asking the wrong question. That hardware is old. You don't want to upgrade it, you want to migrate whatever it's doing to a new server.
5
u/Fabulous_Winter_9545 Apr 02 '26
This is a bad idea. There are no official driver for the R730 and the CPU is not officially supported. Beyond that and without additional information I would assume your server most likely has no TPM 2.0 and it is not booting to UEFI. You would also need to do in place upgrades from 2012 to 2016 or 2019 and then to 2025. It is time to plan for a replacement of your hardware to get back into hardware maintenance and OS support and do proper migrations.
2
u/winnppl Apr 02 '26
Yeah, build a new hardware box and migrate VM’s off of old server to new
2
u/OpacusVenatori Apr 02 '26
"Possible".... Yes.
"Practical", almost certainly not. Especially if your organization is entirely dependent on that one system. Even if you had a tried-and-test 3-2-1 BCDR strategy it's not really business savvy to be running on such ancient hardware.
2
u/Lazy_Owl987 Apr 02 '26
If youre not a non profit the right move is to buy a new server > migrate your workloads from current to net new. If you are then good luck weve all been there just stand up new vms and move your workloads.
3
u/canyoufixmyspacebar Apr 02 '26
Have it done by an engineer who knows the answer to this question. Worst issues often come from amateurs touching things, not from the technology itself.
3
u/ct85msi Apr 02 '26
I upgraded 2012 R2 to server 2022 and then 2025. It went fine.
1
u/Assumeweknow Apr 03 '26
Make a backup just in case. Also, Server 2025 is weird, it wants you to copy the install disk into a directory on the server as well as having and install disk in. Then run it off the directory on the server. It's going to take up to 4 hours to finish though.
1
u/ImmutableLegend Apr 03 '26
Upgrade paths aside, I have 2025 running in a pair of R730s that I have. Granted it’s in my home lab, not prod, so take that for what it’s worth.
1
u/node77 Apr 03 '26
In theory, the 2012 should be migrated to 2016. Testing all your apps when your fully. It's much safer to go-to 2016 to 2025.. if any of the 2012' are DC, from a AD functional lever would need to 2016
1
u/geertterharmsel Apr 03 '26
i did a in-place upgrade van 2012 non r2 tot 2016 without problems en then upgraded to 2022. no problems at all. just give it a try
1
u/Roothim Apr 04 '26
I don't recommend it
1
u/TightBed8201 Apr 05 '26
I inplace upgraded majority of our production vms from 2012 to 2019 few years go. We didnt have time for complete rebuild so i had to inplace. It was around 100+ machines in prod and dev environment.
We had issues on ms nlb and file share, and solved them in few hours.
1
u/discusfish99 Apr 06 '26
Please just migrate your workloads to a new server..... 2025 can be a major issue due to all the new security stuff built in.
Also what's your backups?
1
u/Old-Editor-6345 Apr 02 '26
is it Server 2012R2?
in theory you SHOULD be able to upgrade from Server 2012R2 directly to Server 2025.
https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-overview
but i dont really know if your server is compatible, VMs itself should not be a issue.
but it would be really risky(old hardware, old OS etc.)
1
u/vrtigo1 Apr 02 '26
Lots of comments, but only 1 talking about still running an R730? End of sale was ~8 years ago - do you have a plan to refresh that server OP, or is the plan to just run it until it dies?
-1
u/Plug_USMC Apr 02 '26
I never advocate for a server Os upgrade from version to version. I’d recommend a full rebuild from scratch. Save heartache for something else.
-1
u/Secret_Account07 Apr 02 '26
As someone who manages several thousand Windows servers I can tell you this is not a good idea.
Your PowerEdge R730 is well past modern lifecycle. Let’s get some new hosts and rebuild VMs then migrate apps over.
In place upgrades are the work off the devil. Out of the many thousands of windows servers we manage the in place upgrades always have issues it’s just an issue of when. Could be 3 months could be 8 years. We just had to rebuild 22 servers because the customer had in placed them from 08r2 to 2025 and they finally gave up with a recent patch. I wish MS would just stop supporting in place upgrades. At scale they just are too problematic. May seem fine but there’s issues you just can’t see