Upgrading a cluster?

[Mike Leone]

I have a cluster that is using nodes that are Win 2019. Am I correct in thinking I can add new nodes that are WIn 2022, then evict out the Win 2019 nodes? Which would then leave me with a Win 2022 cluster?

--

Mike. Leone, <mailto:tur...@mike-leone.com>

PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>

[Philip Elder]

How is the shared storage set up?

 

You could in-place upgrade just make sure to have the component firmware and drivers lined up prior.

 

Philip Elder MCTS

Senior Technical Architect

Microsoft High Availability MVP

MPECS Inc.

E-mail: Phili...@MPECSInc.Ca

Phone: +1 (780) 458-2028

Web: www.MPECSInc.Com

Blog: Blog.MPECSInc.Com  

Twitter: Twitter.com/MPECSInc

 

Please note: Although we may sometimes respond to email, text and phone calls instantly at all hours of the day, our regular business hours are 8:00 AM - 5:00 PM, Monday thru Friday.

--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BjNmq2TnROiZMyus21RwO%3DisYxfXtifeP5NA7FV-6qdGQ%40mail.gmail.com.

[Brian Illner]

That’s a Cluster OS Rolling Upgrade.

 

Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade | Microsoft Learn

 

The Cluster Object is separate from the Server OS – so after all hosts are replaced with Win 2022, you’d still have to upgrade the cluster itself too.

 

BRIAN ILLNER  |  Senior Systems Administrator ​​​​ 864.250.9227 Office 864.679.2537 Fax Canal Insurance Company 101 N. Main Street, Suite 400 Greenville, SC 29601 WARNING:  As the information in this transmittal (including attachments, if any) may contain confidential, proprietary, or business trade secret information, it should only be reviewed by those who are the intended recipients.  Unless you are an intended recipient, any review, use, disclosure, distribution or copying of this transmittal (or any attachments) is strictly prohibited.   If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.  While Canal believes this transmittal to be free of virus or other defect, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Canal (or its subsidiaries and affiliates) for any loss or damage arising therefrom.

 

From: ntsys...@googlegroups.com <ntsys...@googlegroups.com> On Behalf Of Mike Leone
Sent: Thursday, March 19, 2026 1:04 PM
To: NTSysAdmin <ntsys...@googlegroups.com>
Subject: [ntsysadmin] Upgrading a cluster?

 

CAUTION: This message was sent from outside of Canal Insurance. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. Please report all suspicious emails to "inf...@canal-ins.com" as an attachment.

---

--

[Mike Leone]

Everything are VMs. The shared storage is via iSCSI to a Nutanix Volume Group, running in VMware. We're planning on migrating the cluster to Nutanix AHV as a hypervisor, and then changing the storage to be Direct Access rather than iSCSI, as that is the recommended method with Nutanix (these days). I'm just thinking that after we do all that, I could upgrade the nodes, and this have the whole cluster be on a newer OS.

Otherwise I have to build a whole replacement cluster, sync the storage manually, then do the cutover myself. 

     

To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/7e97617d99554b6daef6cf45213ea439%40MPECSInc.Ca.

[Mike Leone]

Huh. I did not know that. We don't use Hyper-V.  I'm hoping and guessing that wouldn't matter, and that this should work on my Nutanix AHV environment ....

     

To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/DS4PR13MB7560EA5D66D8704E62180CAFC54FA%40DS4PR13MB7560.namprd13.prod.outlook.com.