migrate windows server 2008 R2 domain to windows server 2016 domain

Question

Hello,

I have a following server:

Server 1: (old need to replace)
Physical server.
Windows server 2008 R2
Domain controller
test.local
holding: PDC, RID, Schema, Domain Naming, Infrastructure
Print server
Public and private folder
IP: 192.168.0.254 (only communicate to servers)
IP: 10.100.200.254 (only communicate with workstations) This is a first DNS server for all workstation entry.

Server VM1: New server
Virtual Server
Windows server 2016
Promo to Integrate Domain controller with test.local
IP: 192.168.0.201 (only communicate to servers)
No communication with the workstations

Server VM2: New server (want to be a second domain con
Virtual Server
Windows server 2016
Promo to Integrate Domain controller with test.local
IP: 192.168.0.202 (only communicate to servers)
No communication with the workstations

What I already done:

Moving all PDC, RID, Schema, Domain Naming, Infrastructure to Server VM1.

What I like to do next but not sure. PLEASE HELP!!!!

1st thing:

I like to put another IP: 10.100.200.201 on Server VM1 and 10.100.200.202 on Server VM2 so I can start add in the Printer for the print server on Server VM2 and change the DNS entry of the workstation one by one to point to Server VM1.

BUT someone told me that "Dual homing domain controllers" will happen on my network if I do that and everything will be unstable. In my opinion, this is windows integrate Domain controllers how Dual homing DC happen. Please let me know what is the best way to approach this.

2nd thing:

I don't know what else in our business is hardcode with Server 1 name and IP. I would like to shut down Server 1 after i transfer everything away from this server.

I like to create an entry in Server VM1 DNS so every time when people search for server 1 or it IP, it will point to Server VM1 instead. Which DNS entry do i need to use: Alias, CNAME or DNAME?

Thank you very much for reading into my question and answer it. Greatly Appreciated.

Answer 1

Multi-homing a domain controller will always cause no end to grief for active directory DNS. Do not add the File / Print role to your domain controller. Better option is to stand up a dedicated virtual machine for this role.

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Please don't forget to Accept as answer if the reply is helpful

Answer 3

Hi ,

1st thing:

As Dave said, Multi-homing DC will cause many problem. The recommend way is configuring a new VM for print server.

2nd thing:

If you still need a temporary fix for applications that point to a removed DC by name, you could add a CNAME record and point to new DC.

Best Regards,

Candy

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

If the server have 2 nic with 2 different IP, does the server support to create it own routing table and route the request by itself. I thought it is by design

If you want the server to do routing you can add and configure RRAS role but do not do this on a domain controller, better to stand up a separate windows instance for this purpose.

--please don't forget to Accept as answer if the reply is helpful--

Answer 5

To be clarify on my question:

The workstations has it own iP range and the server has it own IP range. If the server have 2 nic with 2 different IP, does the server support to create it own routing table and route the request by itself. Multi-homing DC will not be an issue here because two different range of network. Is that right?

I don't know why my network was design like this. It was created by a consultant company before I was hired so I am kind of confuse and I don't want to spend a lot of time to change all the workstations, scanner and other devices to same IP range as the servers.