Virtualization of a domain controller, how to do it right?

Question

Active Directory

Hi all. the question arose there is an old computer on which the server 2012 domain controller is spinning and I want to use VMware vCenter Converter Standalone Client to overtake it to a virtual machine and so that it works on vmware

, I kind of overtook it, but the controller refuses to work.
I read it on the Internet and it turns out that controllers are not amenable to virtualization and for them you need to create a virtual system from scratch and transfer all rights to the virtual one through lowering the rights on the physical server.

is it really true? Or am I still stupid?

Answer 1

If you just need a virtual DC, raise a new one, switch roles and display the old one - voila, a domain controller on a virtual machine. The main thing then is to bother with time synchronization so that there is no such thing that the CD receives time from the host, and the host from the CD.

Answer 2

What kind of nonsense? Standalone Converter does nothing with the machine - it stupidly fills the disk block by block, skipping empty blocks, swap, hibernation file and other things that are not needed.
Converted without autostart, turned off the old one, turned on the new one.

Answer 3

With the virtualization of domain controllers, there is only one recommendation - to keep at least one of them in hardware. But this is actually very optional.
You also need to remember about the time in the domain and the time on the hypervisor. So that it does not work out that the hypervisor throws its wrong time to the domain controller through the integration services.
And in your case, most likely the network connection has fallen off, go in and set up a new one, just like the old one was.