Share via

Migrate Active Directory Server 2012 to 2022

Ravinder Makkar 80 Reputation points
2025-06-27T03:20:07.92+00:00

Hi

I am planning to migrate our Active Directory Server from Windows Server 2012 to 2022 and I would like to ensure a smooth transition, especially since we have several applications link like ADFS, Accops, SAP, Firewall, and ISP that are linked to our current AD.

My main concern is with keeping the hostname and IP address the same as the existing 2012 server. If I were to demote or shut down the 2012 server, it could potentially disrupt these applications. Could you please provide guidance on how to approach this migration while maintaining the same hostname and IP address?

Note - I have a few questions regarding the process of creating a new Windows Server 2022 and joining it as an Additional Domain Controller (ADC). If I assign a separate IP address and hostname to the new server and then transfer all roles to it, will my applications experience downtime or be closed during this transition?

Additionally, once the transfer of roles is complete and everything is functioning as expected, am I able to revert the new ADC’s hostname and IP to the original settings? Furthermore, can I demote the old server and give it the same hostname and IP as the old server?

Thanks and Regards

Ravinder Makkar

Windows for business | Windows Server | Networking | Other
0 comments

Answer accepted by question author

  1. Marcin Policht 89,730 Reputation points MVP Volunteer Moderator
    2025-06-27T03:31:16.1333333+00:00

    Here is the procedure you should be able to follow:

    1. Promoting a new Windows Server 2022 as an Additional Domain Controller (ADC).
    2. Transferring FSMO roles and making the new server a Global Catalog.
    3. Replicating AD and DNS.
    4. Ensuring no replication or DNS issues.
    5. Demoting the old server.
    6. Reassigning the hostname and IP.
    7. Prepare and add Windows Server 2022 as an additional domain controller
    • Assign it a unique hostname and separate IP during setup.
    • Join the domain and promote it as an additional domain controller in the same domain
    • Make it a DNS server and Global Catalog.
    1. Transfer FSMO roles

    FSMO transfer is seamless and doesn’t cause downtime.

    • Confirm using: 
        netdom query fsmo
    1. Update AD-integrated services
    • ADFS, Accops, SAP, Firewall, ISP, and others must be confirmed to reference the domain name, not the DC hostname/IP.
    • If they point to domain.local and not directly to dc01.domain.local, you’re generally safe.
    • If hardcoded to old IP or hostname, you’ll need to update these after role transfer or when the new server takes over the IP/hostname.
    1. Verify replication and health

    Run these:

    dcdiag /v
repadmin /replsummary

    Ensure replication is healthy and DNS zones are syncing properly.

    1. Demote the old DC, shutdown the OS and disconnect it from the network.
    2. Reuse the IP and hostname assigned to the demoted DC
    • Rename the new 2022 DC to the hostname assigned to the demoted DC

    To rename the server, run:

    Rename-Computer -NewName "DC01" -Restart
    • Assign the old IP address.
    • Restart the 2022 server.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ravinder Makkar 80 Reputation points
    2025-06-27T04:13:50.5966667+00:00

    Thank you so much for your positive response

    I wanted to clarify that I have a total of 15 servers, including 14 ADC servers at different locations and one PDC in my corporate office. I am set to migrated the 14 ADC (Windows Server 2022) servers at their respective locations, which are all functioning perfectly.

    Regarding the migration of the PDC, I want to confirm that following the steps you provided will not adversely affect the other servers that have already been migrated to Windows Server 2022 at different locations.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.