Active Directory in virtual machine--domain controller virtual machine clone

Before the book, when we see the Active Directory for the enhancement of the virtualized environment, can we think of more scenarios where virtual machine snapshots are used to manipulate domain controller virtual machines?

In fact, the most effective way is to combine the virtualization Daemon services to complete the domain controller virtual machine cloning, so in many places will play a role, such as:

1. Domain controller environment disaster recovery in virtual machine environment

2. Rapid cloning deployment of a new domain controller environment

3. Flexible deployment of domain controller environment

4. Quickly establish a domain controller environment for developing tests

...

Let's go through a test and experience the whole process completely.

First, the prerequisites for implementing a domain controller virtual machine are described:

Domain controllers in the domain PDC emulator FSMO (PDCE) role is Windows Server 2012

PDC emulator need to remain active throughout the cloning process

In addition, looking at the previous blog, we learned that combining the virtual machine snapshot rollback of domain controllers also required the cloning and recovery process:

The cloned source Windows Server 2012 runs on the guest virtual machine

Virtualization Host Platform hypervisor layer support vm-generation ID (Vmgid)

Note the above requirements that domain controller virtual machine clones are not equivalent to snapshot recovery for domain controller virtual machines, for the first domain controller with a PDCE role in the domain, it is not possible to recover by fast cloning, except that the DC can be quickly generated and deployed by cloning. At this point, you can play the speed advantage of fast cloning:-)

To get back to our test environment, now I have two domain controllers DC01 and DC02 in the test environment that I want to build DC03 domain controllers in a fast cloning way.