Share via

migrate windows server 2008 R2 domain to windows server 2016 domain

Duc Hong Huynh 21 Reputation points
2021-03-29T17:17:07.783+00:00

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.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,428 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,034 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
416 questions
0 comments
Accepted answer
  1. Anonymous
    2021-03-29T19:27:51.253+00:00

    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--

6 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-03-30T18:47:32.837+00:00

    Multi-homing DC will not be an issue here because two different range of network. Is that right?

    No that's not correct. A domain controller can service multiple subnets but do the routing on layer 3 hardware not on windows.

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

    0 comments
  2. Anonymous
    2021-04-02T13:16:03.983+00:00

    Any progress or updates?

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

    0 comments