Wilf
asked on
Adding a 2016 server as a DC to a 2008 R2 network
I am trying to add a 2016 standard server as a DC to a 2008 R2 network. Once it is added, it will become the only Domain controller on the network and the 2008 R2 will be removed.
I have joined the domain, and added Active Directory Domain Services, DHCP Server, DNS Server and the various roles. When I go to promote the server, I get a " cannot find the domain controller error and suggests I check the spelling of the domain.
The domain is chosen from the drop down menu, and is correct.
Should I tried to promote it to a domain controller prior to joining the network?
I have joined the domain, and added Active Directory Domain Services, DHCP Server, DNS Server and the various roles. When I go to promote the server, I get a " cannot find the domain controller error and suggests I check the spelling of the domain.
The domain is chosen from the drop down menu, and is correct.
Should I tried to promote it to a domain controller prior to joining the network?
Joining the domain was fine. However, I would've simply chosen ADDS and DHCP for server roles. Once those were done, then I would've gone ahead and promoted to a DC.
You need to join to the existing domain before promoting to be a DC.
Check the DNS settings in the server to make sure they are pointing to the old DC for now.
Is the current domain controller online and accessible from this new server? (Are they on the same subnet? Are there any firewalls?). Sounds like you did things correctly so far. (It has to be on the domain before it can be the domain controller). On the NEW server if you launch Active Directory Users and Computers and then drill down to the Domain Controllers OU, do you see the CURRENT domain controllers?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The DCDIAG did identify an old DNS entry that could have been removed. Upon cheking the setup, it was discovered that both Ethernet ports had been connected to the switch and the Team configuration had not been completed. Once the Team configuration was completed, the DC promoted