I have a functioning 2012 r2 RDS farm with 3 servers.

I added a 2012 r2 print server and used GPO to configure it as a print server.  I then created a gpo that i would use to push the printers down to the rds servers (in print manager, deployed to computer policy...)

I also setup each printer on the print server using the v.4 class drivers built in as each model printer i have is represented.

rebooted each of the rds servers and got my new network tcpip printers.

Problem: the correct printer drivers did not get pushed to the printers on the rds server

In other words when i look on the print server at "Xerox 7855 Mail Room" i see the 7800 series class driver i selected.  On rds i see "Xerox 7855 Mail Room" but the driver is the HP Color Laserjet A4/Letter PCL6 class driver

Did i miss a config that should PUSH the correct driver?

Hi,

Thanks for your post.

We could use Terminal Services Printing-Related Group Policy Settings to help control Terminal Services printing behavior.

https://technet.microsoft.com/en-us/library/ff519193%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

How did you configure the group policy?

Regards.

I have these set:

Do not allow client printer redirection disabled

Do not set default client printer to be default printer in a session enabled

Redirect only the default client printer enabled

Specify terminal server fallback printer driver behavior enabled Show both PCL and PS if one is not found though truthfully i never really understood this one.

I have these set:

Do not allow client printer redirection disabled

Do not set default client printer to be default printer in a session enabled

Redirect only the default client printer enabled

Specify terminal server fallback printer driver behavior enabled Show both PCL and PS if one is not found though truthfully i never really understood this one.

Use remote desktop easy print first is also set to disabled.

• Edited by Willmeister Friday, July 03, 2015 9:09 AM rd easy print

Hi Willmeister,

I think RDS is hitting  terminal server fallback printer driver behavior.

For some reason RDS server does not have Xerox WorkCentre 7800 series class driver installed, and tries to find closest matching driver which is HP Color Laserjet A4/Letter PCL6 class driver.

Try to install Xerox WorkCentre 7800 series class driver on RDS server and check.

KR,

Sergey.

thats sort of my point though fallback to that driver seems odd to me.  wouldnt it just fallback to an hp laserjet 4?

as a test i'll remove the fallback config.

but the real point, isn't the print server supposed to *install* the correct driver when it pushes the printer to the client?  in this case the client being an rds server..

There are NO print drivers deployed when using type 4 "Class" drivers (except the case when Win7 / Server 2008R2 is the client machine).  That's the point of the class driver, the print spooler service is no longer a software provider.

The connection is setup using some registry information.  It sounds like an HP driver was originally used for the printer and this data was never purged.

I think if you set up a new printer that uses the Xerox driver, the connection GUID data will be correct and you will not see the HP driver data.

I do know that the vendors initially setup all their print driver using some sample information.  If the sample is still in use with this print driver, what you state would be the default experience.

Setup the new printer, if you still see the same thing. I'll have to dig up the information on how this is supposed to