Knowledgebase
Printer Redirection on terminal server
Posted by David Saliba on 03 March 2010 04:56 PM

When setting up printer redirection on a terminal server policy setting may be useful in setting up how the Terminal Services print spooler behaves when a driver is not found:

Specify terminal server fallback printer driver behavior

This policy setting allows you to specify the terminal server fallback printer driver behavior.

By default, the terminal server fallback printer driver is disabled. If the terminal server does not have a printer driver that matches the client's printer, no printer will be available for the terminal server session.

If you enable this policy setting, the fallback printer driver is enabled, and the default behavior is for the terminal server to find a suitable printer driver. If one is not found, the client's printer is not available. You can choose to change this default behavior. The available options are:

Do nothing if one is not found  

If there is a printer driver mismatch, the server will attempt to find a suitable driver. If one is not found, the client's printer is not available. This is the default behavior.

Default to PCL if one is not found  

If no suitable printer driver can be found, default to the Printer Control Language (PCL) fallback printer driver.

Default to PS if one is not found  

If no suitable printer driver can be found, default to the PostScript (PS) fallback printer driver.

Show both PCL and PS if one is not found  

If no suitable driver can be found, show both PS and PCL-based fallback printer drivers.

If you disable this policy setting, the terminal server fallback driver is disabled and the terminal server will not attempt to use the fallback printer driver.

If you do not configure this policy setting, the fallback printer driver behavior is off by default.

Please note: If the “Do not allow client printer redirection policy” setting is enabled, this policy setting is ignored and the fallback printer driver is disabled.

 

Original article: http://technet.microsoft.com/en-us/library/cc731963%28WS.10%29.aspx




 

  • Please make sure that you are running the latest build. To find out what the latest version/build is, kindly visit the following link: http://www.2x.com/downloads/
  • Please note that in order to upgrade, you must have purchased the upgrade insurance, as licenses need to be upgraded in order to work on a later build.
  • To find out what is the version you currently have installed on your ThinClientServer, please open the console and check the currently installed version from the top right of your screen.
  • To find out what is the currently installed version of your 2X Application, please open the console and navigate to help>about.
  • Please kindly note that the issues and resolution presented on this article may be obsolete or no longer helpful with the latest version of your 2X Application. Should you require further assistance, please submit a ticket with Technical Support from the following link: http://2x.helpserve.com/index.php?_m=tickets&_a=submit
  • Please be aware that links related to 3rd parties like Microsoft, may sometimes be replaced or moved by the 3rd party itself.
(321 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: