How to retain same Computername and IP after migration of DC from 2k12 to 2k19 OS

Mohd Arif 51 Reputation points

I have at least two DC 2012 r2 in development environment. Those two DCs are also holding DNS, DHCP and NPS roles. Now I need to migrate them to 2019 OS but my managers want to retain same computer name and IP address post migration. How can I do it?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,977 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP

    As to retaining the old names / addresses the safest simplest method is to transfer roles off, decommission then follow along below to stand up the new one with correct name / address.

    The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can move on to next one.

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

    0 comments No comments

  2. Thameur-BOURBITA 32,596 Reputation points


    To promote the first domain controller on a existing domain , the forest functional level must be Windows 2008 R2 or higher, and the sysvol replication use DFSR ( FRS is not supported for sysvol replication on a domain controller Windows 2019.

    If you want remain the same IP and name , you can follow those steps:

    1. Build new servers on windows 2019 and join it to domain
    2. Demote the first domain controller and rename it ( check if this Domain Controller holds a one of FSMO roles, if it's the case you should move them to another Domain controller before demote it)
    3. Once the domain controller is demoted , you can rename it to avoid a name conflict during the migration
    4. Rename one of new server windows 2019 with the old name of the first demoted domain controller
    5. Migrate DHCP and NPS from demoted domain controller to new server 2019
    6. Shutdown old domain controller
    7. Promote a domain controller on new server 2019 and change its IP in order to use the same IP of old domain controller
    8. Do the same for the second domain controller

    Please don't forget to mark helpful reply as answer

  3. Andrea Libralato 1 Reputation point

    Hi all,
    in this scenario you need at least a couple of new Windows Servero 2019, one for to became the new DC and one to be renamed as the old DC, but is that possible to get the same result if you have a single server?
    In little scenarios (10-20 client PCs) there is one DC that often is a file/application server too, how can I upgrade Windowd Server mantaing the domain, the server name and the IP address?

    Thanks in advance!

    0 comments No comments