he VLAN field to VLAN disabled: Network Adapter 3 [None] Tenant Network Tenant VLAN di 29. Leave the Add Properties page as default and click on Next. 30. Review the summary and click on Create. 31. Once the VM has been deployed, navigate to VMs and Services I All Hosts click the host that has the HNVGateway1 VM deployed. 32. Right-click on the HNVGateway1 VM, navigate to Connect or View, and click on Connect via Console. 33. Log in to the VM if necessary. Open an elevated PowerShell console and enter the following command to install the required Remote Access roles: Install-WindowsFeature -Name DirectAccess-VPN, Routing, RSAT- RemoteAccess-PowerShell 34. In the VMM console, navigate to Fabric I Networking I Network Service. Right-click on Network Service and click on Add Network Service. 35. Enter an appropriate name, in this case HNVGateway1, and a description. Click on Next. 36. Ensure the dropdown Manufacturer is set to Microsoft and Model is set to Microsoft Windows Server Gateway. Click on Next. Specify manufacturer and model of network service Manufacturer: Microsoft Model: Microsoft Windows Server Gateway Configuration provider: Microsoft Windows Server Gateway Provider If you are adding a gateway, after you complete this wizard, right-click the listing for the gateway, click Properties, and fill in the connectivity properties for the gateway. 37. Select a Run As account that has sufficient privileges on the HNVGateway1 VM; in this case, the standard VMM Agent Run As account. Click on Next. Creating the Gateway for Virtual Machine Communications 38. In the connection string, enter the information in the requested format: VMHost= < FQDN OF THE HYPER-V HOST> ; GatewayVM=<FQDN OF VM BE THE GATEWAY> In this case, the connection string would be the following: VMHost=HNVG2 . ad. demo com GatewayVM=hnvgatewayl. 39. Click on Next. 40. Ignore the certificate information as it is not required. Click on Next. 41. Click on Test to ensure that VMM can utilize the VM. If the VM fails, check the Run As account that was 