Consider the following scenario:
- You have a failover cluster and the cluster spans two datacenters with different network subnets.
- Node weight and quorum is configured to make sure that the primary datacenter would remain primary.
- A connectivity issue occurs between datacenters.
Hotfix informationImportant If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there's 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 get 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 don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix in Windows Server 2012 R2, you must install April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355).
Registry informationTo use the hotfix in this package, you don't have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix doesn't replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.