Презентация на тему Optimizing device drivers for terminal server’s plug and play device redirection framework

ready
Call to action

in Windows Vista and Windows Server codenamed “Longhorn”
Aligned with

Terminal Server vision of providing rich remote experiences
Ability to redirect certain types of PnP devices over Remote Desktop Connection or using Remote Programs
Applications access PnP devices seamlessly regardless of whether they run locally or remotely
Redirected devices scoped per session

potentially any type of PnP device to be redirected
Certain

set of rules to be followed to write supported device drivers
All rules required to write drivers based on new User-Mode Driver Framework (UMDF) apply
Windows Logo Program for devices ascertains Terminal Server redirection readiness of device

Stack
Hardware



RDP protocol
stack








Application





Device redirection components
RDP protocol components
User - Mode

Driver Framework (UMDF)
Real device components

PnP Redirector

IO Redirector

UmRdpService

Redirection Driver

UMDF Reflector

Bus IO

PnP Events

IO Replay

RDP Virtual Channel

RDP Virtual Channel

PnP Protocol

Reflected IO

IO

actual device driver required on server
Use Terminal Server redirection

driver on server
Takes care of I/O and PnP traffic between actual device driver on client and application on server
PnP and I/O notifications sent only to appropriate device in correct session
Support for dynamically adding or removing devices while session is active

(WPD)
MTP (Media Transfer Protocol) and PTP (Picture Transfer Protocol)-based

devices
Windows Embedded for POS (Point of Service) Devices
Using Microsoft POS for .NET 1.1

guidelines
Follow Terminal Server redirection guidelines
Modify your driver INF
Get Logo
Depends

on whether your device category in WDK includes the Terminal Server redirection Logo test

communicate between driver and application
Do not pass kernel objects

between driver and application
Do not pass data pointers for pre-allocated shared kernel buffers

of locality of reference
Do not use shared memory
Do

not use registry
Do allow your 32-bit driver to be able to talk to your 64-bit application and vice-versa
Do not have strict timing expectations in responses
Do allow multiple simultaneous access to device
Do allow normal user context access to device

INF should load the TS redirection driver instead of

the actual device driver
On the client, the driver INF should register the device as being available for redirection
Only then the TS Client UI will enumerate it in the list of supported PnP devices for redirection

Windows Vista
Requires two machine logical client/server setup
Client/Server can both

be Windows Vista
Require modified driver INF
WDK lab at room 617 tomorrow at 9 am

for more categories of PnP devices
Windows Mobile devices, scanners,

etc.
Generalization of Windows Driver Kit Terminal Server redirection Logo test
More device categories to be added
Inclusion of checks in driver development tools like PREfast for drivers

Vista and beyond
Follow UMDF guidelines
Follow TS redirection guidelines
Modify your

driver INF
Get Logo (if applicable)

Requirements for Windows Vista and Windows Server codenamed “Longhorn”:
http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx

White paper on Device Driver INF Changes for Plug and Play Device Redirection on Terminal Server: http://www.microsoft.com/whdc/driver/install/ts_redirect.mspx
Related Sessions
Ask The Experts session at noon tomorrow
Windows Driver Kit Lab: Room 617 at 9 am on 05/25/2006
User-Mode Driver Framework: Introduction and Overview
User-Mode Driver Framework: Technical Synopsis
User-Mode Driver Framework Lab
For further questions on the Terminal Server PnP Device Redirection Framework, please send e-mail to:

tspnp @ microsoft.com

Windows, Windows Vista and other product names are or

may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.