V2V for DC - Windows 2008 R2

[Josephvirtual]

Hello, I am planning to V2V (as part of the datacentre migration) a Windows 2008 R2 domain controller (DC) to new datacentre. As it’s not best practice to convert/ clone domain controller, I am stopping all AD related services and doing the V2V conversion.  When V2V finishes, I power on target VM, connect the network and start the services. We have other live domain controllers in the network.

As I am stopping the AD services, I am assuming that server is down from AD point of view. Is it right assumption?

Do you see any issues? Appreciate your thoughts on this.

I can’t use cold clone. OVF method or parallel DC build and migrate roles for some other reasons. I have no access to source vCenter server.

Cheers!!

[jnord]

I know its a little more of a pain but I would just spin up a new Dc and let it replicate.

I do disaster recovery and taking over the FSMO roles at DR site I have found the best and cleanest way with out issue. V2V works but has not been a 100% all the time if you have other DC in your environment.