 a PowerShell console. Note that this does not need to be an elevated PowerShell console. 13. Once you have opened PowerShell, type in Enter-PSSession HYPVCH1 and press Enter (where HYPVCH1 is the name of the Hyper-V host where PVLAN190-1 is running). 14. As in the previous recipe you will see the PowerShell session change. Windows PowerShell Windows PowerShell Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\adminuser> Enter-PSSession HYPUCH1 [HYPUCH1]: PS C:\Users\AdminUser\Documents> Implementing Network Isolation in Hyper-V 15. Using this PowerShell console enter the following cmdlet (if this was closed please repeat steps 21-23): Set-VMNetworkAdapterVlan -VMName PVLAN190-4 Community - PrimaryVlanId 190 -SecondaryVlanId 5 16. Then, run the following PowerShell cmdlet: Get-VMNetworkAdapterVlan VMName PVLAN190-4 17. You will see that the mode has changed from Isolated to Community. 18. This means that PVLAN190-4 can communicate with PVLAN190-1 and PVLAN190-4. 19. In the VMM Console, right-click on PVLAN190-4, navigate to Connect or View, and click on Connect via Console. 20. Log on to the VM using the default password. 21. Open an elevated PowerShell console. 22. Enter the following PowerShell cmdlets one at a time and press Enter: Test-NetConnection 192.168.190.2 Test-NetConnection 192.168.190.3 Test-NetConnection 192.168.190.6 23. You should have the following results: PS C:\Users\Administrator> Test-NetConnection 192.168.190.2 ComputerName : 192.168.190.2 RemoteAddress : 192.168.190.2 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.190.5 PingSucceeded : True PingReplyDetails (RTT) : PS C:\Users\Administrator> Test-NetConnection 192.168.190.3 WARNING: Ping to 192.168.190.3 failed -- Status: DestinationHostUnreachable ComputerName : 192.168.190.3 RemoteAddress : 192.168.190.3 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.190.5 PingSucceeded : False PingReplyDetails (RTT) PS C:\Users\Administrator> Test-NetConnection 192.168.190.6 ComputerName : 192.168.190.6 RemoteAddress : 