Windows Server 2016-Deploy the first domain controller

We mentioned in the previous section about Winser Active directory Domain Services overview, the new features and prerequisites in the WinSer2016 ad domain, and so on, this section will bring you WinSer2016 to deploy the first domain-controlled operation process. (PS. Enterprises in the preparation of the domain must be based on the enterprise's system, network and other practical needs to make a rationalized planning framework, to facilitate the adjustment of the post-structure, upgrade, etc.), topology and operation steps are as follows:

role	hostname	ip address
	major	192.168.156.1
auxiliary domain	SPARE/BDC	192.168.156.2
Read-only domain control	Brodc	192.168.156.3

One: Add the Active Directory Domain Services role:

1.1. Open Server Manager and select "Add Roles and Features":

1.2, add the wizard, the default choice next to continue:

1.3. Select "Select Server from Server Pool" and click Next to continue:

1.4. In the server role bar, tick "Active directory Domain Services" to add the required features for AD DS:

1.5, the function default next can:

1.6, the default next continue:

1.7. Confirm that the role information has been added and click Install to continue:

1.8. The Domain service role installation is complete. Next we perform the elevation domain controller operation.

Two: Raise the domain controller:

2.1, before upgrading the first domain controller, please fixed the IP address information, as follows:

2.2, click "Promote this server to a domain controller" in the 1.8 step, select "Add New Forest" in the Popup Deployment Wizard interface and enter the corresponding root domain name azureyun.local:

2.3, select the New forest and root domain functional level, 2016 forest, domain functional level defaults to Winser2016, by default, the domain Name System (DNS) server and global Catalog (GC) (G), two times the directory Restore Mode password, the next step continues:

2.4. Because it is the first domain controller in the domain, the DNS server delegation cannot be created by default, ignoring and continuing next:

2.5. Confirm the NetBIOS domain name, the default is the same as the root domain prefix, and proceed directly to the next step:

2.6. Specify the AD DS database, log file, and SYSVOL location, this example accepts the default (the production environment recommends that three are stored separately) and the next step continues:

2.7. Confirm that you have entered the information click Next to continue:

We can also install the first domain control through the PowerShell script, which reads as follows:

#用于azureyun. Local AD DS Deployment PowerShell script Import-module addsdeploymentinstall-addsforest '-creatednsdelegation: $false '- DatabasePath "C:\Windows\NTDS" '-domainmode "Winthreshold" '-domainname "azureyun.local" '-domainnetbiosname " Azureyun "'-forestmode" Winthreshold "'-installdns: $true '-logpath" C:\Windows\NTDS "'-norebootoncompletion: $false '- Sysvolpath "C:\Windows\SYSVOL" '-force: $true

2.8. After the prerequisite check is correct, click Install to continue:

2.9. Installation configuration The first domain controller is complete (for NT4.0 and DNS delegation warning information can be ignored).

Third, verify the domain controller:

3.1. View added "Active Directory Users and Computers" management tool and display the relevant azureyun.local domain information properly, view the relevant area of DNS Manager add and include domain controller major-192.168.156.1 parsing information, etc.

3.2. Open the Local service to view active Directory Domain Services services running.

3.3. Verify that the computer role is primary through net accounts

3.4. After the default domain controller is successfully created, the default Netlogon, sysvol corresponding shared folder is created locally to facilitate subsequent synchronization, and so on.

The first domain controller was successfully installed.

Windows Server 2016-Deploy the first domain controller