Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Changed cluster properties revert to default values on cluster nodes that run Windows Server 2012

Changed cluster properties revert to default values on cluster nodes that run Windows Server 2012

View products that this article applies to.

Symptoms


Assume that you have a two-node failover cluster that is running Windows Server 2012. You change the heartbeat related properties, such as SameSubnetDelay and SameSubnetThreshold, by running the Cluster /prop command. In this situation, the properties are changed successfully and work correctly. However, if you restart either of the nodes or rejoin either of the nodes to the cluster, the properties revert to the default value.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows Server 2012 hotfixes are included in the same Windows 8 hotfix packages. However, only Windows 8 is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8". Always refer to the "Applies To" section in an article to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.2.9200.209737,256,06422-Feb-201405:24x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File propertyValue
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.20973_none_131ec69d44665fdc.manifest
File versionNot applicable
File size10,086
Date (UTC)22-Feb-2014
Time (UTC)08:02
PlatformNot applicable
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.2.9200.20973_none_1d7370ef78c721d7.manifest
File versionNot applicable
File size6,868
Date (UTC)22-Feb-2014
Time (UTC)05:46
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbhotfixserver, kbfix, kbqfe, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2935773
Revision : 1
Created on : 1/7/2017
Published on : 5/14/2014
Exists online : False
Views : 187