specified has local administrator privileges on the VM. Click on Next. 42. Select the All Hosts host group as shown in the following screenshot. Click on Next. Specify the host groups for which the network service will be available Selecting a top-level host group automatically selects its child groups. Host groups: All Hosts Hosts Gateway 43. Review the summary and click on Finish. 44. After the gateway has been added, right-click on the newly created HNVGateway1 entry and click on Properties. Click on the new Connectivity option on the left: Specify the configuration of each network connection and bandwidth that is available for tenants Connectivity Gateways have a front end that is connected to a traditional physical network and a back end that contains the network using network virtualization. Enable front end connection Front end network adapter: Ethernet 2 Front end network site: Host-Cluster_0 (Host-Cluster) Enable back end connection Back end network adapter: Ethernet 2 Back end network site: Host-Cluster_0 (Host-Cluster) Available bandwidth Select the amount of bandwidth that is available for tenants to use on this connection. This value can exceed the physical capabilities of the gateway if you expect the virtual networks to use less than they have requested. Limit bandwidth Available bandwidth (MBps): 10000 Chapter 3 45. It is important to know which network adapter is connected to which network interface. In the wizard, there are the following three Ethernet adapters listed at the moment: Ethernet2 Ethernet3 Ethernet4 None of these are particularly useful. The following PowerShell script will obtain all the information about the gateway VM from VMM, determine the VM Networks each NIC is attached to and rename the NIC in the VM with the appropriate name. The code is as follows: #Hashtable of VM Networks and the names the NICs should be inside the Gateway VM $NicNames =@{ "Host-Management" "Management"; "External (NAT)" ="External"; "TenantNetworks" #Get the VM from VMM, not from Hyper-V $GatewayVM = Ge