Windows Server 2025 is now generally available

[DrCheese]

Remember, backup software doesn't officially support this yet, so if you are rolling it out onto production VMs, be aware.

[PotNoodleTech]

Gordon nuggets ive only just got mine to 2022 and nw you want me to upgrade again?!?!?!

 

Job for next year methinks.

[jthompson]

Gordon nuggets ive only just got mine to 2022 and nw you want me to upgrade again?!?!?!

 

Job for next year methinks.

 

The little gantt chart that I keep tells me that you're okay for a while yet.

[Tefters]

Turns out the Windows upgrade path to 2025 may have been an accident https://www.neowin.net/news/microsoft-blamed-for-windows-11-kb5044284-automatically-upgrading-server-2022-to-2025/

[MS2011]

Anyone done [emoji638][emoji[emoji6[emoji640][emoji638]][emoji640][emoji6[emoji640][emoji638]]][emoji637][emoji6[emoji640][emoji638]] to [emoji638][emoji[emoji6[emoji640][emoji638]][emoji640][emoji6[emoji640][emoji638]]][emoji638][emoji6[emoji640][emoji637]]? Our DC’s are running on [emoji638][emoji[emoji6[emoji640][emoji638]][emoji640][emoji6[emoji640][emoji638]]][emoji637][emoji6[emoji640][emoji638]] but I’m tempted to upgrade one of the member server to [emoji638][emoji[emoji6[emoji640][emoji638]][emoji640][emoji6[emoji640][emoji638]]][emoji638][emoji6[emoji640][emoji637]].

[PotNoodleTech]

The little gantt chart that I keep tells me that you're okay for a while yet.

[ATTACH=CONFIG]72577[/ATTACH]

 

Brilliant!!! STOLEN AND PLAGARISED!!!

[ITGuyNW]

The little gantt chart that I keep tells me that you're okay for a while yet.

[ATTACH=CONFIG]72577[/ATTACH]

I don't see Windows Server 2012 on this ??

[jthompson]

I don't see Windows Server 2012 on this ??

 

Here's a version for anyone feeling nostalgic.

 

(incidentally, these are created with Mermaid, using a plugin for DokuWiki)

[Simcfc73]

Did a couple of servers... windows update doesn't work on one and I can't use the troubleshooting as the ms-store can't open either.

 

I did 1 DC which didn't have any roles which worked fine apart from my Azure AD Connect which I ended up having to reinstall.

[3s-gtech]

Edugeek current concensus seems to be: avoid putting this on DCs for now!

[jthompson]

Did a couple of servers... windows update doesn't work on one and I can't use the troubleshooting as the ms-store can't open either.

 

I did 1 DC which didn't have any roles which worked fine apart from my Azure AD Connect which I ended up having to reinstall.

 

Win11 24H2 has a bug where the component store hashes are all out of whack (so "sfc /scannow" always finds and repairs errors every single time you run it). I've found that that results in Windows Updates in the Settings app getting stuck on "Something went wrong" for extended periods. Might the same problem be affecting Server 2025?

 

That bug should be fixed once the November patches come next week, btw (it's supposedly fixed in the preview update).

[DrCheese]

Edugeek current concensus seems to be: avoid putting this on DCs for now!

 

oh I'll do it once Veeam supports it

 

You need to rebuild your DCs rather than in place upgrade them - At least if you want to benefit from the new 32k AD database size.

[Warwick_Tech]

Bit the bullet and updated the Deployment server - seems suspiciously happy so far....

[Warwick_Tech]

Bit the bullet and updated the Deployment server - seems suspiciously happy so far....

 

Ha - knew it was too good to be true, updated the ADK, WinPE and MDT only to discover it froze on load (PXE); then found out it was because I has an older version of VirtualBox THEN I'm getting errors on 'install operating system' for 24H2 - Although I'm more inclined to believe that's virtualbox again....

 

 

Edit: Yes, it was virtualbox not mounting the disk drive correctly

Edited November 13, 2024 by Warwick_Tech

[Simcfc73]

Both my DC's upgraded fine and I've promoted the function level to 2025. All seems fine so far.

 

5 servers done... 1 with a driver issue for an old NIC and 1 won't activate but I'm working on that.

[Olliedawg]

IMO if your current estate is on 2022, theres no need to upgrade, especially if you don't need any of the new features. 2022 has 6 (nearly 7) years of life left at time of posting. No rush at all to upgrade, especially until any bugs/issues are ironed out by MS

 

Microsoft Windows Server | endoflife.date

[DrCheese]

Bit the bullet and updated the Deployment server - seems suspiciously happy so far....

 

Yeah I've started upgrading unimportant stuff while I wait for Veeam - Veeam backs them up 2025 machines fine just doesn't have application awareness support yet (so things like DCs, Exchange, SQL servers blah blah) so won't be touching those until official support comes.

[CHiLL]

I'm probably going to look at deploying 2025 to our less critical servers in the February half term, so hopefully Veaam will have updated B&R by then. I currently get warning emails from Veeam when it's backing my machine, saying 24H2 isn't supported yet, though it appears to be backing up fine. Maybe that's patched in a newer update, but I can wait until February for that too.

[DrCheese]

I'm probably going to look at deploying 2025 to our less critical servers in the February half term, so hopefully Veaam will have updated B&R by then. I currently get warning emails from Veeam when it's backing my machine, saying 24H2 isn't supported yet, though it appears to be backing up fine. Maybe that's patched in a newer update, but I can wait until February for that too.

 

They've confirmed that 2025 will be fully supported in 12.3 & that it will be released this calendar year so you should be good!

[Jxosh]

A little late to the party but I'll at least be testing Server 2025 on a test machine.. The 11 UI is hit or miss for me though.