info API Implemented Test system info Passed NAT management API Implemented Metering API Implemented Routing Domain Configuration API Implemented Customer Subnet Configuration API Implemented Chapter 5 34. Click on Next. 35. Select All Hosts. Click on Next. 36. Review the summary and click on Finish. 37. Using the PowerShell script from Chapter 3, Creating the Gateway for Virtual Machine Communications, change the name of the VM to HNVGateway2.ad.demo.com #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 = Get-SCVirtualMachine -Name HNVGateway2 ad.demo.com #Iterate through each entry in the Hashtable ForEach ($Key in $NicNames.Keys) { #Find the Network Adapter's MAC Address in VMM that is connected to #the VM Network. As the Tenant Network Adapter is not attached to a #VM Network it must be dealt with carefully $VNAMacAddress = ($GatewayVM.VirtualNetworkAdapters Where-Object{ #Check for an actual value if ($_. VMNetwork.Name) { if($ VMNetwork.Name -eq $key) { $True #check for the Tenant NIC elseif( ($_. VMNetwork. Name) -and ! ($key) ) { $True } ) MACAddress Invoke-Command -ComputerName $GatewayVM. ComputerName - ScriptBlock { Windows Server Gateway Configuration Param ($LocalMacAddress, $NewNicName) #Change the format of the MAC Address $LocalMacAddress = $LocalMacAddress -replace ":"," - #Find the NIC based on the MAC address obtained from VMM $NIC = Get-NetAdapter I Where-Object $_.MacAddress -eq $LocalMacAddress} #Get the WMI object based on the NIC's current name $wmi = Get-WmiObject -Class Win32 NetworkAdapter - Filter "NetConnectionID = '"$ ($NIC.Name) IIIIII #Change the NIC's name to the correct name $wmi.NetConnectionID = $NewNicName $wmi Put () } -ArgumentList $VNAMacAddress $NicNames.Item($Key) 38. In the VMM console, click on the Home tab in the ribbon bar and click on the PowerShell button. This will launch PowerShell with the