WEBVTT 00:05.600 --> 00:07.490 I usually complete a worksheet. 00:07.490 --> 00:08.650 Kind of like this one. 00:08.650 --> 00:13.790 Prior to any server installation notice the first column. 00:13.790 --> 00:19.850 This isn't the first question that you're asked during a server installation in fact adding roles and 00:19.850 --> 00:24.140 features are the last part of a new server deployment. 00:24.140 --> 00:31.130 But that said roles and features and identifying what your server is going to do and what your server 00:31.130 --> 00:35.710 is going to be should be the first part of your plan. 00:35.780 --> 00:40.270 Each role and each application will have its own set of requirements. 00:40.580 --> 00:49.790 Some like DNS and DHS S.P. have a very small footprint and may be able to coexist on a server possibly 00:49.790 --> 00:52.130 even with other roles. 00:52.130 --> 00:54.540 Others have varying demands. 00:54.560 --> 01:01.400 File sharing is likely to require high volumes of storage and fast network interfaces while acting as 01:01.400 --> 01:09.240 a domain controller may require enhanced local security and controlled access planning which roles you're 01:09.240 --> 01:16.470 going to add to a server should be done with these considerations of the security needs of the hardware 01:16.470 --> 01:24.590 needs of the processing and memory as well as storage needs from the individual servers. 01:24.630 --> 01:28.790 Actually installing the role once you've made these decisions is quite easy. 01:30.930 --> 01:37.050 Adding a role or feature can be done from the server manager or from power show here in the desktop 01:37.050 --> 01:37.740 experience. 01:37.740 --> 01:44.340 You can add any role or feature from right here in the server manager from either selecting step two. 01:44.520 --> 01:51.480 Notice again Step 1 was configure the server and that is the server name the network configuration and 01:51.480 --> 02:00.710 so on step to add roles or features or if you've wandered off from this screen the manage menu has ADD 02:00.710 --> 02:04.810 roles and features right here at the top of the list. 02:05.110 --> 02:10.450 This wizard starts with a welcome screen which most people read once and then check the box to never 02:10.450 --> 02:16.690 have to see it again and then moves on to the question of whether you're installing a role or a feature 02:17.230 --> 02:23.350 a purpose for this server to conduct or if you're installing an application that needs to be available 02:23.350 --> 02:25.930 to remote desktop clients. 02:25.990 --> 02:31.960 If you're installing Microsoft Office for a desktop as a service environment this is what you would 02:31.960 --> 02:38.530 select remote desktop for but we want to add a role or a feature to this server so we'll remain with 02:38.530 --> 02:42.170 the top choice moving on to the next screen. 02:42.280 --> 02:47.950 We get to select which server we would like to install a role or feature on. 02:48.130 --> 02:53.440 Now in this single server environment that we've just begun to construct that seems like a very easy 02:53.440 --> 02:54.350 choice. 02:54.580 --> 03:01.120 But when you start managing multiple servers you can add your entire datacenter worth of servers into 03:01.120 --> 03:09.210 this list and you can add roles or features to any server you like from this same wizard in this window 03:09.210 --> 03:12.390 you can add any other windows 2012 server. 03:12.390 --> 03:20.760 Now that includes 2012 and 2012 R2 as well as any other 2016 or 2019 servers that you want to manage 03:21.830 --> 03:28.340 and then you can move forward and select the roles and the features roles are on a separate tab from 03:28.340 --> 03:35.240 features you can select which components you'd like to add to the server for the most part when you 03:35.240 --> 03:41.480 select a role you're going to be prompted for some prerequisites or some management tools. 03:41.480 --> 03:48.740 In this case for hyper v it wants to add the power shell module which is the collection of command lists 03:48.740 --> 03:53.240 and functions that you'll need to use in power shell to manage this role. 03:53.960 --> 03:59.620 And it gives you the desktop the gooey management tools and we could move forward from there. 03:59.690 --> 04:02.350 But let me back up and show you a couple of others. 04:02.480 --> 04:10.160 If I was to select the web server it only adds the management console the tools that I need to administer 04:10.160 --> 04:11.440 that particular role. 04:12.200 --> 04:18.110 If I were to pick something a little more involved say Active Directory Domain Services it's going to 04:18.110 --> 04:27.490 add a bigger list of tools other prerequisites might also be added to this list configuring any one 04:27.490 --> 04:34.630 of these roles requires at least the same kind of planning that's used in preparing for the installation 04:34.630 --> 04:36.500 of the server itself. 04:36.670 --> 04:39.370 What's it going to do what resources does it need. 04:39.370 --> 04:45.840 What are the clients going to need for this to function failure to do this kind of planning on a production 04:45.840 --> 04:51.340 server would put an administrator in a category my grandfather used to warn me about. 04:51.390 --> 04:56.910 He said that many people who don't take the time to do something right will often be forced to take 04:56.910 --> 04:58.930 the time to do it over. 04:58.980 --> 05:05.100 That's sage advice whether you're building a shed or deploying a certificate authority new versions 05:05.100 --> 05:11.730 of Windows Server mean new features and upgraded versions of the roles you already know. 05:11.730 --> 05:17.040 Sometimes you may assume the installation is pretty much the same as you've seen in previous versions 05:17.550 --> 05:23.640 and so you go ahead and install the roll and then you have to pause to go figure out the roll configuration 05:23.640 --> 05:29.010 maybe catch up on some prerequisites before you can finish and configure the role. 05:29.070 --> 05:31.140 There is a better sequence of events here. 05:32.160 --> 05:38.610 Understanding what the role will require allows you to complete the prerequisites first then install 05:38.610 --> 05:43.120 the role and then conduct whatever configuration is necessary. 05:43.120 --> 05:49.050 There is a prime example of this Active Directory Domain Services has gone through a few changes since 05:49.050 --> 05:52.000 Windows Server 2016. 05:52.030 --> 05:59.380 Now you could install the role and then pause the process to go back and update Active Directory so 05:59.380 --> 06:05.510 that you can promote that machine to domain controller and you could get away with doing it like that. 06:05.740 --> 06:10.090 But there are other roles like ADFA s that upgrade differently. 06:10.090 --> 06:12.450 ADF s is an identity role. 06:12.490 --> 06:17.350 It allows you to create single sign on relationships with outside entities. 06:17.350 --> 06:23.170 It allows you to secure web based applications inside your own environments and more. 06:23.330 --> 06:29.140 And this is another role that has changed from Windows Server 2016 to 2019. 06:29.440 --> 06:34.550 But its upgrade or migration path is different with ADF s. 06:34.720 --> 06:38.860 You install the roll on a new server join the cluster. 06:38.860 --> 06:46.360 In this case the cluster is known as a farm and by joining that farm that 2019 server will automatically 06:46.360 --> 06:53.110 take over and be the primary server in the cluster allowing you to decommission the old one and once 06:53.110 --> 06:58.060 there are no old servers in the mix you can upgrade the functional level. 06:58.060 --> 07:04.650 Take the time to figure out which roles require extensive migration processes. 07:04.690 --> 07:09.140 Consider which roles can coexist on a server with others. 07:09.220 --> 07:15.020 Study out each role learn its requirements learn the processes before you get started. 07:15.130 --> 07:23.580 The concept of measure twice and cut once has applications far beyond just carpentry.