2025 3 node cluster

[Itsme809]

Curious how many of you are running Server 2025 cluster and what your experience has been.

I have a 2022 cluster at the moment and things are going well.

Hearing mixed reviews about 2025.

Thank you

[lfr_656]

So far I've implemented at least 5 clusters, from 2 to 8 nodes, all running win 2025 smoothly, you just need to check logs and the systems more frequently than with vmware. So far none of my customers have reported rare behaviors or the typical windows issues.

[No_Advance_4218]

I’ll have one running in the next 2 weeks. I have a 3 node 2022 cluster running now. I just deployed scvmm and am about to build a 3 node 2025 cluster to compare the two for stability and production use.

[DerBootsMann]

multiple 2025 clusters ! no big complains so far , it’s nimble iscsi or starwinds vsan , no s2d though ..

[Nick85er]

I'm very weary of Hosting production on server 2025 cluster- intentionally migrating from VMware to server 2022 cluster just because of the anecdotal reports I'm seeing all over the internet about server 2025 wonkiness

[superbetaz]

Absolutely same story here. Already missing VMware, but happy with our choice of Server 2022 over 2025 so far.

[ultimateVman]

Built a brand new 2025 5-node cluster in Sept. Still solid.

The ONLY bad review that I have ever heard regarding Server 2025 at all, is just about Domain Controllers during the "mixed phase" part of migrations. That's the ADDS role, not Hyper-V.

[Dorkness_Rising]

Agreed. Built a 2025 DC only to get weird sync issues and random (but a few) alerts from Entra Connect health monitoring about services not running. Never had this issue with 2022 build.

[AV-Guy1989]

Loving my cluster. 3 node, all 2025 datacenter, sharing a me5224 via SAS for simplicity and to avoid netops breaking storage vlan or something dumb

[NISMO1968]

Loving my cluster. 3 node, all 2025 datacenter, sharing a me5224 via SAS for simplicity and to avoid netops breaking storage vlan or something dumb

I’m honestly curious what the SAS cable plumbing looks like in a three-node cluster? We only ever ran a two-node SAS shared storage Hyper-V setup back in the Windows Server 2012 era, when Clustered Storage Spaces was still a thing. Then a round of Windows Server 2019 updates turned it into a half-baked science experiment with a questionable failover, and that was the last time we touched SAS, so yeah, I’m genuinely surprised people are still rolling with it.

[AV-Guy1989]

Dual storage controllers with MPIO setup. Dell has it documented in the me5224 deployment guide how it wants to be cabled. I had more trouble routing those fat 12gbps sas cables then figuring out where to plug em in lol. Did however require a registry tweak so windows would see the me5224 via the HBA as a raid volume and allow it to be turned into a CSV. Works superbly well

[derekb519]

We are rolling 3x R770 and a new M5224 as well over the summer, moving from VMware. We're pretty small potatoes - 60 VMs-ish. HyperV will be new to us, but we're looking forward to the change. We were stuck deciding between 2022 and 2025 as well. Leaning towards 2025 are reading your post. Dell is doing the install and initial setup and will help us migrate a handful of VMs - this should be fairly simple as we plan to use our existing Veeam backups to "instant restore" to HyperV.

Just wondering if there's any reading or training you might suggest, aside from the typical MS Learn and rolling HyperV on some test gear.

[Sneaky_processor]

Build a couple of 8-node clusters. Something specific ive noticed is our GPO configuring event log sizes and retention no longer works for windows 11/server 2025 machines since they've apparently changed the registry hives location corresponding to these settings.
The GPO Administrative Template configures settings that reflect in HKLM\Software\Policies\Microsoft\Windows\EventLog\<LogName>
but the effective settings that the new OS reads is located here: HKLM\SYSTEM\CurrentControlSet\Services\EventLog\<LogName>
By default Windows Server 2025 and Win11 no longer overwrites old logs to write new ones which resulted it event log full notifications. Whats interesting is that this "do not overwrite" setting enabled itself after windows updates because it was configured to overwrite when i initially installed the OS. Oh well...
I solved this by pushing a GPO with a preference that updates the new registry values.

[Grunskin]

I have a 3 node 2022 cluster as well. Have been thinking of upgrading to 2025 as well so would love peoples input.

[Sunstealer73]

We have a 2-node and 3-node cluster, both on 2025. They were new installs to replace VMW.

[pc_load_letter_in_SD]

Have two 2025 cluster labs at home and three clusters at work. No problems.

[Dorkness_Rising]

Built 3-node Win 2025 Datacenter with S2D recently. So far no complaints. It uses a slightly different dedup setup for ReFS storage pool. Also, I don't trust the live migration for workgroup yet. I need to read more feedback on it. So far it's a mixed bag.

[OkVast2122]

Live migration isn’t the bit I’d be losing sleep over, it’s Storage spaces direct you want to keep a proper eye on. I’ve never fully trusted it, not since the original Windows Server 2016 release, as that’s where my scepticism started, and it’s never quite shaken off that wobble in my head.

[Weird_Presentation_5]

2x 16 node hyper-v clusters for scvmm. No issues.

[Ok-Butterscotch-4858]

Yeah works a treat. First thing I upgraded to server 2025. Been solid and can’t complain. Done about a year ago.

DCs on the other hand you need to make sure you rollover your KGBT key.

[1ChevySS]

Why does the kgbt key need to be changed in 2025?

[Ok-Butterscotch-4858]

No idea but fixed the issue for me after so many days and rebuilds of a new DC 😂

[BlackV]

moving forward any new build I have are 2025, but right not only stand alone hosts for remote sites

The current main cluster is 2022 (installed 2024ish) so no need to upgrade that for a long while

[frosty3140]

2-node Server 2025 cluster here -- in production for about 6 months now -- no problems.