WEBVTT 00:05.620 --> 00:10.630 I'm about to use a term that some network administrators consider offensive. 00:10.720 --> 00:16.420 Now I'm not one to commonly use vulgar expressions in the workplace but I feel that this one needs to 00:16.420 --> 00:17.850 be discussed. 00:17.860 --> 00:26.580 The term is in place upgrade every version of Windows workstation and Windows Server has come with a 00:26.580 --> 00:30.330 list of operating systems that you can upgrade from. 00:30.510 --> 00:37.470 Meaning if you're running a listed operating system you can install in a way that keeps all of the existing 00:37.470 --> 00:40.630 configurations drivers and applications. 00:40.830 --> 00:46.100 But changes to a newer version of Windows for the most part. 00:46.140 --> 00:54.340 That list is the two previous versions of Windows Server but doing this kind of upgrade comes with some 00:54.370 --> 00:56.080 obstacles. 00:56.080 --> 01:02.530 There is never a guarantee that the hardware and drivers supported by a previous operating system will 01:02.530 --> 01:08.880 be supported by a newer more demanding version second over a period of time. 01:08.880 --> 01:17.150 Most computers inherit clutter from different applications user preferences updated drivers and so on. 01:17.340 --> 01:22.700 If all the settings are kept through an upgrade that means the clutter stays as well. 01:24.030 --> 01:30.870 A third challenge is that not all rules and features can survive an upgrade because they're just too 01:30.870 --> 01:37.400 different from one version of the next to survive a simple transfer of settings and there are other 01:37.400 --> 01:38.060 obstacles. 01:38.060 --> 01:45.140 But consider this your starter list given these insurmountable obstacles you may ask why someone would 01:45.140 --> 01:47.820 ever want to upgrade a server in the first place. 01:48.650 --> 01:55.250 Well when Microsoft first announced a semi-annual release channel for Windows Server it became clear 01:55.250 --> 02:02.570 to me that an in-place upgrade option was going to need to become a reality at some point these additions 02:02.570 --> 02:09.080 of Windows Server are designed to come out every six months and have a lifecycle of only about a year 02:09.080 --> 02:10.340 and a half. 02:10.490 --> 02:17.300 New features are being released at breakneck speeds and servers are going to need to be upgraded almost 02:17.300 --> 02:24.550 as fast as these new releases are coming out it stands to reason then that if Microsoft is going to 02:24.550 --> 02:32.410 work out the capability of in-place upgrades for the semi-annual release that that same capability is 02:32.410 --> 02:41.550 going to be transferable to the long term service releases the Windows Server 2019 and beyond for that 02:41.670 --> 02:48.090 and I'm sure other reasons in place upgrade is being touted as one of the noteworthy new features in 02:48.090 --> 02:50.340 Windows Server 2019. 02:50.400 --> 02:58.150 So I decided to give it a try I've mentioned a fairly robust role before a DFS. 02:58.260 --> 03:05.430 This is a Windows 2016 data center server and it's a member of an Active Directory Domain that is hosted 03:05.430 --> 03:12.590 by also Windows Server 2016 and this machine is installed with the role 80 DFS. 03:12.840 --> 03:14.620 All of those features are there. 03:14.700 --> 03:20.010 There are configurations to do federated identity across domain lines. 03:20.040 --> 03:32.130 Let me show you what happens when we've inserted the Windows Server 2019 DVD and go ahead and run setup. 03:32.340 --> 03:37.840 Now this startup screen may look familiar if you've upgraded desktop operating systems before. 03:37.920 --> 03:39.440 I'm going to go ahead and say yes. 03:39.450 --> 03:46.610 Download updates because I know it's not really going to take all that long just to do the check and 03:46.610 --> 03:48.910 I'm being asked to enter my product key. 03:48.920 --> 03:56.750 So let me go ahead and put that in and it will take a couple of screens where it asks me which version 03:56.750 --> 03:58.310 I want to install. 03:58.340 --> 04:06.010 Let's continue with at least the same resources that we have to begin with and after checking with whether 04:06.010 --> 04:10.870 or not I accept the license terms it asks me what I want to keep. 04:10.990 --> 04:17.470 Well if we're testing out in-place upgrades I'm going to tell it that I want to keep everything and 04:17.470 --> 04:25.270 move on to the next screen so you can see this takes a couple of screens before it gets to any warnings. 04:25.520 --> 04:28.920 But take a look at what we're being told right away. 04:28.970 --> 04:35.660 This tells us that the Active Directory Federation service role is installed on this machine and it 04:35.660 --> 04:39.390 goes on to tell us that this isn't going to work. 04:39.500 --> 04:45.710 That that role is not going to be here when we finish the upgrade it will need to be configured differently 04:45.710 --> 04:47.110 later on down the line. 04:48.440 --> 04:55.100 Microsoft has no expectations that everyone is going to want to perform in-place upgrades and they have 04:55.100 --> 05:01.770 these reminders in place for those that try to do it on servers where it's a bad idea. 05:01.830 --> 05:06.180 Now I'm not going on record as saying that in-place upgrades don't work. 05:06.180 --> 05:14.100 I have successfully run this upgrade process on file servers a DHS IP server and even on a radius server 05:14.100 --> 05:19.110 and they all worked out fine but there are rules that shouldn't be upgraded. 05:19.110 --> 05:22.910 We've talked a little bit about how these processes may vary. 05:22.920 --> 05:29.130 We've discussed a DFS and briefly reviewed Active Directory Domain Services. 05:29.130 --> 05:34.830 We've briefly discussed Active Directory Domain Services so you should already be on board with the 05:34.830 --> 05:40.130 idea that these types of upgrades have a little more involved. 05:40.160 --> 05:47.960 Now in addition to performing in-place upgrades where they will work and doing the role specific migration 05:47.960 --> 05:57.110 processes there's another option available to us in migrating a role the server migration tools often 05:57.110 --> 06:06.260 abbreviated to Smick will allow you to create a special tool on your new 2019 19 server that you can 06:06.260 --> 06:17.600 take to an older machine by 2016 or a 2012 R2 server and export or pack up the configuration of say 06:17.630 --> 06:25.760 a DHS CPS server or some other role or feature that is running and has been for some time on an existing 06:25.760 --> 06:33.940 server you can then take that wrapped up export BRING IT OVER TO YOUR 2019 server and import the smug 06:33.950 --> 06:42.020 feature that allows you to port an entire configuration from an old box that needs to be retired to 06:42.020 --> 06:48.050 a new server Cemig tools are something that you're probably going to want to become more familiar with 06:48.560 --> 06:58.070 especially if you have a Windows Server 2012 or 2016 network that you would like to migrate to new installations 06:58.160 --> 07:06.740 of Windows Server 2019 these tools are usually preferred over in place upgrades and are explored in 07:06.740 --> 07:10.820 greater detail in courses on installing and configuring Windows servers.