is case, VLAN150 - 1. Ensure that the VM is connected to VM Network VMN-VLAN-Testing_0-150 and the VMN-VLAN-Testing_0-150_0 VM subnet is selected on the Configure Hardware page, as shown in the following screenshot: Network Adapter 1 Connectivity Not connected Connected to a VM network VM network: VMN-VLAN_Testing_0-150 Browse... VM subnet: VMN-VLAN_Testing_0-150_0 IP address Dynamic IP Static IP (from a static IP pool) IP protocol version: IPv4 only Chapter 6 26. Complete the deployment of the Virtual Machine. 27. Once the VM has been deployed, navigate to the VMs and Services workspace, and click on All Hosts. 28. Start one of your VMs that use Hyper-V Network Virtualization, in this case, Tenant A - VM 1, and live migrate it to the same host as VLAN150- 1VM. This will show you that two different isolation technologies can be used on the same Hyper-V host. Once the VM has completed its live migration, open a PowerShell console on the VMM server. Note that this does not need to be an elevated PowerShell console. 30. Once you have opened PowerShell, type in Enter-PSSession HYPVCH1 and press Enter (where HYPVCH1 is the name of the Hyper-V host where both VMs are running). You will see the PowerShell session change, as shown in the following screenshot: Windows PowerShell Windows PowerShe II Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\adminuser> Enter-PSSession HYPUCH1 [HYPVCH1]: PS C:\Users\AdminUser\Documents> 31. The prefix [HYVCH1] indicates that any further PowerShell you execute in this console will be executed on HYPVCH1 until you exit the remote PowerShell session. 32. Enter the following PowerShell and press Enter: Get-VM I Where State -eq "Running" 33. This will return a list of running VMs: in this case, the list should include Tenant A - VM 1 and VLAN150-1, as shown in the following screenshot: [HYPUCH1]: PS C:\Users\AdminUser\Documents) Get-UM : Where State -eq "Running" State CPUUsage(%) MemoryAssigned(M) Upt ime Status Tenant A - UM 1 Running a 02:03:38 Operating normal