Terminal Server USB Printer mapping

Issue: When connecting to a Windows 2003 Terminal Server over RDP, some or all of your local printers (LPT or Parallel printers seem to always autocreate), ie USB, local TCP/IP printers don’t autocreate when logging on. Some of the multifunction devices and other USB printers use DOT4 printing which isn’t recognized by default by Windows Server.

Cause:This problem occurs because the printer port does not begin with COM, LPT, or USB. By default, printer port names that do not begin with COM, LPT, or USB are only redirected in Windows Server 2003. By default, multifunction print devices may not be redirected unless you are running Windows Server 2003 on your local computer because they use DOT4 ports.

Solution: To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, open regedit and add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF. Log on to the Terminal Server and all local printers should be redirected to the server. To make sure that printing works normally, install the same printer driver on the Terminal Server so that the printer is mapped to the right driver.