complete, another VM will be deployed for further testing. The following diagram shows how the VMs will be connected to the network: Virtual Port Profile (Tenant) Tenant B VM1 Tenant B VM2 Tenant A VM1 Tenant A 10.0.00/24 Tenant B 10.0.0.0/24 Provider Network 172.30.0.0/16 Uplink Port Profile (Standard) and Logical Switch Default VMM Management Server Hyper-V Cluster Configuring Networks for Hyper-V Network Virtualization Getting ready You will need to have a VM Template set up that is not connected to any VM Network in the template, this can then be assigned during deployment. Please visit http / microsoft.com/en-gb/library/hh427282 aspx for information on how to create a VM template. The operating system used for all VMs in this cookbook is Windows Server 2012 R2 Standard with a GUI and they only have a single Network Adapter. Please see Appendix, VM Templates, for detailed information on the VM template used. How to do it... The following diagram shows you the high-level steps involved in this recipe: Overview of Recipe: Actions: Creation of 2 VMs, one in each VM Network Prove that each VM is isolated Deploy another VM with a matching IP address but in a different VM Network This will result in three VMs deployed, two in one VM Network and one in the other. You will be able to prove that they are isolated from one another. Now, you have to perform the following steps: 1. Navigate to the Library workspace and expand Templates and VM Templates. Right-click on your VM template and click on Create Virtual Machine. 2. Enter a name for the VM. In this case, it is Tenant A - VM1. Click on Next. 3. On the hardware page, scroll down and click on Network Adapter. In the Connectivity option, change the selection to Connected to a VM network. Click on Browse, select Tenant A from the dialog, and then click on OK. 4. Set the VM subnet to Subnet 1. 5. Set the IP address section to Static IP (from a static IP pool). 6. Ensure the MAC address section is set to Static. Chapter 2 7. Under Port Profile, change the Classification