Assistance Needed with Domain Controller Restoration during VMware to Hyper-V

[parvez_khp]

Dear Team,

We are in the process of migrating from VMware to Microsoft Hyper-V. All our servers are currently hosted in a VMware virtual environment and backed up using Veeam Backup. Our Hyper-V environment is now ready, and we are proceeding with the restoration of virtual machines from Veeam Backup.

As part of our migration process, we are following these steps:

Removing VMware Tools from the virtual machines.
Taking a fresh backup of the virtual machines after removing VMware Tools.
Restoring the updated backup to the Hyper-V environment.
We plan to carry out the restoration during a long holiday or weekend to ensure minimal impact, as there will be no replication traffic during this period.

Currently, we are performing this migration at our head office. At the head office, we have two domain controllers:

A primary domain controller (PDC).
An additional domain controller (ADC).
In addition, we have four other sites, each with two additional domain controllers.

My primary concern is regarding the restoration of the primary domain controller (PDC) from the Veeam Backup:

Are there any specific challenges we might face during or after the restoration of the PDC to the Hyper-V environment?
Could you please advise on best practices for restoring a domain controller to avoid potential issues?
We would appreciate your guidance and recommendations to ensure a smooth migration process.

Thank you in advance for your support!

Regards,
PK

[MOBO]

Hi
why dont you just make new DCs in the hyper-v and join them to the current domain and move the FSMO roles ?
https://learn.microsoft.com/en-us/troub ... fsmo-roles
no downtime and zero chance of the domain getting fracked up

[tyler.jurgens]

When possible, I always take the route Morten recommends.

Move all FSMO roles to DC1.
Decommission DC2 on old cluster.
Provision new DC2 on new cluster.
Move FSMO roles to DC2. Wait a few hours for everything to catch up. Check DNS entries and sites/services.
Decommission DC1 on old cluster.
Provision new DC1 on new cluster. Wait a few hours for everything to catch up. Check DNS entries and sites/services.
Decide where to put FSMO roles - either move or leave as is.

Don't forget to check if you're running DHCP or a Certificate Authority on those DCs. Migrate those as required as well.