How To Install A Domain Controller On Windows Server 2016

To ensure the availability of your Active Directory domain, Microsoft recommends installing at to the lowest degree 2 Agile Directory domain controllers per domain.
Creating a second domain controller for an existing domain also makes it possible to physically movement a domain controller closer to where your users are located in the outcome that your Agile Directory infrastructure spans multiple cities or different countries.

Currently, we have a domain controller for "informatiweb.lan" our domain.

Here is the network configuration used for this tutorial.
So, that the second server (DC2) can find your Active Directory domain and get a copy of the configuration of this domain, brand sure to add the IP address of your 1st domain controller equally the master DNS server on your 2nd server.

Then, on your second server, launch the Add Roles and Features Wizard.

Install the "Active Directory Domain Services" role.

Once the "Active Directory Domain Services" role is installed, click on the "Promote this server to a domain controller" link.

Select "Add together a domain controller to an existing domain", so click the "Select" push button.

Specify the credentials of the Administrator account of the domain yous wish to replicate on your 2nd server (DC2 in our case).
Note that you must prefix the username with the NETBIOS name of the domain to join or by using the "[username]@[domain name]" annotation for this to work.

Select your domain from the list.

The selected domain appears in the wizard, as well as the name of the account used to join the domain.

As when creating the 1st domain controller, yous can activate or non different options :

• Domain Name Organisation (DNS) server
• Global Catalog (GC)
• Read-just domain controller (RODC)

When you install a 2d domain controller in an environment where its security cannot be ensured, it's strongly recommended that yous install it as read-only (RODC).
However, this is part of another tutorial, so we will not be checking this box in this tutorial.

In our case, we have only 1 Active Directory site.
However, when y'all are a multinational, you may take users in several cities or in several countries. In this example, creating an additional domain controller for an existing domain tin can reduce the response fourth dimension for your users past physically bringing it closer.

For more than information about the options available hither, refer to our tutorial : Create an Active Directory domain controller on Windows Server 2016

As when creating the 1st domain controller, a warning is displayed concerning the DNS delegation for the parent zone.
In summary, this is non possible, since the parent zone (".lan" in our case) doesn't exist and is therefore not managed by a server on Windows Server.

Since nosotros are adding a domain controller to an existing domain, we need to replicate the data from an existing domain controller.
In our case, there is just one, and so this choice does not matter.

The sorcerer offers you to choose where to store the different folders of the Active Directory.

A summary is displayed indicating in detail from which source domain controller the data will be replicated.
Click on Side by side.

Wait while checking the system requirements.

Once the checks are complete, click Install.

Note : you can ignore these warnings because nosotros are not using a server on Windows NT four.0 and the parent zone ".lan" doesn't be. Therefore, the creation of the optional DNS delegation cannot exist created.

Look while this new Active Directory domain controller is installed.

As expected, the wizard will replicate the information from the domain controller previously selected as the source.

After installation and replication is consummate, the server will restart.

Log in with the domain administrator account.

If you open the "Active Directory Users and Computers" console, you will see that your 2nd server (DC2 in our case) is now a domain controller.

So that your customer PCs can even so connect even if the 1st domain controller (DC1) fails, exist sure to as well add the IP accost of the 2d domain controller (DC2) in the network configuration of your client PCs.

Source: https://us.informatiweb-pro.net/system-admin/win-server/ws-2016-ad-ds-add-a-domain-controller-to-an-existing-ad-domain.html

Posted by: mendenhallrearandeas.blogspot.com

Share this post