locked
Problem with printer drivers RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have a Windows 2003 Terminal Server server. Clients connects to it with RDP, to use Office applications and view PDF Files. The server has a number of different printer drivers installed. For example:

    - HP Laserjet 500

    - HP color Laserjet 200

    - HP Universal Printer Driver PCL5.

    And about ten more drivers.

    Clients connect to server and have diferent printers, each with each driver. The problem is that, whatever model of printer the client has, with whatever driver it has installed, the mapped printer in the server takes the HP 500 Driver. So every single printer mapped in the server, is being mapped with the HP 500 driver, despite the server has installed the correct driver for all the printers.

    How can I achieve that if I use in a client a printer which driver is installed on the server, the server maps the printer with the correct driver instead of the HP 500?

    Tuesday, January 24, 2017 12:08 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Which way could I use an HP Universal PCL 6 driver as Failback driver?

    Please create a new registry value similar to below on the server:

    HKLM\ SYSTEM\ CurrentControlSet\ Control\ Terminal Server\ Wds\ rdpwd

    FallbackPclDriver     REG_SZ     HP Universal PCL 6

    Thanks.

    -TP

    Wednesday, February 8, 2017 10:13 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    Please make sure you are spelling the registry value FallbackPclDriver precisely, you are setting the data to match precisely the name of the driver as installed on the server.  Capitalization and spacing need to match exactly.  Also make sure you are creating under the correct key location.

    I just tested and was able to set the fallback driver to different drivers as desired.  For example, I created the following registry entry under rdpwd key:

    FallbackPclDriver     HP LaserJet 1200 Series PCL

    Immediately after creating the entry I logged on a fresh session and the redirected printers used the 1200 driver as expected.  I didn't have to restart the spooler or server for the change to take effect.

    Thanks.

    -TP


    • Edited by TP []MVP Thursday, February 9, 2017 11:35 PM
    • Proposed as answer by Amy Wang_ Friday, February 10, 2017 5:31 AM
    • Marked as answer by TP []MVP Thursday, February 16, 2017 12:52 AM
    Thursday, February 9, 2017 11:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Francisco,

    As Windows Server 2003 is out of support, please upgrade Operating System to get more efficient assistance.

    In addition, you may try to test whether creating a custom printer mapping file would help:

    https://technet.microsoft.com/en-us/library/ff519149(v=ws.10).aspx

    Best Regards,

    Amy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 25, 2017 11:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you very much. I can't test it today, but I'll do it tomorrow.
    Wednesday, January 25, 2017 12:14 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    From your description it sounds like the server is configured to use a custom print driver mapping file and possibly the fallback printer driver.  As a start, I would suggest restoring things to default behavior and then testing.

    To restore to default, make sure Terminal Server Fallback Printer Driver Behavior group policy setting is set to Not Configured and remove the registry entries (PrinterMappingINFName and PrinterMappingINFSection) for custom print driver mapping.  Path for group policy setting and registry values below:

    Computer Configuration\ Administrative Templates\ Windows Components\ Terminal Services\ Client/Server data redirection\

    HKLM\ SYSTEM\ CurrentControlSet\ Control\ Terminal Server\ Wds\ rdpwd\

    Please note that some manufacturer printer drivers will cause spooler crashing and other undesired/odd behavior.  As a result you may need to try different versions of manufacturer drivers and/or use a custom mapping file to force a different driver to be used and/or use the fallback printer driver for some printers.

    Thanks.

    -TP

    • Proposed as answer by Amy Wang_ Thursday, January 26, 2017 2:11 AM
    Wednesday, January 25, 2017 12:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The inf file did the trick. There are many printers that still are being mapped to the wrong driver, but that is because the client driver name is not exactly the one that I have written in the inf file, I have figured out the name. I have to go client by client writing the correct driver name.

    Thursday, January 26, 2017 10:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Glad to hear that the issue is resolved!

    Please mark the helpful reply as answer, which would be much more efficient for other forum community members to find useful information.

    Best Regards,

    Amy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 30, 2017 1:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi again,

    The problem is not solved. It is very very strange. I have made the inf file, and put there some lines mapping printer drivers to the driver name. In some cases, it works. But in some other, it doesn't. So, for example, I have this line in the inf file:

    "HP LaserJet P2050 Series PCL6" = "HP LaserJet P2055 PCL6"

    When a client has a printer which driver name is "HP LaserJet P2055 PCL6" in the remote desktop session that printer is mapped to the server installed HP LaserJet P2050 Series PCL6. But I have this other line:

    "HP LaserJet 200 color M251 PCL 6" = "HP LaserJet 200 color M251 PCL6 Class Driver"

    And when the client with a printer which driver name is "HP LaserJet 200 color M251 PCL6 Class Driver", that printer is mapped and assigned to a HP Deskjet 500 driver. The funny thing is that I have uninstalled the Deskjet 500 driver from the server, and when the client connects with the "HP LaserJet 200 color M251 PCL6 Class Driver", the HP Deskjet 500 driver is installed again in the server and mapped to that printer and the user cannot print.

    Thursday, February 2, 2017 8:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    That seems like a different printer mapping file is configured, please double check .inf file.

    In addition, restart Print Spooler service to test.

    Best Regards,

    Amy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Edited by Amy Wang_ Monday, February 6, 2017 10:24 AM
    Monday, February 6, 2017 10:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks. No reference to HP Deskjet 500 driver in inf file. Print Spooler service has been restarted several times
    Monday, February 6, 2017 10:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Did you make sure the TS Fallback driver Disabled as I mentioned above?  By making sure the group policy setting is Not Configured, this will revert to the default behavior of it being Disabled.  You can use gpresult.exe to verify the effective setting.

    With the fallback driver enabled, if there is a problem finding a matching driver or there is some issue using the matching driver it will use the DeskJet 500 driver (if PCL option is selected for fallback).

    -TP

    Monday, February 6, 2017 11:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks.

    I am not really sure if the failback driver is disabled. There are many GPO's in the domain. But tomorrow I will search in all GPOs applied to that server.

    But I am not sure about the implications. If I disable the driver failback and a printer without associated driver connects, what driver will that printer map?

    And where is configured that, if diver failback is enabled, the failback driver be the HP Deskjet 500?

    Monday, February 6, 2017 12:23 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    With fallback driver disabled, if it can't find a suitable driver or has some issue mapping then the printer will not be created.

    HP DeskJet 500 is the default TS fallback driver for PCL black and white printers.  If color is part of the driver name it should use the DeskJet 550C driver instead by default.  There is option to create registry entry to change the default driver for PCL and/or PS, but this driver applies to all cases where fallback is used.

    -TP

    • Proposed as answer by Amy Wang_ Tuesday, February 7, 2017 2:23 AM
    Monday, February 6, 2017 4:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Which way could I use an HP Universal PCL 6 driver as Failback driver?

    Tuesday, February 7, 2017 8:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Which way could I use an HP Universal PCL 6 driver as Failback driver?

    Hi,

    I am not able to find a built-in method to achieve that goal.

    Best Regards,

    Amy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 8, 2017 9:54 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Which way could I use an HP Universal PCL 6 driver as Failback driver?

    Please create a new registry value similar to below on the server:

    HKLM\ SYSTEM\ CurrentControlSet\ Control\ Terminal Server\ Wds\ rdpwd

    FallbackPclDriver     REG_SZ     HP Universal PCL 6

    Thanks.

    -TP

    Wednesday, February 8, 2017 10:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, thanks for the answers.

    I have create the registry key, I have restarted the spool printer service, but the printers still use the HP Deskjet 500.

    Thursday, February 9, 2017 8:35 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    Please make sure you are spelling the registry value FallbackPclDriver precisely, you are setting the data to match precisely the name of the driver as installed on the server.  Capitalization and spacing need to match exactly.  Also make sure you are creating under the correct key location.

    I just tested and was able to set the fallback driver to different drivers as desired.  For example, I created the following registry entry under rdpwd key:

    FallbackPclDriver     HP LaserJet 1200 Series PCL

    Immediately after creating the entry I logged on a fresh session and the redirected printers used the 1200 driver as expected.  I didn't have to restart the spooler or server for the change to take effect.

    Thanks.

    -TP


    • Edited by TP []MVP Thursday, February 9, 2017 11:35 PM
    • Proposed as answer by Amy Wang_ Friday, February 10, 2017 5:31 AM
    • Marked as answer by TP []MVP Thursday, February 16, 2017 12:52 AM
    Thursday, February 9, 2017 11:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It worked. Thanks!!
    Wednesday, February 15, 2017 10:53 AM