Server OS 2025

[-]

jarvisofficial@reddit

That migration path doesnt give confidence specially with an old database in the mix. Legacy databases tend to be the weakest link in these upgrades. I think dbForge for SQL server or even SSDT can help map out and verify the whole thing. You can start by generating documentation for old schemas, comparing structure between versions and validate data after migration. It takes a lot of the uncertainty out of moving those archaic systems to new environments.

Reply

[-]

CPAtech@reddit

You're brave trying to use 2025 for domain controllers.

Reply

[-]

Slippy_27@reddit

Still not stable, eh?

Reply

[-]

taeratrin@reddit

Our experience with 2025: servers with names that end in '2' randomly freeze. This happened in two separate cases on two different hypervisors. Quirky.

Reply

[-]

GremlinNZ@reddit

Interesting, might be having this exact issue. Would renaming it resolve it, or it's a new build?

Reply

[-]

taeratrin@reddit

We didn't bother testing further or renaming. If it wouldn't support a 2 at the end, there's no telling what else might happen. There were other issues, as well. We just destroyed the VMs and built some 2022 VMs instead.

Reply

[-]

CPAtech@reddit

Do you have mixed versions of DC's?

Reply

[-]

taeratrin@reddit

No. Have no idea why it was happening, and we needed to rebuild our Storefront servers quickly, so we didn't investigate much and just installed 2022.

Reply

[-]

jcwrks@reddit

Quirky.

Reply

[-]

bill-m@reddit

Quarky

Reply

[-]

Ivy1974@reddit (OP)

Wasn’t my choice. Boss ordered it and then after the smoke cleared he said never again.

Reply

[-]

lart2150@reddit

Do you have downgrade rights?

Reply

[-]

Ivy1974@reddit (OP)

We solved the issues using a combination of the 2025 and a VM 2019. The 2012 has been shutdown. Miracle the machine lasted this long.

Reply

[-]

AutomaticDiver5896@reddit

Most pain here is new security defaults breaking old stuff: confirm SYSVOL is on DFSR before adding 2025 DCs, and audit LDAP signing/channel binding, NTLMv1/RC4, SMB1, and TLS 1.0/1.1. Update ODBC/OLE DB drivers; old 32‑bit providers won’t load on 2025. Schannel and LSASS logs will point to the culprit. Stagger by keeping the app on 2019 while you harden GPOs. Used Quest Change Auditor and Redgate SQL Compare; DreamFactory helped expose the legacy DB via REST during client upgrades. Fix the security baseline gaps first and most quirks disappear.

Reply

[-]

OpacusVenatori@reddit

New PSA over in r/ExchangeServer with a specific FSMO role residing on 2025 DC: [https://www.reddit.com/r/exchangeserver/comments/1o2cpfi/psa\_do\_not\_use\_windows\_server\_2025\_as\_the\_schema/](https://www.reddit.com/r/exchangeserver/comments/1o2cpfi/psa_do_not_use_windows_server_2025_as_the_schema/) [https://techcommunity.microsoft.com/blog/exchange/active-directory-schema-extension-issue-if-you-use-a-windows-server-2025-schema-/4460459](https://techcommunity.microsoft.com/blog/exchange/active-directory-schema-extension-issue-if-you-use-a-windows-server-2025-schema-/4460459)

Reply

[-]

YinSkape@reddit

We were testing rolling out Server 2025 for our DCs and each time the DC was promoted, the DC locked itself out and left behind a bunch of DC-related metadata. Went through days of troubleshooting before giving up and testing Server 2022. Promoted without a hitch. Weeks later, found this thread. www.reddit.com/r/sysadmin/comments/1i2jl5x/upgraded_from_2022_to_2025_domain_controller_can/

Reply

[-]

Flashy-Departure-445@reddit

We went from 2012r2 to 2025 no issues :)

Reply

[-]

miscdebris1123@reddit

I keep my servers 1 version behind. The number of times I've needed the latest feature is basically zero. The only exception was server 2003.

Reply

Reply to Post

18 Comments

jarvisofficial@reddit

CPAtech@reddit

Slippy_27@reddit

taeratrin@reddit

GremlinNZ@reddit

taeratrin@reddit

CPAtech@reddit

taeratrin@reddit

jcwrks@reddit

bill-m@reddit

Ivy1974@reddit (OP)

lart2150@reddit

Ivy1974@reddit (OP)

AutomaticDiver5896@reddit

OpacusVenatori@reddit

YinSkape@reddit

Flashy-Departure-445@reddit

miscdebris1123@reddit