Quantcast
Channel: Print/Fax forum
Viewing all articles
Browse latest Browse all 3156

Windows 2008R2 RDS - Slow Mapping of Printers and Drivers - Advice on preventing the logon process from mapping driver when GPP adds printers.

$
0
0

Good Afternoon Experts, I'm really struggling with slow printer mapping and am after some advice.

Heres our Environment

Print Server: Windows 2008 R2, Kyocera Printer fleet using Kyocera KX Package aware drivers version 6.0.2212

RDS Servers: Windows 2008 R2 pre installed with same print drivers as print server.  - GPP used to map printers for users at logon,

Thin Clients, so cannot use Easy Print.

Some of our offices have up to 20 printers and users on the office RDS have every printer in the office mapped at logon using GPP. The problem is that the printer mapping process for our large offices can take almost 10 minutes (30 secs per printer ish). Reading into the problem suggests that when a printer is mapped the server copies the print driver from the print server, checks its version and updates the RDS version as necessary. - Please correct me if i'm wrong in my thinking here..

If i'm correct and the package aware driver is causing this can anyone advise as to how we can improve the matter. The driver on the print server can only be updated by Admins therefore very rarely changes. This seems a very inefficient process to me there has to be a way to stop the printer mapping process from checking the driver version every time and just use the preinstalled identical version.

One RDS server can have up to 25 users on and our worst office has 18 printers which means 450 driver installation attempts as everyone logs on !!

I've tried the old method of using a vb script to map drives and experience the same slow printer mapping.

Really hope someone can offer some useful advise.

Cheers

Andy


Viewing all articles
Browse latest Browse all 3156

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>