WEBVTT 00:05.620 --> 00:09.750 I was speaking recently with a network administrator for a global company. 00:09.760 --> 00:15.760 He told me that his I.T. infrastructure was out of date because his Windows servers were a version or 00:15.760 --> 00:25.560 two behind the newest thing for Microsoft the long term Windows Server releases like Server 2012 2016 00:25.860 --> 00:32.000 and now Windows Server 2019 are meant to remain functional for more than just a couple of years. 00:32.000 --> 00:39.600 So this is a normal situation a new one will come out every two to four years and they'll be supported 00:39.600 --> 00:42.480 for approximately 10 years. 00:42.540 --> 00:46.740 That means you're never really forced into a quick upgrade. 00:46.740 --> 00:54.270 In fact I'll go on record as saying that the release of a newer version of Windows Server is never the 00:54.270 --> 00:57.180 reason to upgrade your entire network. 00:57.210 --> 01:02.250 Let me tell you instead why you should install a newer version of Windows Server. 01:02.450 --> 01:10.040 You should plan to start integrating Windows Server 2019 installations into your network if you're expanding 01:10.040 --> 01:16.640 a data center and would like the control and flexibility of being able to group your clusters and take 01:16.640 --> 01:24.410 advantage of advances in storage spaces direct you might consider Windows Server 2019. 01:24.480 --> 01:31.290 If your older file servers need to be retired and you need a new system that will allow you to easily 01:31.290 --> 01:39.910 migrate data and entire configurations to new servers without disrupting service or you might be looking 01:39.910 --> 01:47.160 for any of the features rolled out in the semi-annual releases of Windows Server but maybe you didn't 01:47.160 --> 01:53.660 want the volatility of an operating system that will reach end of life in less than two years and this 01:53.660 --> 01:55.880 is by no means an exhaustive list. 01:55.880 --> 01:57.710 But the bottom line is this. 01:57.890 --> 02:05.210 You should begin to upgrade your network because you face evolving needs and you recognize that Microsoft 02:05.210 --> 02:12.180 has addressed those needs in the new version of Windows Server in courses on installing and configuring 02:12.180 --> 02:13.460 Windows server. 02:13.470 --> 02:19.830 I discussed the process of planning how servers will be used so that the installation will fit the needs 02:19.830 --> 02:26.130 from the very beginning including the roles the right additions of Windows Server and when it comes 02:26.130 --> 02:32.690 to adding a new version of Windows Server or a new version of any product you add another dimension. 02:32.850 --> 02:38.880 You still need to consider all of this but you also need to take into account the minimum system requirements 02:39.600 --> 02:46.980 for example Windows Server 20 19 has hardware requirements that may seem very similar to Server 2016 02:47.880 --> 02:55.140 a minimum of a one point four gigahertz 64 bit processor that supports memory protection and second 02:55.140 --> 03:01.820 level address translation is still a requirement especially for virtualization roles. 03:01.920 --> 03:05.720 You will also need at least a couple of gigabytes of memory. 03:05.880 --> 03:11.430 Now you should be looking at that and saying Yeah right like that will work 2 gigabytes of memory is 03:11.490 --> 03:15.540 only enough to run Windows itself and barely that. 03:15.540 --> 03:20.460 Always consider the roles that you're going to install and the load that you're going to put on the 03:20.460 --> 03:24.310 server and make sure you have enough horsepower for those needs. 03:24.540 --> 03:31.710 And it might be more than what you're used to similarly when you read that the storage requirement is 03:31.770 --> 03:36.880 32 gig or more of hard drive space on a compatible controller. 03:36.990 --> 03:44.160 Understand that it will require a lot more 32 gig is enough to run Windows and possibly several months 03:44.160 --> 03:50.740 worth of updates but it's by no means a recommended threshold. 03:50.780 --> 03:56.690 You also need to make sure that your network controllers support the PCI Express architecture and that 03:56.690 --> 04:04.340 they support at least one gigabit per second of throughput and even after you look at all of these requirements 04:04.970 --> 04:13.970 if you're upgrading a network you need to consider the roles like 80 DFS or CERT services or even more 04:13.970 --> 04:16.400 common Active Directory. 04:16.400 --> 04:23.690 These roles involve multiple servers working together and upgrading them requires some planning. 04:23.690 --> 04:30.320 Whether you're going to take the ADF s farm or the functional level of the role for the entire network 04:30.740 --> 04:38.210 and try to bring that up to the enhanced versions in Windows Server 2019 planning the upgrade or the 04:38.210 --> 04:45.050 introduction of a new Windows Server 2019 system into your network will require you to take a look at 04:45.050 --> 04:52.040 your entire infrastructure not just that one server as you decide to upgrade specific services. 04:52.190 --> 04:58.460 These types of roles require their own unique methods for upgrading and the service or migration of 04:58.460 --> 05:03.130 the responsibilities has to be echoed across multiple machines. 05:03.150 --> 05:07.050 Bottom line there's a lot to consider as we go through this course. 05:07.080 --> 05:13.080 We're going to take a look at new as well as traditional roles performed by Windows Server and what's 05:13.080 --> 05:16.710 involved in bringing Windows Server 2019 into your mix.