pport a single VM Network, whereas Windows Server Gateways configured for NAT can support up to 50 VM Networks by default. In this recipe, you will create a simple web server and it will be available to computers outside of the HNV network using its HNV IP address; NAT will not be used. Windows Server Gateway Configuration Getting ready You should have completed the Creating HNV Gateways with Service Templates recipe in Chapter 3, Creating the Gateway for Virtual Machine Communications, as this recipe relies upon the service template that was created in that recipe. A new Windows Server Gateway will be provisioned for use by this recipe as it will be dedicated to the Tenant B VM Network. How to do it.. The following diagram shows you the high-level steps involved in this recipe: Overview of Recipe: Prerequisites (not covered by this recipe): Chapter 3 recipe "Creating HNV Gateways with Service Templates" must be complete Actions: Create a new Windows Server Gateway Add the new Windows Server Gateway to VMM as a Network Service Configure the Tenant B VM Network to use the new Gateway Install IIS on a test VM in the Tenant B VM Network Test the gateway Now, perform the following steps: 1. Open the VMM Console, navigate to the Library workspace, and click on Service Templates. You should have the HNV Gateway (non-HA) Service Template listed, as shown in the following screenshot: Library Templates (1) Templates Service Deployment Configurat Release Type Service Templates HNV Gateway (non-HA) 1.0 Service Template VM Templates Chapter 5 Right-click on the HNV Gateway (non-HA) Service Template and click on Configure Deployment. 3. Enter an appropriate name, HNVGateway2 in this case, and ensure the destination host group is set to Gateway. Click on OK. In the Deploy Service preview, click on the HNVGateway instance, change VM name to HNVGateway2 ad. demo com, and change Computer name to HNVGateway2 ad. demo com, as shown in the following screenshot: Gateway HNVGateway2 Template: HNV Gateway (non-HA) Release: 1.0 Windows 