WEBVTT 00:05.600 --> 00:11.510 Once the deployment of a new server has been planned the installation itself is a pretty elementary 00:11.510 --> 00:12.790 task. 00:12.830 --> 00:20.760 Unlike servers from long ago the installation of Windows servers today only ask a small handful of questions. 00:20.990 --> 00:25.490 And if the answers are known in advance installation is pretty smooth. 00:25.820 --> 00:31.550 If you're prepared with the language preference the product key and whether or not you need the desktop 00:31.550 --> 00:38.360 experience the only configuration question that you'll be asked is the size and the placement of the 00:38.360 --> 00:43.200 install partition and that size can even be modified after the fact. 00:43.220 --> 00:50.750 If you need to the barebones requirement here is that you should have at least 32 gigabytes for the 00:50.750 --> 00:52.670 install partition. 00:52.670 --> 00:58.050 As we mentioned before that minimum doesn't even account for the desktop experience. 00:58.100 --> 01:04.160 That's only for core which is now considered the default install for Windows servers. 01:04.160 --> 01:09.970 Best practice is to consider starting at double or more the stated minimum requirement. 01:09.980 --> 01:15.530 Keep in mind that you're going to be installing various roles and that you want this server to run for 01:15.530 --> 01:21.740 several years so there's going to need to be room for whatever security and feature updates may be released 01:21.800 --> 01:30.400 over that time here's a fresh install that I completed on a server in my test lab on a virtual machine 01:30.400 --> 01:34.030 with 8 gig of ram dynamically expanding. 01:34.090 --> 01:40.390 You can see that right now it's using three quarters of that and this server is literally doing nothing. 01:40.450 --> 01:48.170 That 2 gig of ram really is a bare bones minimum I installed this like I said and a virtual machine. 01:48.170 --> 01:55.340 I granted it eight virtual processors and this 8 gig of ram and it took all of 15 minutes to complete 01:55.430 --> 01:57.830 including the reboot at the end. 01:57.860 --> 02:01.880 In fact it felt like the reboot was the longest part of the process. 02:03.250 --> 02:09.760 Completing that install is only the first step to getting a new server ready before you add any rolls 02:09.790 --> 02:16.050 share any folders or install any applications you need to assign the server an identity. 02:16.210 --> 02:22.840 And this includes two things the network address and the computer or hostname. 02:23.200 --> 02:29.500 Just like in previous versions of Windows server the server manager loads by default and just as in 02:29.500 --> 02:36.790 previous versions of Windows server you can select this line next to ether net and get the legacy interface 02:36.820 --> 02:43.510 for changing the IP address and network configuration of any interface in the machine. 02:43.540 --> 02:51.060 I'm going to go ahead and assign this an address using tools that have been around for several versions 02:51.060 --> 02:53.280 of Windows and Windows Server. 02:53.340 --> 02:55.860 I'm going to assign it a static IP address 03:05.880 --> 03:11.880 including the default gateway and DNS information provided to me by my network administration team 03:22.220 --> 03:29.600 assigning new IP configuration even adding or removing IP version four or six or switching from dynamic 03:29.600 --> 03:30.670 to static. 03:30.710 --> 03:33.610 None of these changes require a reboot. 03:33.650 --> 03:39.770 I like to get as many things done as possible before a reboot so that all of those settings can be applied 03:39.800 --> 03:41.370 as the system comes up again. 03:42.140 --> 03:45.140 So let me go ahead and save those changes. 03:45.140 --> 03:47.230 And this is on my company network. 03:47.240 --> 03:54.910 And yes I do want my server to be visible to other machines so I'm gonna go ahead and say yes and I 03:54.910 --> 04:01.200 can close out of this panel and now the next step of giving the computer a name. 04:01.200 --> 04:05.930 This can also be done from the server manager but I want to show you a different path. 04:05.970 --> 04:11.810 I'm going to open power shell and if you haven't started using power shell yet it's time. 04:12.090 --> 04:17.790 Especially if you're considering semi-annual releases of Windows Server or if you go with the default 04:17.820 --> 04:23.970 installation of Windows Server formerly known as core where you don't have this desktop experience with 04:23.970 --> 04:27.380 a server manager from the start menu. 04:27.430 --> 04:29.020 Here is power shell. 04:29.020 --> 04:34.840 I'm going to right click it so that I can run it as administrator if I've logged into the machine as 04:34.840 --> 04:36.160 the administrator account. 04:36.160 --> 04:41.920 This extra step may not be necessary but it's a pattern that I've gotten used to and it allows me to 04:41.920 --> 04:49.730 always have the access I need regardless of how I logged in to start so here in power shell let me go 04:49.730 --> 04:55.400 ahead and maximize this window the process of renaming the server. 04:55.400 --> 04:57.820 I like to do it in two steps. 04:57.830 --> 05:01.850 The first is to type the command lit hostname. 05:01.900 --> 05:06.310 This gives me the automatically assigned computer name. 05:06.310 --> 05:11.350 That's not something that I want to have to remember or be responsible for typing accurately. 05:11.350 --> 05:19.460 So I'm going to select it and use control C on the keyboard to copy that information now to rename the 05:19.460 --> 05:20.710 computer. 05:20.960 --> 05:24.560 The power shall command lit for that is rename computer 05:28.540 --> 05:33.010 and that's the basic syntax in power shall we first start with a verb. 05:33.010 --> 05:34.560 In this case rename. 05:34.720 --> 05:37.120 And then we have a noun computer. 05:37.120 --> 05:38.460 Most power shall command. 05:38.470 --> 05:41.980 Let's have a verb noun construct. 05:41.980 --> 05:44.220 So we're going to rename a computer. 05:44.350 --> 05:50.980 First we need to tell it which computer we're going to rename the parameter computer name. 05:50.990 --> 05:55.690 And now I'm going to hit control V to paste the current computer name. 05:55.730 --> 06:05.310 That's the computer we want to rename and we want to assign it a new name on our network. 06:05.370 --> 06:08.760 Let's go ahead and name this server 1 06:11.380 --> 06:13.170 naming conventions are very important. 06:13.180 --> 06:19.240 And as you bring up new machines and configure them in your environment consider using server names 06:19.240 --> 06:23.740 that will be meaningful to your users in very large organizations. 06:23.740 --> 06:29.650 Those names might include something about the function and the location of the server in smaller to 06:29.650 --> 06:31.230 medium size organizations. 06:31.240 --> 06:38.530 They may be named after the task that they perform or some people even use characters from TV series 06:38.530 --> 06:42.910 or movies that represent a task being done by that server. 06:43.030 --> 06:49.290 But make sure those decisions are deliberate when I go ahead and hit enter. 06:49.310 --> 06:54.500 You'll notice that despite getting a warning that I'm going to have to restart that change was done 06:54.500 --> 06:56.150 really quickly. 06:56.150 --> 07:03.860 All we need to do now is reboot and that can be done using the shut down command using the R parameter 07:03.860 --> 07:07.550 for restart and that should take care of it. 07:07.760 --> 07:14.000 If this server is also going to be part of an existing active directory domain you should take care 07:14.000 --> 07:17.810 of joining it to the domain as soon as it reboots. 07:17.810 --> 07:24.170 Then and only then will you have a fresh install of Windows Server 20 19 that is ready to be put to 07:24.170 --> 07:24.490 work.