Use terminal services easy print printer driver first

This policy setting is located in the following node of the Local Group Policy Editor:. Enabled or Not configured: If this policy setting is enabled or not configured, the terminal server will first try to use the Terminal Services Easy Print driver to install all client printers. If for any reason the Terminal Services Easy Print driver cannot be used, a printer driver on the terminal server that matches the client printer will be used.

If the terminal server does not have a printer driver that matches the client printer, the client printer will not be available for the Terminal Services session. By default, this policy setting is not configured. Disabled: If you disable this policy setting, the terminal server will try to find a suitable printer driver to install the client printer.

If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer.

If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session. Office Office Exchange Server. Not an IT pro? In this case, enable the policy named Redirect only the default client printer. Thus, by using the Easy Print you can greatly simplify the configuration of Remote Desktop servers. Another thing is that the Administrator will no longer need to install the same printer drivers on the server and the local computer.

Great article, thanks! Are there any new requirements to make Easy Print work in Windows Server ? Even with the Easy print GPO enabled. Have you had this problem before? Hi, Your article was really helpful, I followed each and every step.

As mentioned above, the general idea behind the solution is to make a driver on the server that redirects all printing related work to the local machine. The implementation of this solution comes in two pieces. The first piece is presenting the user with printing preferences through UI so that they may configure the print job on any printer they have. Instead of creating some server side UI that will show the bare minimum of preferences users need such as number of copies, landscape v.

When the user edits preferences for a print job on a redirected printer, the TS client will launch this UI from the local machine on top of the remote session. As a result, the user sees the same detailed printer-specific UI and all printer options are available to him. He would see exactly the same options as if he were printing something locally. The user's selected preferences are then redirected to the server for use when printing. Below are screenshots that show an example of the above behavior.

The mstsc window is made smaller and the theme of the printer preferences window is different. This shows that the printing preferences window is running on the TS client machine!