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.

The Next button is not available on the Domain Controller Options page


View products that this article applies to.

Symptoms

When you use Windows Server 2012 Server Manager to install Active Directory Domain Services (AD DS) on an additional domain controller or on the first domain controller in a new child or tree domain, the�Next button is never available on the�Domain Controller Options�page.�For example:



This prevents the installation of AD DS on the domain controller.

↑ Back to the top


Cause

This issue occurs for one of the following reasons:
  • You didn't type and confirm a Directory Services Restore Mode (DSRM) password.�
  • Your forest contains more than one site, and the computer on which you are installing AD DS belongs to an IP subnet that is not defined or is not associated with a logical site. Notice that in the screen shot, the�Site name�list is empty. This means that�no site could be automatically selected.

↑ Back to the top


Resolution

There are two possible resolutions for the second cause. The first resolution is to make sure�that all network subnets are defined in the forest and�that all sites in the topology have valid associated subnets. You can do this by using�Dssite.msc�or the Windows Server 2012 version of the Active Directory Windows PowerShell module. After you do this, you should try to install AD DS again by using Server Manager. The correct site will be detected automatically.

We recommend this�resolution.

The second resolution is to select the correct site name from the Site name list manually. For example:



We do not recommend this resolution as strongly because it masks the underlying problem. This is that clients, servers, and domain controllers that are not associated with AD DS sites correctly do not work efficiently with DFS Namespace referrals, Windows Server 2012 Direct Access, or other site-aware technologies. One or more incorrectly designed sites and subnets are present in the forest.

↑ Back to the top


More information

To detect all AD DS sites that are missing associated subnets, you can use the following sample Windows Server 2012 Active Directory Windows PowerShell command:�
get-adreplicationsite -filter * -property subnets | where-object {!$_.subnets -eq "*"} | format-table name�

↑ Back to the top


Keywords: KB2737807

↑ Back to the top

Article Info
Article ID : 2737807
Revision : 7
Created on : 9/22/2012
Published on : 9/22/2012
Exists online : False
Views : 221