This article describes the hotfixes that are currently available for Windows Server 2012-based failover clusters. Failover Cluster Management enables multiple servers to provide a high availability of server roles. Failover Cluster Management is frequently used for file services, virtual machines, database applications, and mail applications.
Collapse this imageExpand this image
The process for installing service packs and hotfixes on Windows Server 2012 differs from the process in earlier versions. In Windows Server 2012, you can use the Cluster-Aware Updating (CAU) feature. CAU automates the software-updating process on clustered servers while maintaining availability. For more information, see Cluster-Aware Updating Overview.
For information about how to manually drain cluster nodes for maintenance, see Draining Nodes for Planned Maintenance with Windows Server 2012.
The following Microsoft Knowledge Base articles describe the currently available fixes. Most of the updates apply to computers that are running Windows Server 2012. Some updates, such as KB 976424
, may be needed on computers that are running Windows Server 2008 R2 or Windows Server 2008 if those operating systems are present in the environment.
Collapse this tableExpand this table
|Date when the hotfix was added||Knowledge Base article||Title||Component||Why we recommend this hotfix|
|Jan. 15, 2014||2913695|
|OffloadWrite is doing PrepareForCriticalIo for the whole VHD in a Windows Server 2012 or Windows Server 2012 R2 Hyper-V host||NTFS.sys||Performance improvement when there is an offload write for a virtual hard disk (VHD) in the host. Available for individual download. |
|Jan. 2, 2014||2878635|
|Update is available that improves the resiliency of the cloud service provider in Windows Server 2012: December 2013||Multiple||This hotfix prevents a CSV failover by fixing an underlying issue in NTFS, software snapshots, and by increasing the overall resilience of the Cluster service and CSV during expected pause states. Available for individual download.|
|Nov. 14, 2013||2894464|
|Error message when you try to schedule a shadow copy task in Windows Server 2012||Failover Cluster Resource DLL||This hotfix resolves an error when you try to schedule a shadow copy task on a shared disk. Available for individual download.|
|June 14, 2013||2838043|
|Can't access a resource that is hosted on a Windows Server 2012-based failover cluster||Failover Cluster Resource DLL||This hotfix prevents an error when resources that are hosted on a Windows 8-based or Windows Server 2012-based failover cluster are accessed from a Windows XP-based or Windows Server 2003-based client computer. |
This hotfix also resolves an Event ID 1196 with error The handle is invalid when the cluster network name resource does not come online and register in DNS.
Available for individual download and included in 2889784
(Windows RT, Windows 8, and Windows Server 2012 update rollup: November 2013).
|Jan. 23, 2013||2803748|
| Failover Cluster Management snap-in crashes after you install update 2750149 on a Windows Server 2012-based failover cluster||Failover Cluster Management snap-in||Resolves a crash in the Failover Cluster Management snap-in after update 2750149 is installed on a Windows Server 2012-based failover cluster. Available from Windows Update or the Microsoft Download Center.|
|Nov. 13, 2012||2770917|
| Windows 8 and Windows Server 2012 cumulative update: November 2012||Multiple||Improves clustered server performance and reliability in Hyper-V and Scale-Out File Server scenarios. Improves SMB service and client reliability under certain stress conditions. Install update 2770917 by using Windows Update in order to receive the cumulative update as described in KB 2770917.|
|Nov. 13, 2012||976424|
| Error code when the kpasswd protocol fails after you perform an authoritative restore: "KDC_ERROR_S_PRINCIPAL_UNKNOWN"||KDCSVC||Install on every domain controller that is running Windows Server 2008 Service Pack 2 or Windows Server 2008 R2 in order to add a Windows Server 2012 failover cluster. Otherwise, Create Cluster may fail with error message: CreateClusterNameCOIfNotExists (6783): Unable to set password on <ClusterName$> when it tries to set the password for the cluster computer object. This hotfix is included in Windows Server 2008 R2 Service Pack 1.|
For more information about the recommended hotfixes and updates for Windows Server 2012-based Hyper-V servers and Windows Server 2012 R2-based failover clusters, see the following resources:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
Article ID: 2784261 - Last Review: January 16, 2014 - Revision: 16.0
- Windows Server 2012 Datacenter
- Windows Server 2012 Standard