Downloading a service template for the HA gateway - Windows Server Tutorial

- [Instructor] Microsoft defines the Gateway setup we're creating as a virtual machine based software router and gateway that allows Cloud Service Providers and Enterprises to enable datacenter and cloud network traffic routing between virtual and physical networks, including the internet. Now that we have a definition of what we're about to create, we need to download a service template. And we're going to do that by going to the link that you see on the screen. Now you don't have to remember the entire link information. All you have to do is go technet.com and type in the DN number which is 249417. So let's go do that and we'll download our script. We are in our virtual machine manager server. We have a web browser open to technet.com. It automatically appends to technet.microsoft.com. Let's put in the number we saw earlier. Hit enter. And there's our link. And now we're at the page where it tells us how to add the Windows Server Gateway. Let's go ahead and click on the link here, and that will download the script we want. We'll go ahead and click save, and we'll save it to the default location, and then we'll open it up and we'll be able to import our script into the library. When we go into our downloads folder, we see the zip file. Let's go ahead and right click on it and choose extract all. And we'll just choose the default location, and there are a bunch of scripts here. We see the .xml files, the user guide, and if we double click on the .cr folder, then we see additional scripts. We see the .ps1 scripts that we can use to import. Having the script doesn't replace the work we need to do to create some of the setup, but it does speed things up, because it does automate it partially. In upcoming videos we're going to take a look at what it will take before we run the script after we import it into Virtual Machine Manager. Let's go back to the parent directory, and we can see a Gateway 2NIC and a Gateway 3NIC option. We're going to use the 3NIC option in this case. And what that's going to do for us is it's going to allow us to create three networks, but they're going to be virtual networks, not physical networks. However, they'll work just like physical networks. One network will be for the virtual machines themselves, another will be for the internal network, and the last one will be for the external network. You could use the 2NIC setup, which combines the internal network as well as the virtual machine network. It does not give you as good of security because it puts the virtual machines on the same network as the internal network itself, which means that anybody who gets a virus, or if the network gets hacked internally, then it could lead to our virtual machines. By going with the 3NIC setup, then we don't have the fear of that happening. Even though it says 3NIC, it actually is referring to three subnets. A highly available gateway used in software defined networking is the main component of what makes software defined networking work by protecting the virtual machines in Hyper-V.