WEBVTT 00:05.610 --> 00:09.230 This course has been about Windows Server 2019. 00:09.390 --> 00:16.500 The latest release in the long term service channel of Windows Server these long term service releases 00:16.500 --> 00:23.550 have the advantage of being supported by Microsoft for several years rather than the 18 month lifecycle 00:23.580 --> 00:26.100 of the semi-annual releases. 00:26.100 --> 00:33.540 But these long term releases benefit greatly from the semi-annual release channel improvements to the 00:33.570 --> 00:41.460 subsystem for Linux storage spaces direct containers and many other server components have been developed 00:41.490 --> 00:49.270 and deployed in these semi-annual releases the community of administrators developers and dev ops then 00:49.270 --> 00:55.430 have the opportunity to weigh in on whether or not the features are meeting their needs and expectations. 00:55.660 --> 01:02.500 Before these various features from all the semi-annual releases get rolled up and added into the next 01:02.500 --> 01:11.220 long term release like Windows Server 2019 the differences between the long term service release and 01:11.220 --> 01:15.600 the semi-annual channel give different opportunities. 01:15.600 --> 01:21.600 You may choose to keep all of your production servers on these long term service channel releases because 01:21.600 --> 01:27.960 of their stability and long term support or you may choose to introduce as many semi-annual release 01:27.960 --> 01:35.530 servers as you can to receive access to new features as quickly as possible if you have a large environment 01:35.530 --> 01:38.980 with lots of servers each performing specific tasks. 01:39.160 --> 01:46.680 You may likely find a way to use both domain controllers likely need the stability of a long term service 01:46.680 --> 01:51.380 release as do other database roles like a certificate authority. 01:51.660 --> 01:57.780 Even with the introduction of the storage Migration Service file servers are less likely to benefit 01:57.780 --> 02:04.170 from lots of new features and so they are also more likely candidates for the long term service release 02:04.170 --> 02:11.250 channel other involved roles that we've talked about in this course also would do well to be on a server 02:11.250 --> 02:18.640 that they can stay installed and configured on for a longer period of time but on the other hand developers 02:18.640 --> 02:21.410 are always looking to what happens next. 02:21.430 --> 02:27.370 They benefit immensely from being able to develop their applications in an environment that has access 02:27.370 --> 02:29.690 to the newest features possible. 02:29.920 --> 02:36.070 Any development projects whether it's a container application or something being deployed in a virtual 02:36.070 --> 02:41.540 server is going to benefit from having access to those features as soon as possible. 02:42.160 --> 02:45.970 The semi-annual releases of server are great for them. 02:45.970 --> 02:51.670 The frequent upgrades would be more of a help than a hindrance to them and their servers are not likely 02:51.670 --> 02:56.460 to be running the server roles that don't survive in-place upgrades. 02:56.650 --> 03:03.280 Make sure as you plan semi-annual release servers in your network that they're regularly backed up not 03:03.280 --> 03:07.470 just the files on the servers but the configurations as well. 03:07.480 --> 03:14.590 Also consider using the various cloud repositories for developer projects container images can be stored 03:14.590 --> 03:23.130 in private repositories at get hub or onsite and for many of the roles that you count on from Windows 03:23.130 --> 03:30.750 servers it may be a good idea to use the semi-annual releases for testing and for future planning allowing 03:30.750 --> 03:36.360 you to try out what's coming next in the role before you deploy it into production. 03:36.390 --> 03:42.510 You can keep the production installation of these mission critical tasks on your long term service release 03:42.600 --> 03:50.280 machines but go ahead and test them test your operations test your development projects test your dev 03:50.280 --> 03:56.130 ops procedures in these semi-annual release servers that deliver all the latest features as quickly 03:56.130 --> 03:56.820 as possible.