TERMINAL SERVER DEVICE REDIRECTION 

Description: Terminal Services provides users the ability to access their local devices and resources in remote sessions. Users can access resources such as local drives, printers, the Clipboard, and supported Plug and Play devices. This is usually referred to as redirection.

In Windows Server 2008 redirection has been enhanced and expanded. Now you can redirect Windows Portable Devices, specifically media players based on the Media Transfer Protocol (MTP) and digital cameras based on the Picture Transfer Protocol (PTP).

In Windows Server 2008 you can also redirect devices that use Microsoft Point of Service (POS) for .NET 1.1. Microsoft POS for .NET device redirection is only supported if the terminal server is running an x86-based version of Windows Server 2008.

Users can specify which types of devices and resources they would like to redirect to the remote computer on the Local Resources tab of Remote Desktop Connection.

You can specify which local devices and resources will be available to users for remote sessions by using a connection on the terminal server. You can enable or disable the redirection of the following:

• Drives
• Printers
• LPT Port
• COM Port
• Clipboard
• Audio
• Supported Plug and Play devices

We will concentrate on redirection scenarios out of Printers scope since we focus on Printer Redirection in another topic.

Scoping the Issue:  Let’s first check if we are having problems in redirecting several resources, or just specific of above resource list. Make sure we enable more than one of above or if possible all of them so we could do a quick test and narrow down the issue.

Data Gathering:  In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done.  Additional data required may include the following:

• Collect the .RDP file used to connect to the Terminal Server
• Collect the output of GPRESULT in verbose mode so that we can see what policies are being applied

Troubleshooting / Resolution:  There are a number of things to check:

• Make sure you are using the latest RDP client
• Check if the device you are trying to redirect is actually working locally. Ex. Sound.
• Double clicking the .RDP  file and then clicking on “Options” expands the configuration for RDP client. Go to the Tab “Local resources” which will show you checkboxes for enabling redirection. There is a “More” button which will bring you more options.
• Check for errors in the system log on the Terminal Server for clues.
• Check for errors in the system log in the client
• Check if the issue presents on different client.
• If possible check if the issue presents on same client on different Terminal Server
• Smart Card redirection is dependent on the installation of required software support. Certain infrastructures require Cryptographic Service Provider (CSP). In order for Smart Cards in the environment to work via RDP Smart Card redirection, CSP must be installed on the server.
• If more than one device is failing to redirect we want to check if “Terminal Server Device Redirector” is enabled on the server. This is the core of the redirection process which works in the kernel, “rdpdr.sys”. Go to “Device Manager”, expand “System Devices” and look for “Terminal Server Device Redirector” status.

Check the following group policies using GPEDIT.MSC from the run command and verify settings for the device you are trying to redirect:

Additional Resources:

• RDS Team Blog: Device Redirection
• TechNet: Make Local Devices and Resources Available in a Remote Session
• Microsoft KB Article 952155: Description of the Remote Desktop Connection 6.1 client update for Terminal Services in Windows XP Service Pack 2
• Windows Help and How-to: Changing Remote Desktop Settings
• AskPerf Blog: Terminal Server and Printer Redirection