e PowerShell cmdlets that VMM is about to execute. Click on Finish. 8. Repeat steps 2-7, substituting Tenant B for Tenant A. All other options should remain the same, including the subnet details. After you have created the two required VM Networks, you must create an IP Pool for each VM Network. To begin, right-click on the VM Network Tenant A and click on Create IP Pool. 10. Enter a name and description for the IP; in this case, it is Subnet 1 - IP Poolpool. Click on Next. Configuring Networks for Hyper-V Network Virtualization 11. On the IP address range page, you will see that the range starts automatically at 10.0.0.2. The first IP address of the subnet is reserved for use by the Hyper-V Network Virtualization gateway and is the default gateway for the subnet. Click on Next. Create Static IP Address Pool Wizard IP address range IP address range IP address range Specify the range of IP addresses from the subnet to be managed by this pool. Gateway IP subnet: 10.0.0.0/24 Starting IP address: 10.0.0.2 Ending IP address: 10.0.0.254 Total addresses: Summary 12. Leave the Gateway information blank. Click on Next. 13. You can enter the IP address for a DNS server that the VMs on this subnet should use. However, as there are no VMs in the subnet and currently no external communication available leave this blank. Click on Next. 14. Leave the WINS server blank. Click on Next. 15. Review the summary. You can click on the View Script to see the PowerShell cmdlets that VMM is about to execute. Click on Finish. 16. Repeat steps 9-15 for the Tenant B VM Network. How it works The VM Networks are where the Tenant networks are declared, along with its subnets if required. Each VM Network is isolated from one another through the NVGRE protocol, which allows each VM Network to have the same subnets while being isolated. Chapter 2 Testing the basic Virtual Machine Networks Now that all of the building blocks are in place, it is time to deploy two VMs-one into Tenant A's VM Network and one into Tenant B's VM Network. Once this is 