Share via

migrate 2016 active directory to 2019 maintaining hostname and ip address

Prince Akai 20 Reputation points
2024-02-07T14:52:13.22+00:00

Hi All,

I want to migrate the customer’s windows server 2016 domain controller to new server but i want to use same hostname and IP address on newly migrated server. Also, the customer have one domain joined server 2022 on which the customer have Azure ad connect configured on it which syncs to the customer’s office365 tenant. Below is our requirement and some question, hope your expert advice may help in smooth migration. Requirement:

  1. Migrating DC from 2016 to 2019
  2. Retain hostname and IP on new server

Question

  1. After migration what will be the impact on Azure AD Connect synchronization? if hostname and IP remains same.
  2. After migration what will be the impact on Azure AD Connect synchronization? if hostname and IP is not same.

Thank you in advance. Regards

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,977 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.
411 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,807 questions
Accepted answer
  1. Thameur-BOURBITA 32,596 Reputation points
    2024-02-08T00:08:17.01+00:00

    Hi @Prince Akai

    1. After migration what will be the impact on Azure AD Connect synchronization? if hostname and IP remains same.

    No impact. If the Domain controller will keep same IP , it will be able to contact domain control because network flows are already opened.

    1. After migration what will be the impact on Azure AD Connect synchronization? if hostname and IP is not same.

    When you change the IP you should ensure that the network flows is opened with new IP. If it’s not the case it will generate error and cannot contact domain for synchronization.

    When you change the hostname you should check if the connector is not configured to contact a specific domain controller hard coded

    Please don’t forget to accept helpful answer

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest