<div>
stop ALL the services before you start.<br />
<br />
its recommended to create a new server, promote to domain controller, and transfer roles.
</div>


<div>
Thanks Andrew, just to be sure I understand.... It is possible to p2v a domain controller if all services are stopped during the transfer, but creating a new VM, promoting to DC. Then demoting the existing physical DCs, virtualising them, and then re-promoting them is better and safer?<br />
<br />
Thanks - Jerry
</div>


<div>
Thanks Andrew, will take the safest option!
</div>


<div>
<div class="content wysiwyg-content">
I had this question after viewing <a href="https://www.experts-exchange.com/articles/17453/HOW-TO-P2V-V2V-for-FREE-to-Hyper-V-Microsoft-Virtual-Machine-Converter-3-1.html" rel="ugc">HOW TO: &nbsp;P2V, V2V for FREE to Hyper-V - &nbsp;Microsoft Virtual Machine Converter 3.1</a>.<br />
<br />
What special considerations should I bear in mind for visualising 2 domain controllers using MVMC 3.1<br />
<br />
There is no mention in the admin guide.
</div>
</div>


I had this question after viewing HOW TO:  P2V, V2V for FREE to Hyper-V -  Microsoft Virtual Machine Converter 3.1 (https://www.experts-exchange.com/articles/17453/HOW-TO-P2V-V2V-for-FREE-to-Hyper-V-Microsoft-Virtual-Machine-Converter-3-1.html).

What special considerations should I bear in mind for visualising 2 domain controllers using MVMC 3.1

There is no mention in the admin guide.

MVMC converting physical domain controller to Virtual

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.