1 00:00:06,440 --> 00:00:13,760 Before we start talking about upgrading a previous versions of Active Directory to Windows Server 2016 2 00:00:13,760 --> 00:00:21,650 or higher I have to mention that when you demoed ADT as domain controllers that are running Windows 3 00:00:21,650 --> 00:00:29,500 Server 2012 R2 2012 two thousand eight are two and two thousand eight. 4 00:00:29,570 --> 00:00:38,840 The metadata in 80 Days and the obsolete DNS records are not removed automatically. 5 00:00:38,840 --> 00:00:42,680 You have to address this manually or use scripts. 6 00:00:42,680 --> 00:00:45,350 Addressing this issue is not necessary. 7 00:00:45,500 --> 00:00:53,510 When an in place upgrade is taken place now to a greater previous version of 8 it s to Windows Server 8 00:00:53,540 --> 00:01:03,710 2016 ADT yes you can use either of following two methods you can upgrade the operating system of the 9 00:01:03,710 --> 00:01:13,690 existing domain controller as two Windows Server 2016 or you can introduce Windows Server 2016 as domain 10 00:01:13,700 --> 00:01:21,410 controller in the existing domain you can then decommission eight it is domain controllers that are 11 00:01:21,610 --> 00:01:27,080 run in earlier versions of Active Directory of these two methods. 12 00:01:27,080 --> 00:01:34,440 The second is preferred because upgrading operating systems especially on servers that have been running 13 00:01:34,490 --> 00:01:41,950 for several years is often difficult because of all the changes made through the years by installing 14 00:01:41,960 --> 00:01:49,100 new domain controllers that are running Windows Server 2016 it will have a clean installation of Windows 15 00:01:49,100 --> 00:01:59,450 Server 2016 you can deploy Windows Server 2016 servers as member servers in a domain with domain controllers 16 00:01:59,720 --> 00:02:04,590 that are running Windows Server 2008 or newer versions. 17 00:02:04,640 --> 00:02:12,050 However before you can install the first domain controller that has run and Windows Server 2016 you 18 00:02:12,050 --> 00:02:19,250 must upgrade the schema inversions of 80 days prior to Windows Server 2012. 19 00:02:19,260 --> 00:02:25,760 Our 2 You ran that at prep that exit tool to perform scheme upgrades. 20 00:02:25,760 --> 00:02:34,410 However when you deploy new Windows Server 2016 domain controllers in an existing domain and if you 21 00:02:34,410 --> 00:02:41,900 are assigned and with an account that is a member of schema admins and enterprise segments group the 22 00:02:41,960 --> 00:02:49,670 Active Directory Domain Services configuration wizard automatically upgrades the HDD forest schema. 23 00:02:49,760 --> 00:02:59,210 Please know that Windows Server 2016 still provides a 64 bit version of ADD prep so you can run at prep 24 00:02:59,210 --> 00:03:01,250 that exist separately. 25 00:03:01,250 --> 00:03:08,600 For example if the administrator who is installing the first Windows Server 2016 domain controller is 26 00:03:08,600 --> 00:03:13,660 not a member of the enterprise admins or schema admins group. 27 00:03:13,790 --> 00:03:16,360 You might have to run the command separately. 28 00:03:16,490 --> 00:03:23,690 You only have to run at Prep though to see if you're planning an in place upgrade for the first Windows 29 00:03:23,690 --> 00:03:27,920 Server 2016 domain controller in the domain. 30 00:03:28,040 --> 00:03:36,620 So the upgrade process consists of four steps to upgrade the operating system over Windows Server 2012 31 00:03:36,920 --> 00:03:43,520 are two Domain Controller two Windows Server 2016 performs the following steps. 32 00:03:43,520 --> 00:03:52,610 Insert the Windows installation media for Windows Server 2016 and then run set up on the choose what 33 00:03:52,610 --> 00:04:02,060 to keep page select keep personal files and apps and then click Next Step 3 is that on there what needs 34 00:04:02,060 --> 00:04:03,950 your attention page. 35 00:04:03,950 --> 00:04:09,110 Read the notice that Windows server upgrades are not recommended. 36 00:04:09,270 --> 00:04:16,880 Then click on forum and then click refresh and on the ready to install page click install the server 37 00:04:16,880 --> 00:04:21,200 will restart several times while the Great is in place. 38 00:04:21,200 --> 00:04:27,860 Keep in mind that with this type of a great edit the s on the domain controller is upgraded to Windows 39 00:04:27,860 --> 00:04:32,360 Server 2016 HDD apps as a best practice. 40 00:04:32,360 --> 00:04:40,490 You should check for hardware and software compatibility before you perform an upgrade after performing 41 00:04:40,490 --> 00:04:42,530 the operating system upgrade. 42 00:04:42,530 --> 00:04:52,280 Remember to keep your drivers and other services such as monitor run agents and also check for updates. 43 00:04:52,340 --> 00:04:57,850 For both Microsoft applications and non Microsoft software. 44 00:04:58,130 --> 00:05:07,110 Please know that you can upgrade directly from Windows Server 2012 and Windows Server 2012 our two to 45 00:05:07,160 --> 00:05:15,950 vendors Sara 2016 to upgrade servers that are running a version of Windows Server that is older than 46 00:05:16,220 --> 00:05:18,570 Windows Server 2012. 47 00:05:18,590 --> 00:05:29,390 You must either perform an interim upgrade to Windows Server 2012 or 2012 our two or you must perform 48 00:05:29,390 --> 00:05:31,100 a clean installation. 49 00:05:31,100 --> 00:05:40,460 Note that Windows Server 2016 8 it is domain controllers can co-exist as domain controllers in the same 50 00:05:40,460 --> 00:05:46,820 domain as Windows Server 2000 eight domain controllers or newer. 51 00:05:47,070 --> 00:05:54,170 Now as for the clean installation process it takes three steps for clean installation of Windows Server 52 00:05:54,170 --> 00:05:57,320 2016 as a demand member. 53 00:05:57,320 --> 00:06:05,690 You have to run these steps first deploy and configure a new installation of Windows Server 2016 and 54 00:06:05,690 --> 00:06:07,650 then join it to the domain. 55 00:06:07,760 --> 00:06:13,820 Second use or manager to get the Active Directory Domain Services role. 56 00:06:14,060 --> 00:06:22,190 And the third step is that you have to promote the new server to be a domain controller and the domain 57 00:06:22,520 --> 00:06:27,680 by using the Active Directory Domain Services configuration wizard.