1 00:00:06,460 --> 00:00:14,050 If you have a network connection between sites that are slow unreliable or costly you might find it 2 00:00:14,140 --> 00:00:20,690 necessary to add another domain controller at a remote location or branch office. 3 00:00:20,710 --> 00:00:28,300 In this scenario it is often better to deploy two days to a server by installing it from media rather 4 00:00:28,300 --> 00:00:31,120 than by deploying it over the network. 5 00:00:31,120 --> 00:00:39,430 For example if you connect to a server that is in a remote office sound to your server manager to install 6 00:00:39,430 --> 00:00:47,710 a days the entire HDD database and the system or folder will cooperate to the new domain controller 7 00:00:47,800 --> 00:00:50,970 over a potentially unreliable Ram. 8 00:00:50,980 --> 00:00:58,690 Alternatively to significantly reduce the amount of traffic moving over the west link you can create 9 00:00:59,020 --> 00:01:07,380 a backup or faded yes perhaps two years b drive and take this back up to the remote location. 10 00:01:07,440 --> 00:01:16,120 Many already the remote location and run server manager to install ADT yes you can select the install 11 00:01:16,120 --> 00:01:17,980 for a media option. 12 00:01:17,980 --> 00:01:21,800 Most of the coping then are curious locally. 13 00:01:21,910 --> 00:01:27,910 In this scenario only security related traffic uses the rand link. 14 00:01:27,910 --> 00:01:36,190 The rand link also helps ensure that the new domain controller receives any changes made to the central 15 00:01:36,250 --> 00:01:43,540 ADT years after you created the install from media backup to install a domain controller by installing 16 00:01:43,540 --> 00:01:49,320 for media browse to the main controller that is not an raw DC. 17 00:01:49,390 --> 00:01:59,830 Use the anti DLC steal command line tool to create a snapshot of the ADF database and then copies is 18 00:01:59,830 --> 00:02:07,750 a snapshot to the sorrow that will promote to a domain domain controller you server manager to promote 19 00:02:08,020 --> 00:02:16,480 the server to domain controller by selecting the install for a media option and then providing the local 20 00:02:16,480 --> 00:02:22,620 path to the install from media directory that you previously created. 21 00:02:22,630 --> 00:02:30,250 The procedure is as follows on the full domain controller at an administrative command prompt time the 22 00:02:30,250 --> 00:02:39,440 following commands where your files are located on IE fam folder on C drive you can name this folder 23 00:02:39,460 --> 00:02:43,250 whatever you like but for this example we'll use this name. 24 00:02:43,510 --> 00:02:49,990 So this folder is a destination directory that will contain the snapshot of the aid it is database. 25 00:02:50,200 --> 00:02:57,600 So please type and TADS you to activate instance enter the s I fam. 26 00:02:57,800 --> 00:03:01,460 Create this world full circle on backslash. 27 00:03:01,490 --> 00:03:08,260 I've found the second step is on the server that you are promoting to the main controller perform the 28 00:03:08,260 --> 00:03:09,640 following steps. 29 00:03:09,710 --> 00:03:13,990 User or manager to add the ADA s role. 30 00:03:14,110 --> 00:03:21,730 Wait while the ADA deals files install and turn server manager click the notification item and then 31 00:03:21,790 --> 00:03:30,250 under post deployment configuration click promote the server to the main controller the Active Directory 32 00:03:30,280 --> 00:03:38,120 Domain Services configuration resort runs and the next step is on the appropriate page of The Visitor. 33 00:03:38,170 --> 00:03:46,020 Select the install from mid option and then provide the local path to the snapshot directory. 34 00:03:46,330 --> 00:03:49,550 Edit Yes install from the snapshot. 35 00:03:49,550 --> 00:03:57,760 Note that when the Domain Controller restarts it contacts the other domain controller as in the domain 36 00:03:57,760 --> 00:04:04,720 and updates aided yes with any changes made after the creation of the snapshot.