How to Join Windows Server 2016 to an existing Active Directory Domain

How to Join Windows Server 2016 to an existing Active Directory Domain

In this article, I will show you how to Join Windows Server 2016 to an existing Active Directory Domain wherein the existing domain controller is also a Windows 2016 Server. There are few points which you need to take care before you proceed with joining the windows server 2016 to an existing AD Domain.

There are two ways to join the new Windows Server 2016 to an existing Active Directory Domain:

TYPE 1: Online Domain Join (Standard Method)

TYPE 2: Offline Domain Join (Used for servers in remote locations)

 

STEPS to be followed under TYPE 1

  1. Check IP Configuration
  • Make sure you have static IP configured on the new server.
  • Make sure the Primary DNS is pointing to the domain controllers server (assuming you don’t have separate DNS server)
  • Confirm the communication between the new server and your domain controller by pinging (try to ping via hostname instead of IP)

 

2. Launch “RUN” either by pressing “Windows + R” keys simultaneously or right click on start menu and hit Run.

3. Type sysdm.cpl in the Run field and hit Ok, It will launch System properties.

Launch System Properties
Launch System Properties
System Properties Window
System Properties Window

4. Click on “change” button and you will see a new window up. In the new window click on “domain” radio button and type the domain name in the field and hit Ok.

Joining to the domain
Joining to the domain

5. You will be prompted with a credentials window in which you will have to supply domain admin credentials.

Credentials window
Credentials window

In my case wherein I was doing this lab in a virtualized environment and cloned the machine instead of doing a fresh Install I have encountered with the following error:

Duplicate SID error
Duplicate SID error

Well, its good that I got a chance to show you this error and how to fix it. (Usually when it’s not cloned successfully the SID Security-Identifier remains the same on both machines and you need to fix it using a utility called SYSPREP)

NOTE: You can expect the Duplicate SID error in case you have not run Sysprep on Gold Image when using Windows Deployment Server.

You can check this article on how to use SysPrep:

 




Search blogs

Bitnami