Skip to content

Update-ClusterFunctionalLevel.md

Latest commit

 

History

History
185 lines (129 loc) · 5.27 KB

Update-ClusterFunctionalLevel.md

File metadata and controls

185 lines (129 loc) · 5.27 KB
Raw
description Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
external help file Microsoft.FailoverClusters.PowerShell.dll-Help.xml
Module Name FailoverClusters
ms.date 07/18/2025
online version https://learn.microsoft.com/powershell/module/failoverclusters/update-clusterfunctionallevel?view=windowsserver2025-ps&wt.mc_id=ps-gethelp
schema 2.0.0
title Update-ClusterFunctionalLevel

Update-ClusterFunctionalLevel

SYNOPSIS

Updates the functional level of a mixed-version cluster.

SYNTAX

Update-ClusterFunctionalLevel [-Force] [-WhatIf] [-InputObject <PSObject>] [-Cluster <String>]
 [<CommonParameters>]

DESCRIPTION

The Update-ClusterFunctionalLevel cmdlet updates the functional level of a mixed-version cluster. You can update the cluster after all nodes have been updated.

Starting with Windows Server 2016, you can add a node that runs a more recent version of the Windows operating system (OS) into a cluster of nodes that run a previous version of the Windows OS.

After you add a node that runs a different version of the Windows OS, the cluster becomes a mixed-version cluster. You can implement a mixed-version cluster to continue to run while you upgrade the OS on each node in the cluster.

We recommend that you upgrade all nodes in the cluster within a month. We don't recommend using a mixed-version cluster permanently.

You can use this cmdlet to support a rolling OS upgrade for a cluster. If you use a cluster that runs Hyper-V in which all the nodes run Windows Server 2012 R2, you can upgrade the nodes of that cluster without downtime for your virtual machines.

First, drain one cluster node by specifying the Drain parameter of the Suspend-ClusterNode cmdlet. This cmdlet causes all virtual machines to live-migrate to one of the other hosts.

Next, remove the host from the cluster by using the Remove-ClusterNode cmdlet.

Next, perform an in-place upgrade to install the new version of the OS. Note that a cluster can only be upgraded one OS version at a time, for example:

  • Windows Server 2012 R2 to Windows Server 2016
  • Windows Server 2016 to Windows Server 2019
  • Windows Server 2019 to Windows Server 2022
  • Windows Server 2022 to Windows Server 2025

Next, add the Hyper-V role and the Failover Clustering feature, if not already installed, by running the following command:

Install-WindowsFeature -Name Hyper-V -IncludeManagementTools
Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools

Finally, add the node into the cluster by using the Add-ClusterNode cmdlet.

Repeat these steps for each node in the cluster.

EXAMPLES

Example 1: Test a possible update

Update-ClusterFunctionalLevel -WhatIf

This command tests whether an update would finish successfully. Because the command includes the WhatIf parameter, the command doesn't perform the update.

Example 2: Update a cluster functional level

Update-ClusterFunctionalLevel -Cluster "cluster_17"

This command updates the cluster functional level of the cluster named cluster_17. All of the nodes of this cluster must already be updated before you run this command.

PARAMETERS

-Cluster

Specifies the name of the cluster on which to run this cmdlet. If the input for this parameter is . or it's omitted, then the cmdlet runs on the local cluster.

Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

-Force

Forces the command to run without asking for user confirmation.

Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

-InputObject

Specifies the input to this cmdlet. You can use this parameter, or you can pipe the input to this cmdlet.

Type: PSObject
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet isn't run.

Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

INPUTS

Microsoft.FailoverClusters.PowerShell.Cluster

This cmdlet accepts a Cluster. This cmdlet updates the functional level of this cluster.

OUTPUTS

Microsoft.FailoverClusters.PowerShell.Cluster

This cmdlet returns a Cluster. This cmdlet updates the functional level of this cluster.

NOTES

Once you update the cluster functional level using this cmdlet, the change is permanent and can't be reverted to a previous level.

RELATED LINKS

Add-ClusterNode

Suspend-ClusterNode

Remove-ClusterNode