Symptom 1When 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 2When 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
Cause 1Verification 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 2The 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.
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.
Article ID: 2737516 - Last Review: 2 Oct 2012 - Revision: 1