Hotspot Question
You have a machine named VM1 that runs Windows Server 2016 VM1 is a Remote Desktop
Services (RDS) server. You need to ensure that only TCP port 3389 can be used to connect to
VM1 over the network. Which command should you run on the Hyper-V host? (To answer, select
the appropriate options in the answer area.)
Which command should you run on the Hyper-V host?
Hotspot Question
You have a machine named VM1 that runs Windows Server 2016 VM1 is a Remote Desktop
Services (RDS) server. You need to ensure that only TCP port 3389 can be used to connect to
VM1 over the network. Which command should you run on the Hyper-V host? (To answer, select
the appropriate options in the answer area.)
Correct: https://docs.microsoft.com/en-us/powershell/module/hyper-v/add-vmnetworkadapterextendedacl?view=win10-ps
why not Add-VMNetworkAdapterAcl?
Add-VMNetworkAdapterACL not provide protocol filter
Still can’t understand why not Add-VMNetworkAdapterAcl.
Can you please explain it to me?
To my understanding Add-VMNetworkAdapterExtendedAcl cmdlet creates an extended access control list (ACL) for a virtual network adapter while Add-VMNetworkAdapterAcl just creates ACL because when a virtual network adapter is created there is no ACL on it. So, why not just Add-VMNetworkAdapterAcl?
That’s because you have to specify the inbound port 3389 (Add-VMNetworkAdapterExtendedAcl … Inbound -LocalPort “3389” …) and Add-VMNetworkAdapterAcl allows only IP-based ACLs.