1
00:00:06,460 --> 00:00:14,200
The fastest way to deploy multiple computers with identical configurations especially when those computers

2
00:00:14,200 --> 00:00:22,450
are running the virtual last environment such as Microsoft hyper v is to clone those computers clone

3
00:00:22,450 --> 00:00:31,020
and corpus the virtual hard drive of the computers and change minor configurations such as computer

4
00:00:31,030 --> 00:00:34,090
name sound IP addresses to be unique.

5
00:00:34,120 --> 00:00:37,630
Then the computers are immediately operational.

6
00:00:37,630 --> 00:00:46,990
This process also referred to as provision and computers is a central technology of private clouds.

7
00:00:46,990 --> 00:00:57,340
Prior to Windows Server 2012 you could clone domain members but you are not able to clone domain controllers

8
00:00:57,520 --> 00:01:03,160
in Windows Server 2016 and Windows Server 2012.

9
00:01:03,160 --> 00:01:05,650
You can clone domain controllers.

10
00:01:05,680 --> 00:01:12,940
The follow is to narrow benefit from virtual domain controller cloning unit to rapidly deploy additional

11
00:01:12,940 --> 00:01:21,430
domain controllers in a new domain unit to quickly restore business continue to during disaster recovery.

12
00:01:21,580 --> 00:01:27,800
You can restore HDD capacity by using clone and to quickly deploy domain controllers.

13
00:01:27,880 --> 00:01:35,530
You can optimize private cloud deployments you can leverage the flexible provision and domain controllers

14
00:01:35,560 --> 00:01:39,830
to accommodate the increased scale requirements.

15
00:01:39,850 --> 00:01:44,260
You can quickly meet increased capacity needs and branch offices.

16
00:01:44,290 --> 00:01:51,460
You can do this either by clone an existing domain controllers in branch offices or by cloning them

17
00:01:51,460 --> 00:01:59,740
in the data center and then transferring them to branches by using hyperbole clone and domain controllers

18
00:01:59,800 --> 00:02:08,800
requires the following a hyper wiser that supports virtual machine generation identifier such as hyper

19
00:02:08,800 --> 00:02:17,590
v in Windows Server 2012 or later you'll need domain controller assess guest operate and systems based

20
00:02:17,590 --> 00:02:25,270
on Windows Server 2012 or later you'll need a domain controller that you want to clone or source a domain

21
00:02:25,270 --> 00:02:31,730
controller that must run a virtual machine guest on the supported hypervisor.

22
00:02:31,750 --> 00:02:38,110
You also need a PDA emulator that runs on Windows Server 2012 or later.

23
00:02:38,140 --> 00:02:45,640
It's possible to clone domain controllers run on Windows Server 2012 when earlier versions of domain

24
00:02:45,640 --> 00:02:48,850
controllers exist in your environment.

25
00:02:48,850 --> 00:02:55,900
However the domain controller that holds the PDC emulator feeds morale needs to support the clone and

26
00:02:55,900 --> 00:03:04,390
process the PDA emulator must be on line when the virtual domain controller clone starter for the first

27
00:03:04,390 --> 00:03:05,150
time.

28
00:03:05,170 --> 00:03:13,660
Now to help ensure that Ada DNS administrators authorize clone and virtualize domain controllers a member

29
00:03:13,660 --> 00:03:22,080
of the domain admins group needs to prepare a computer for clone in hyper v administrator or Sara enabled

30
00:03:22,080 --> 00:03:30,790
to clone a domain controller without Ada s administrators and similarly added Yes administrators are

31
00:03:30,790 --> 00:03:36,010
unable to clone a domain controller without hyper v administrators.