Terminal Server Plug and Play Device Redirection Framework in Vista and Longhorn: Part 2

Terminal Server Plug and Play Device Redirection Framework in Vista and Longhorn: Part 2

  • Comments 1

In the last part of this series, we introduced the new Plug and Play Device Redirection Framework and discussed how to redirect Windows Portable Devices based digital cameras and media players. In this part, we are going to talk about a targeted retail customer scenario – how the Framework can help in redirection of Microsoft Point of Service for .NET devices over the Remote Desktop Protocol.

 

Microsoft Point of Service for .NET

 

With the remote computer being Windows Server codename "Longhorn",  you can also redirect Microsoft Point of Service for .NET devices that use Microsoft POS for .NET 1.11.

 

Note

Microsoft Point of Service for .NET device redirection is only supported if the terminal server is running an x86-based version of Windows Server codename "Longhorn".

 

For more information, see Microsoft Point of Service for .NET on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=67182). You can download Microsoft POS for .NET 1.11 from the Microsoft Download Center (here).

 

To implement Microsoft POS for .NET 1.11 on your terminal server:

 

1.       Install Microsoft POS for .NET 1.11

2.       Install the .NET service objects or configuration XML files for the Microsoft Point of Service for .NET device. The device service objects or configuration XML files are usually provided by the device vendor and are written to work with POS for .NET by using the Microsoft POS for .NET 1.11 Software Development Kit (SDK). You can install the device service objects or configuration XML files through the standard installation software that accompanies the device. For installation instructions for the specific Microsoft Point of Service for .NET device that you are using, consult the device’s manual.

3.       After you install the device service objects or configuration XML files for all the Microsoft Point of Service for .NET devices that you are supporting on the terminal server, you need to stop and start the Terminal Services UserMode Port Redirector service. To restart the Terminal Services UserMode Port Redirector service, follow these steps:

a.       Open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.

b.      In the Services dialog box, in the Name column, right-click Terminal Services UserMode Port Redirector, and then click Restart.

 

Note

Restart the Terminal Services UserMode Port Redirector service only after you have installed the device server objects or configuration XML files for all the Microsoft Point of Service for .NET devices that you are supporting on the terminal server. If you later install a new device server object or configuration XML file on your terminal server for a Microsoft Point of Service for .NET device, you will need to restart the Terminal Services UserMode Port Redirector service.

 

Microsoft Point of Service for .NET devices, by default, are not listed under Local devices and resources on the Local Resources tab in Remote Desktop Connection. Therefore, to enable Microsoft Point of Service for .NET devices for redirection, you need to edit the Remote Desktop Protocol (.rdp) file that you use to connect to the terminal server.

 

To enable Microsoft Point of Service for .NET device redirection in an .rdp file:

 

Open the .rdp file in a text editor. Add or change the following setting:

 

redirectposdevices:i:<value>

 

·         If <value> = 0, Microsoft Point of Service for .NET device redirection is disabled.

·         If <value> = 1, Microsoft Point of Service for .NET device redirection is enabled.

 

For more information about .rdp file settings, see Remote Desktop Protocol settings in Windows Server 2003 and in Windows XP (http://go.microsoft.com/fwlink/?linkid=66168).

 

After you have implemented Microsoft POS for .NET 1.11 on your terminal server and have enabled Microsoft Point of Service for .NET device redirection in your .rdp file, plug in your Microsoft Point of Service for .NET device and then connect to the remote computer by using the modified .rdp file. After you connect to the remote computer, you should see the Microsoft Point of Service for .NET device that is redirected get automatically installed on the remote computer. Plug and Play notifications will appear in the taskbar on the remote computer.

 

After the redirected Microsoft Point of Service for .NET device is installed on the remote computer, any Microsoft Point of Service for .NET application residing on the terminal server can access the Microsoft Point of Service for .NET device as if the device were available locally. There is a sample application in the POS for .NET 1.11 SDK that you can use to test access to and the functionality of the redirected Microsoft Point of Service for .NET device. The sample application is called ccltestapp.exe and can be found in the \SDK\Samples\Sample Application folder in the folder where you installed POS for .NET.

 

You can control Microsoft Point of Service for .NET device redirection by using the same Group Policy settings used for Windows Portable Devices redirection or using the Client Settings tab in the Terminal Server Configuration tool (tsconfig.msc).

 

In the last part, I'll discuss how you can optimize your driver to work with PnP Redirection.

Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • Microsoft POS for .NET 1.11 has been released.  I've updated the link above.

Page 1 of 1 (1 items)