Skip to main content
Question

Domain Controller migration with Move — AHV to AHV

  • April 23, 2026
  • 4 replies
  • 65 views
A

Hi Experts!

We are planning a migration from an existing AHV cluster (AOS 6.x) to a new AHV cluster running AOS 7.5.1, and we need to migrate our Active Directory Domain Controllers.

We are aware that the official Move documentation states that DC migration is "not recommended but can be performed with some limitations", and that AOS 6.7+ supports VM Generation ID to reduce USN rollback risks.

We have a few questions :

Has anyone successfully migrated Domain Controllers using Nutanix Move in an AHV-to-AHV scenario on AOS 6.7 or higher ?

Did you experience any USN rollback, replication issues, or post-migration AD inconsistencies ?

Any specific pre/post-migration checks you would recommend for this use case ?

Constraint: We need to keep the same IP addresses for our DCs after migration

Thanks in advance

4 replies

J
Forum|alt.badge.img+3

I have done at home lab and it was smooth.

My pre and post migration for you will be to use Microsoft tools for confirmation of dc health (repadmin and etc).

In our organization we can't risk any sort of down time so we went the hard and long way ;)

    JeroenTielen
    Forum|alt.badge.img+8

    I did plenty of them without any issues. I know it is not supported but we tested them correctly before putting them in the correct vlan. 
     

    migrating them the official way is just a pain :(. 

    Nutanix NTC 2022+2023+2024+2025+2026 || Community Excellence Award 2025+2026 || Nutanix NUG Champion || Nutanix Certified Instructor
      LMohammed
      Forum|alt.badge.img+1
      • LMohammed
      • Trailblazer
      • May 1, 2026

      Hi ​@AbdelazizO 

      I can confirm that I have performed Dcs migration using move so many times without running into any issues.

      Keep in mind the following points :

      Before migration, made sure the AD environment is already healthy, clean and no replication issues, regarding FSMO roles, in my personal point in view it’s better to have them all in one dc at this stage of migration. also confirmed that you have proper time sync and that each DC is behaving normally under load.

      ** You should meet all the prerequisites on the Move interface for the selected dc if you have any issue fix it before heading the way**

      During migration, only move one DC at a time and let replication fully converge before touching the next one.

      After migration, you can validated replication again, checked Event Logs for any 2095/USN-related warnings, and forced a few replication cycles just to be sure everything is consistent. and Re-check the AD Sites & Services.

      Once everything is oky Move the other Dcs in the forest.

      2*NCA & 3*NCP & Microsoft & Dell and VmWare certified
        A
        • AbdelazizO
        • Author
        • Voyager
        • May 2, 2026

        Thank you for your responses, I'll get back to you with some feedback :)

        LMohammed
        Forum|alt.badge.img+1
        • LMohammed
        • Trailblazer
        • May 3, 2026

        sure ​@AbdelazizO I’m here to help.

        2*NCA & 3*NCP & Microsoft & Dell and VmWare certified
        Terms & ConditionsAccessibility statement