resources outside of the VM Network they resided upon. This access was only one way: outbound; this recipe will show you how to create inbound NAT rules on the gateway to allow access to your VM's resources. A typical use case of this would be to host a website behind a public IP address. Windows Server Gateway Configuration In this recipe, you will create a simple web server and publish it using NAT rules on the Windows Server Gateway. Getting ready For this recipe, you will need access to a computer that is outside of the VM Networks created so far, but it can access the IP range you used for the external 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): Have access to a computer that can access the External (NAT) network Actions: Install IIS on a test VM in the Tenant A VM Network Create a custom HTML page Create a NAT rule to the test VM Test the NAT rule View the configuration change in the Windows Server Gateway Now, perform the following steps: 1. Start a Tenant A VM on your Hyper-V cluster; in this case, Tenant A - VM 10. 2. Once the VM has started, log on to the VM using an administrative account. Chapter 5 3. Open an elevated PowerShell window and enter the following PowerShell and press Enter: Install-WindowsFeature Web-Server,Web-WebServer,Web-Common- Http, eb-Default-Doc, ,Web-Dir-Browsing,Web-Http-Errors,Web- atic-Content, Web-Health,Web-Http-Logging,Web- Performance, eb-Stat-Compression, Web-Security, Web- Filtering, Web-Mgmt-Tools, Web-Mgmt-Console - This will then install IIS with the required features for this recipe, as shown in the following screenshot: Administrator: Windows PowerShell indows PowerShel Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\Administrator> Install-WindowsFeature eWeb-Server,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Dir-Brows ing,Web-Http-Errors,Web-Static-Content,Web-Health,Web-Http-Logging,Web-Performance,Web-Stat-Com