You cannot join a Windows Server 2012-based failover cluster to a domain by using the OEM Appliance OOBE feature

Article translations Article translations
Article ID: 2795643 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Assume that you use the OEM Appliance OOBE feature to deploy a two-node failover cluster that is running Windows Server 2012. When you are prompted to specify the Active Directory domain and user credentials during the deployment, you enter a valid user name and password to join the domain. In this situation, you cannot join the domain. Additionally, you receive an error message that resembles the following: 
Domain name\user name is not granted access rights to resolve the domain account

Cause

This issue occurs because the WinNT provider API cannot resolve a domain user account before the computer joins the domain.

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

Collapse this imageExpand this image
assets folding start collapsed
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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • 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 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
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Createpool.exe6.2.9200.164937,68004-Jan-201311:14x64
Createvirtualdisk.exe6.2.9200.164937,68004-Jan-201311:14x64
Microsoft.windows.server.ps.commands.dll6.2.9200.1649315,87204-Jan-201311:14x64
Msoobe_oem.exe6.2.9200.1649351,20004-Jan-201311:14x64
Oemoobe.exe6.2.9200.16493358,40004-Jan-201311:14x64
Oobediscoveryservice.exe6.2.9200.164938,70404-Jan-201311:14x64
Preparecluster.exe6.2.9200.16493236,03204-Jan-201311:14x64
Provisionvolume.exe6.2.9200.164937,68004-Jan-201311:14x64
Serverceipoptindlg.exe6.2.9200.164937,16804-Jan-201311:14x64
Serverweroptindlg.exe6.2.9200.164937,16804-Jan-201311:14x64
Setupcluster.exe6.2.9200.16493206,33604-Jan-201311:14x64
Createpool.exe6.2.9200.205987,68004-Jan-201309:49x64
Createvirtualdisk.exe6.2.9200.205987,68004-Jan-201309:49x64
Microsoft.windows.server.ps.commands.dll6.2.9200.2059815,87204-Jan-201309:49x64
Msoobe_oem.exe6.2.9200.2059851,20004-Jan-201309:49x64
Oemoobe.exe6.2.9200.20598358,40004-Jan-201309:49x64
Oobediscoveryservice.exe6.2.9200.205988,70404-Jan-201309:49x64
Preparecluster.exe6.2.9200.20598236,03204-Jan-201309:49x64
Provisionvolume.exe6.2.9200.205987,68004-Jan-201309:49x64
Serverceipoptindlg.exe6.2.9200.205987,16804-Jan-201309:49x64
Serverweroptindlg.exe6.2.9200.205987,16804-Jan-201309:49x64
Setupcluster.exe6.2.9200.20598206,33604-Jan-201309:49x64
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed


Status

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

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

Collapse this imageExpand this image
assets folding start collapsed

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
Collapse this imageExpand this image
assets folding start collapsed
Collapse this tableExpand this table
File nameMsil_microsoft.storagemanagement.oobe_31bf3856ad364e35_6.2.9200.16493_none_003cf5364c7f0fe5.manifest
File versionNot applicable
File size41,457
Date (UTC)04-Jan-2013
Time (UTC)11:25
PlatformNot applicable
File nameMsil_microsoft.storagemanagement.oobe_31bf3856ad364e35_6.2.9200.20598_none_00cb937365982e62.manifest
File versionNot applicable
File size41,457
Date (UTC)04-Jan-2013
Time (UTC)10:02
PlatformNot applicable
Collapse this imageExpand this image
assets folding end collapsed
Collapse this imageExpand this image
assets folding end collapsed

Properties

Article ID: 2795643 - Last Review: February 13, 2013 - Revision: 2.0
Applies to
  • Windows Server 2012 Datacenter
  • Windows Server 2012 Standard
Keywords: 
kbqfe kbautohotfix kbhotfixserver kbexpertiseadvanced kbfix kbsurveynew kberrmsg KB2795643

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com