Is it possible to migrate a VM (Domain Controller) from ESXi to AHV? Is there a problem? How to do it?

Hereby a snip from the move documentation: 

• Domain Controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles.

So you should create a new domain controller in AHV and then move the FSMO roles. When all is over you should decommission the old domain controller.

Hereby a link to the move documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Move-v5_5:Nutanix-Move-v5_5

While it is recommended that a new DC is created and I would also recommend that if at all possible, from my experience I did have to move our Domain Controllers and we had no issues using either Move or with a Protection Domain on a couple different occasions with some data center moves and our own vmware to ahv migration. Just to be clear though your results my vary. Good luck on either route. 

Same experience here as Jamie is telling ;) But the recommended way is create a new one. (But me to, successfully moved domain controllers)

recommendation will be to create a new VM on the Nutanix and then sync to it .

does it work with MOVE, most probably yes.but if you faced any issue, you will get the above recommendation from nutanix and Microsoft :)

Hi Jeroen, Jamie and Ahmad.

Thank you very much for your answers and recommendations. I'll proceed to create a new VM in Nutanix as a Domain Controller and move the FSMO roles.

Thanks.

While it’s completely unsupported, I successfully migrated a Server 2008 DC from ESXi to AHV with Move. Only one issue- the network card didn’t carry over the IP address, but once that was fixed it just worked, no issues whatsoever. I started the seeding at around 4am using the scheduler, completed cutover about 7:30 or so.

Dear All,

I have done more then 10,000 workload migrations and following is my recommendation. May helpful to you.

Note: DON”T decommission your original AD server instance for at-least one week that can be used as roll-back plan, if something goes wrong with migrated or new instance. 

V2V Migration: VMware ESXi to AHV

Use Case 1: If it is windows server 2012 or older. It is recommended to deploy new Widows server with 2016 / 2019 or later and move AD roles.

Use Case 2: If you are running Windows serve 2016 or later then it can be migrated from P2V to ESXi to AHV probably without any AD functionality issue. 

Note: you may need to re-active Windows license again in some cases.

P2V Migration: Physical to ESXi to AHV 

If you are planning to migrate physical server to ESXi to AHV.

Following blogs may help to troubleshoot the P2V migration issues:

1. P2V Migration Error: VMware converter failed a general system error occurred internal error
    
2. Linux P2V Migration Error: Make sure that you can run sudo without entering a password – Troubleshooting
    
3. P2V Migration Error: VMware vCenter Converter insufficient permissions to connect to admin$

Thank you,