When you use Remote Desktop Connection to create a Terminal Services session to a Windows Server 2003-based terminal server, the first drive letter of the client is not redirected to the Terminal Services session

Consider the following scenario:

• You use Remote Desktop Connection to create a Terminal Services session to a Windows Server 2003-based terminal server.
• The smart card redirection functionality is enabled, and the local drive redirection functionality is disabled.
• You disconnect the Terminal Services session.
• You use Remote Desktop Connection to reconnect this session. However, this time, the smart card redirection functionality is disabled, and the local drive redirection functionality is enabled.

In this scenario, the first drive letter of the client is not redirected to the Terminal Services session. For example, drives C, D, E, and F exist on the Terminal Services client. However, only drives D, E, and F are redirected. This issue also affects Windows CE users because the local disk drive is not redirected to Terminal Services sessions in this scenario.

The issue is caused by Terminal Services. The smart card device is not correctly reset when a Terminal Services session is disconnected. An issue that involves the first drive device ID occurs if the Terminal Services session is reconnected when the smart card redirection functionality is disabled. Therefore, the first drive letter is not redirected. On the other hand, Windows CE devices have only one drive device. Therefore, you cannot access any files on a Windows CE device when this issue occurs.

To work around the issue, enable the smart card redirection functionality in Remote Desktop Connection.

Hotfix information

Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 1, x86 versionWindows Server 2003 with Service Pack 2, x86 versionWindows Server 2003, x64 versionWindows Server 2003 with SP2, x64 versionWindows Server 2003 with Service Pack 1, IA-64 versionWindows Server 2003 with Service Pack 2, IA-64 version

Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix requires Windows XP Service Pack 2 or Windows XP Service Pack 3 to be installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with SP2, x86-based versionsWindows XP with SP3, x86-based versionsWindows XP Professional x64 Edition with SP1 Windows XP Professional x64 Edition with SP2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.