Local Printer Added to Terminal Services Session Using the RDP Client

In Windows 2000, a local printer is automatically added to a Terminal Services client for a Terminal Session.

This only works for printers that are locally attached to the clients parallel or serial port.

To see this behavior, perform the following steps:

1. Connect a printer to Lpt1 on the computer running the client session, and then install the print driver locally. Configure this printer as the default printer.
2. Install the Windows 2000 Terminal Client on the computer running the client session.
3. Using Terminal Services, connect to a computer running Windows 2000 Server with Terminal Services.
4. Check the printers folder in the terminal session and note that the default local printer is automatically added as the default printer in the terminal session.

Printers are automatically added for the following operating systems:

• Windows 9x
• Windows NT 4.0 Workstation and Server
• Windows 2000 Professional, Server, Advanced Server and Datacenter
• Windows Based Terminals (WBT) that conform to the WBT 2.0 specification. (Contact your WBT OEM for availability.)

This entire creation process uses the Windows 2000 Plug and Play architecture. When Windows 2000 adds the printer, it automatically installs the driver required for the printer. (As long as the printer is a model for which a driver is already installed or supported.)

All printers that are automatically created are registered in the following registry key: NOTE: The above key is one path, but has been wrapped for readability.