Later on this year, Microsoft will be releasing an update for the Remote Desktop Client on Windows 7. Actually, the update will be upgrading the protocol to version 8.0 and adding new capabilities that integrate with Windows Server 2012 Virtual Desktop Infrastructure (VDI). Windows Server 2012 powers the back-end of Microsoft VDI.
In server core environments, the task of modifying and troubleshooting NICs protocol bindings may require the use of a tool called nvspbind which is available from MSDN here. However, the same tool can become very handy when you need to change the network binding order of network interfaces from the command line during the installation of Windows 7, and where the GUI tools are not yet available. Also, you can leverage the tool in environments where the default Windows shell (Windows Explorer) is replaced with other shells such as, command prompt, Windows PowerShell or custom built shells.
Windows 7 supports different password-based and certificate-based authentication protocols that can be used for both dial-up and VPN connections. Windows 7 first tries to use the most secure authentication protocol that is enabled and then falls back to less secure protocols if they are available.
The best to way to understand WFAS (Windows Firewall with Advanced Security) is by setting up a test rule as we are going to see in this article. We will configure a firewall rule that accepts only authenticated RDP (Remote Desktop Protocol) connections from hosts on a specific or same subnet:
Windows 7 native firewall is based on two sets of rules that complement each other. The basic Windows Firewall uses simple rules that directly relate to a program or service while the Windows Firewall with Advanced Security (WFAS) allows for more complicated rules that filter traffic on the basis of port, protocol, address and authentication.