dy You will need to start two VMs in the Tenant A VM Network: in this case, Tenant A - VM 10 (which was used in Chapter 5, Windows Server Gateway Configuration, to test the gateway and as such should have IIS installed) and Tenant A - VM 11. How to do it... The following diagram shows the high-level steps involved in this recipe: Overview of Recipe: Prerequisites (not covered by this recipe): Complete Chapter 5 Start two VMs in the same Tenant VM Network Actions: Creation of Hyper-V Port ACLs Creation of Stateful Hyper-V Port ACLs Testing of Port ACLs Now perform the following steps: In the VMM console, click on the Home tab in the ribbon bar and click on the PowerShell button. This will launch PowerShell with the VMM module already loaded and the console connected to the current VMM instance. To obtain the Virtual Subnet IDs for all subnets in the Tenant A VM Network, enter the following PowerShell: $VMNetworkName = "Tenant A" $VMNetwork = Get-SCVMNetwork Where-Object Property Name -EQ $VMNetworkName Get-SCVMSubnet -VMNetwork $VMNetwork Select-Object VMNetwork, Name, SubnetVlans, VMSubnetID Chapter 7 2. You will be presented with the list of subnets and the VMSubnet for each. The VMSubnet ID will used later in this recipe; in this case, the VMSubnetID is 4490741, as shown in the following screenshot: VMNetwork SubnetVLans UMSubnet ID Tenant A Subnet 1 {10.0.0.0/24-0} 4490741 Your VMSubnetID value may be different to the one obtained here; this is normal behavior. 3. In the PowerShell Console, run the following PowerShell to get the IP addresses of Tenant A - VM 10 and Tenant A - VM 11: $VMs = @() $VMs += Get-SCVirtualMachine -Name "Tenant A - VM 10" $VMs += Get-SCVirtualMachine -Name "Tenant A - VM 11" ForEach ($VM in $VMs) { Write-Output "$($VM. Name) : $ ($VM.VirtualNetworkAdapters. IPv4Addresses) " Write-Output "Host name: $ ($VM.HostName) " 4. You will be presented with the IPv4 addresses for the two VMs as shown in the following screenshot: Tenant A - UM 10: 10.0.0.14 Host name: : HYPUCH1.ad.demo.com Tenant