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.

IFM verification limitations in Windows Server 2012 Server Manager


View products that this article applies to.

Symptoms

Symptom 1

When you use Windows Server 2012 Server Manager to�install Active Directory Domain Services (AD DS) on an additional domain controller by using the�Install from Media (IFM) option on the�Additional Options page, the Verify button seems to do nothing when you click it.

Symptom 2

When you select full domain controller IFM files to install AD DS on a read-only domain controller (RODC), the�Verify button and the Prerequisites Check�page do not report errors. However, if you try to install later, the installation fails, and you receive the following error message:

An error occurred while trying to configure this machine as a domain controller. The Install-From-Media promotion of a Read-Only DC cannot start because the specified source database is not allowed. Only databases from other RODCs can be used for IFM promotion of a RODC.

Note�If you are using RODC IFM files for a full domain controller installation, you receive the following error message, as expected:

could not validate media path

↑ Back to the top


Cause

Cause 1

Verification occurs automatically every time that you specify a new path by using the browse ("...") button. If the media is invalid, you receive an error message when you browse to that folder. However, if you type the path or change the contents of the path, you must click�Verify�to test the contents. Until� verification occurs, the�Next�button is not displayed.�

No messages or dialog boxes are displayed if verification passes. Information is displayed only if an error is found.

Cause 2

The Server Manager IFM verification only validates the presence and integrity of the media. It does not match the media type to the previously selected domain controller type. Also, there is no prerequisite validation of the IFM option.�

When you validate full domain controller IFM files on an RODC, all the files are present. However, an RODC IFM option does not contain the registry output that is needed by a full server, and you receive an error.

You should always use the correct IFM option together with the correct kind of server.

↑ Back to the top


Resolution

To resolve the error that is mentioned in the "Symptom 2" section, create a new IFM output from the correct kind of domain controller, and then try installation again.

↑ Back to the top


More information

This behavior is by design.

For more information about how to create the domain controller IFM option, go to the following Microsoft TechNet website:

↑ Back to the top


Keywords: KB2737516

↑ Back to the top

Article Info
Article ID : 2737516
Revision : 5
Created on : 10/2/2012
Published on : 10/2/2012
Exists online : False
Views : 340