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. Update adds four-node failover cluster deployment support in Windows Server 2012

Update adds four-node failover cluster deployment support in Windows Server 2012

View products that this article applies to.

Introduction

This update introduces a new feature for the OEM Appliance OOBE feature to support four-node failover cluster deployment in Windows Server 2012. This update also adds a wizard to create a domain controller on a Hyper-V virtual machine to use in a first-server environment. The wizard supports the Cluster-in-a-Box design.

Notes
  • Currently, the OEM Appliance OOBE feature supports only two-node failover cluster deployment.
  • This update is not intended for installation by end-users. This is an optional update for OEM computer manufacturers that use the OEM Appliance OOBE feature for rapid server deployment.         

↑ 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 use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must 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 that are 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 8 hotfixes and Windows Server 2012 hotfixes are included in the same 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" on the page. Always refer to the "Applies To" section in articles 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
  • The MANIFEST (.manifest) files and the MUM (.mum) files that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, 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
Microsoft.windows.oemoobe.common.dll6.2.9200.16563478,20826-Mar-201309:05x64
Microsoft.windows.oemoobe.common.dll6.2.9200.20673638,97627-Mar-201304:11x64

↑ 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.

↑ Back to the top

More Information

For more information about how to set up an OEM Appliance OOBE four-node cluster, go to the following Microsoft website: 
Windows Server 2012 OEM Appliance OOBE four-node cluster setup guide

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 nameAmd64_3023995d2de3430479901a752af46383_31bf3856ad364e35_6.2.9200.20673_none_58f979683760b986.manifest
File versionNot applicable
File size705
Date (UTC)27-Mar-2013
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_6153922de5c11fc880acc72cf4ab2223_31bf3856ad364e35_6.2.9200.16563_none_09bd206284b8b9aa.manifest
File versionNot applicable
File size705
Date (UTC)27-Mar-2013
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_628644592e06543ab27a13c573ed7384_31bf3856ad364e35_6.2.9200.16563_none_4f02509479728264.manifest
File versionNot applicable
File size705
Date (UTC)27-Mar-2013
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_ca9a9b82630b9070986201b3b97f45e9_31bf3856ad364e35_6.2.9200.20673_none_77946d02ec8fe0a6.manifest
File versionNot applicable
File size705
Date (UTC)27-Mar-2013
Time (UTC)18:15
PlatformNot applicable
File nameMsil_microsoft.storagemanagement.oobe_31bf3856ad364e35_6.2.9200.16563_none_005d66e04c66b939.manifest
File versionNot applicable
File size41,457
Date (UTC)26-Mar-2013
Time (UTC)09:21
PlatformNot applicable
File nameMsil_microsoft.storagemanagement.oobe_31bf3856ad364e35_6.2.9200.20673_none_00dc33bf658c74f4.manifest
File versionNot applicable
File size44,623
Date (UTC)27-Mar-2013
Time (UTC)04:25
PlatformNot applicable
File nameMsil_microsoft.windows.oemoobe.common_31bf3856ad364e35_6.2.9200.16563_none_8b2c4d6829fa219a.manifest
File versionNot applicable
File size1,659
Date (UTC)26-Mar-2013
Time (UTC)09:21
PlatformNot applicable
File nameMsil_microsoft.windows.oemoobe.common_31bf3856ad364e35_6.2.9200.20673_none_8bab1a47431fdd55.manifest
File versionNot applicable
File size1,659
Date (UTC)27-Mar-2013
Time (UTC)04:25
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2769588
Revision : 1
Created on : 1/7/2017
Published on : 5/20/2013
Exists online : False
Views : 304