In certain rare scenarios, when connected to a system using Remote Desktop, the status of the NumLock key may go out of sync between the host and client systems. This typically can be seen on slower dial-up connections or if system resources are low on either system. Repeatedly pressing or holding down the NumLock key can cause this behavior.

Consider the following scenario:

• You have a computer that is running Windows Vista Enterprise 64-bit edition.
• You type mstsc /? at the 32-bit command prompt (%windir%\SysWOW64\Cmd.exe) to view the mstsc command syntax.

In this scenario, the Remote Desktop Connection Usage dialog box that contains the mstsc command syntax is not displayed.

Note: The Remote Desktop Connection Usage dialog box appears when you type mstsc /? at the 64-bit command prompt (%windir%\System32\Cmd.exe).

When you use Remote Desktop Connection to connect to a Windows Vista-based computer, you receive an error message that resembles the following:

The requested session access is denied.

When you use the Remote Desktop Client to connect to a Microsoft Windows 2000 Terminal Server from Window Vista or from Windows Server 2008, the automatic authentication fails, and you are prompted two times for the credentials.

This does not occur when you connect to a Windows Server 2003 Terminal Server.

Consider the following scenario:

• You use the Remote Desktop Connection feature to connect to a server from a Windows Vista-based client computer.
• Desktop Window Manager (DWM) is enabled on the server and on the client computer. Additionally, the Aero Glass theme is enabled on the server and on the client computer.
• On the client computer, you press CTRL+ALT+DEL, and then you lock the computer.
• You click Switch User, and then you log back on to the client computer.

In this scenario, Desktop Window Manager stops working on the server.

Note: This issue does not occur when you log back on to the client computer without clicking Switch User.

This article discusses the Remote Desktop Connection 6.0 client update that helps you use the new Terminal Services features. These features are introduced in Windows Vista and in the Microsoft Windows Server 2008 operating system from a computer that is running one of the following operating systems:

• Microsoft Windows Server 2003 with Service Pack 1 (SP1)
• Microsoft Windows Server 2003 with Service Pack 2 (SP2)
• Microsoft Windows XP with Service Pack 2 (SP2)

The Remote Desktop Connection 6.0 client can be used to connect to legacy terminal servers or to remote desktops as before. However, the new features that are mentioned in this article are available only when the remote computer is running Windows Vista or Windows Server 2008.

When you use Remote Desktop Connection to connect to a terminal server, Portable Network Graphic (PNG) images do not display in Windows Internet Explorer 7 during that Remote Desktop Protocol (RDP) session. A red X appears instead of the image.

This problem occurs when you configure the Remote Desktop Connection to use the “256 colors” display mode.

Note: This problem does not occur in Microsoft Internet Explorer 6.

In the Active Directory domain, you configure different profile paths for a roaming user profile and for a terminal services profile. When a user logs on to a Windows Vista-based client computer by using a Remote Desktop session, Windows Vista uses the profile path that is defined on the Terminal Services Profile tab to load the profile. However, Windows Vista should use the profile path that is defined on the Profile tab to load the profile.

The eighteenth video tip from PCWizKid. Control remotely over a network connection your Windows Vista or XP computer. Get access to your Vista applications or data stored on a remote computer from your XP PC. This tip applies to Windows Vista Ultimate, Business and XP Pro.

Consider the following scenario.

• You type a keyboard shortcut on a Windows Vista-based computer.
• You are working in a Terminal Services session that was started by using Remote Desktop Connection 6.0 (RDC 6.0).

In this scenario, some keys in the keyboard shortcut may remain active. Therefore, in the Terminal Services session of the Remote Desktop window, some later keystrokes are interpreted as part of the previous keyboard shortcut. For example, this problem occurs if the following conditions are true:

• You lock the local computer by pressing “Windows logo key” + L.
• You unlock the local computer.
• The Remote Desktop window is in the full-screen mode.
• The Remote Desktop window is active.

When you press any key, various Windows keyboard shortcuts occur in the Terminal Services session. For example, when you press E in the Terminal Services session, Windows Explorer starts.