CLIENT PRINTER MAPPING

Client printer mapping allows a user to access client printers from within a Presentation Server session. Client printers are mapped into the Presentation Server session upon logon and are called auto-created printers. They are automatically removed from the server upon session termination. Published applications often rely on auto-created printers to provide access to a printer, as print management utilities may not be available from the application itself. Client printers are supported in different ways, depending on the operating system of the client machine. Presentation Server servers are able to automatically map all printers that are installed locally on Windows 32-bit clients , provided a suitable driver is installed on the server or the Universal Print Driver is used.

These printers will show up in the user's session as

  printer_name  on  server_name (  from  client_name)  in  session_ID  

If legacy printer names are being used, they will show up as

 Client  \ user_name#name_on_remote  

When the users print to the network printers from the server farm, they see the original network printer names.

Tip 

Many legacy applications don't rely solely on the native Windows print features; instead, the applications read from the available Windows printers and store the selected printer in an ini file, configuration file, or similar structure. Since these files are part of the user's profile, the application expects the printer name to be identical session-to-session. With the new naming convention ("in session_ID ") the name changes every session and the application is unable to "reset" the previously stored printer nameit no longer exists. To overcome this behavior, use the legacy printer naming policy.