Check out the new features and known issues in RDP 8.0.
To use this update, you must download the update, install a prerequisite and then install this update.
Note You may have to restart the computer multiple times when you install this update.
If you install RDP 8.0 on the client, you must manually enable it after the installation.
Note The following instructions are applicable only to remote computers that are running Windows 7 SP1.
- Install the appropriate version of the update package by running the Windows6.1-KB2592687 update file.
- Restart the computer.
- Open the Local Group Policy Editor.
- Enable the Remote Desktop Protocol policy. The setting for this policy is under the following node:Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
- If the UDP functionality is required, enable the RDP Transport policy, and then set the value to Use both TCP and UDP. The setting for
the RDP Transport policy is under the following node:Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\ConnectionsNote Configuring the RDP Transport policy also lets the firewall allow UDP port 3389.
- Restart the computer.
- If RDP 8.0 is enabled, the connection quality button will be displayed in the connection bar.
- Click the connection quality button to open an information dialog box that resembles the following. (Refer to the following screen shot for this step.)
- Virtual desktops that have RemoteFX vGPU installed cannot use RDP 8.0.
After you use Group Policy to install and enable RDP 8.0 on a computer that has RemoteFX vGPU installed, RDP 8.0 is not available.
This update does not enable RDP 8.0 for connections to computers that have RemoteFX vGPU installed. If you must have RDP 8.0 enabled, remove RemoteFX vGPU from the virtual desktop.
- The Shadow command cannot be used to remotely monitor another user's remote connection.
Windows 7 SP1 supports the Shadow command (Remote Control). This command can be used by an administrator to view or control an active session of another user. After RDP 8.0 is enabled on a computer that's running Windows 7 SP1, an administrator user cannot use the Shadow command to view or control another user's session.
Administrators can use Remote Assistance or another product that provides similar capability to view or control another user's session.
- Aero Glass support is unavailable.
The Aero Glass remoting feature in Windows 7 lets users who are running compatible Remote Desktop Connection clients use features such as a Flip-3D, the live task bar preview, and the translucent window border in a remote desktop session when a compatible RDC 7.0 client is used. After RDP 8.0 is enabled, users cannot use the Aero Glass remoting feature.
Administrators should not enable RDP 8.0 on remote computers that are running Windows 7 SP1 for users who must use the Aero Glass remoting feature.
- RDP 8.0 on remote computers that are running Windows 7 SP1 does not use the UDP protocol.
The RemoteFX for WAN feature in RDP 8.0 uses TCP and UDP protocols to optimize the user experience. After you install and enable RDP 8.0 on computers that are running Windows 7 SP1, RDP 8.0 is configured to use only the TCP protocol.
Configure RDP 8.0 to use both the TCP and UDP protocols. For more information, see the "How to enable RDP 8.0" section.
- Local administrators who are not members of the Remote Desktop Users group cannot sign in by using a Remote Desktop Connection client.
After RDP 8.0 is enabled, local administrators who are not a member of the Remote Desktop Users group cannot sign in.
Add local administrator users to the Remote Desktop Users group.
- The firewall rule that allows UDP traffic is not enabled when you use a Group Policy Object (GPO) to enable RDP 8.0.
If you use a GPO to enable RDP 8.0, the UDP firewall rule that allows UDP traffic may not be enabled.
Create a GPO to enable the "Remote Desktop - User Mode (UDP-In)" firewall.
- The firewall rule that allows TCP traffic may not be enabled if you apply this update manually.
If you use Local Security Policy to enable RDP 8.0, the TCP firewall rule that allows TCP traffic may not be enabled.
Enable the "Remote Desktop - RemoteFX (TCP-In)" firewall rule in the Windows Firewall with Advanced security.
- You experience slow performance when IPsec is deployed in the network.
If you connect to a computer by using the RDP 8.0 protocol when IPsec is deployed on the network, you may experience slow performance.
Install hotfix 2570170 on the server.
- You cannot use the multi-touch and gestures functionalities when you connect to a computer remotely.
This issue occurs when you use Remote Desktop Connection Client 8.0 on a computer that is running Windows 7 SP1.
The RemoteFX multi-touch feature is supported only when both the client and server computers are running Windows 8 or Windows Server 2012.
- You are repeatedly prompted for authentication when you connect to computers by using Remote Web Access in Small Business Server 2011 and Windows Server 2012 Essentials domains.
When you try to connect to a computer in a Windows Server 2012 Essentials, Windows Small Business Server 2011 Standard, or Windows Small Business Server 2011 Essentials domain by using Remote Web Access or Remote Desktop Gateway, you are repeatedly prompted for authentication.
To work around this issue, see Information about how to work around multiple authentication prompts after you apply updates 2574819 and 2592687.
Straipsnio ID: 2592687 – Paskutinė peržiūra: 2017-01-09 – Peržiūra: 2