When adding base rules such as a Deny All, it is suggested to apply a weight of 1 to allow other rules to override it if appropriate. 13. Return to the PowerShell console left open on Tenant A - VM 11 in step 10. You will see that Tenant A - VM 10 has stopped responding to pings. PS C:\Users\Administrator> ping 10.0.0.14 -t Pinging 10.0.0.14 with 32 bytes of data: Reply from 10.0.0.14: bytes=32 time=2ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Reply from 10.0.0.14: bytes=32 time-1ms TTL=128 Reply from 10.0.0.14: bytes=32 time=1ms TTL=128 Reply from 10.0.0.14: bytes=32 time=1ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Reply from 10.0.0.14: bytes=32 time<1ms TTL=128 Request timed out. Request timed out. Request timed out. Request timed out. Chapter 7 This has created a Hyper-V Port ACL that will deny all inbound traffic to Tenant A - VM10. 14. In the same PowerShell console, enter the following PowerShell: Test-NetConnection -CommonTCPPort HTTP ComputerName 10.0.0.14 InformationLevel Detailed 15. Here, 10.0.0.14 is the IP address of Tenant A - VM 10. This shows that you cannot access the IIS website on Tenant A - VM 10. PS C:\Users\Administrator> Test-NetConnection -CommonTCPPort HTTP -ComputerName 10.0.0.14 -InformationLevel Detailed WARNING: Ping to 10.0.0.14 failed Status: TimedOut WARNING: TCP connect to 10.0.0.14:80 failed ComputerName : 10.0.0.14 RemoteAddress : 10.0.0.14 RemotePort 1NameResolutionResults MatchingIPsecRules NetworkIsolationContext Private Network InterfaceAlias Ethernet 2 SourceAddress 10.0.0.15 NetRoute (NextHop) 0.0.0.0 PingSucceeded False PingReplyDetai 1s (RTT) TcpTestSucceeded False 16. Return to the PowerShell console left open on the VMM console in step 11 and enter the following PowerShell cmdlets: Invoke-Command -ComputerName hYpVCH1.ad.demo.com - ScriptBlock { Add-VMNetworkAdapterExtendedAcl -Action Allow - Dire