Thank you for your reply! I think I've found a solution:
'We've configured our PC's to search for drivers on a network location when they're not found in %SystemRoot%\Inf
This is done by adding a network path to
When we delete the network portion the printer objects are added rapidly. I must now see if I can add some info to %SystemRoot%\Inf to prevent the systems from searching on the network.
Any suggestions would be welcome.
normally when the driver is installed once on a client, its not installed again when adding a new queue with the same driver
maybe you are running into a policy issue on the clients ?
Ik am having an issue with connecting to network printers in our organisation:
We have one printserver with 5 Xerox printers. all using the Xerox GPD PS V3.5.404.8.0 driver When logging on to machines and connecting to one of the printers The driver is downloaded and installed and the printer works fine. However, when a second or third (or 4rth or 5th) printer is added, every time the driver is downloaded and installed again from the printserver. Even though the driver is allready present on the system. This is time consuming and the CPU (spoolsv process) takes up to 100% of system resources. This is a problem for our users on Stateless VDI's who have the 5 printer mappings created using a script, everytime a user session is created. We've made sure the driver is allready installed on the disk images of our VDI's, but this doesn't reduce overhead.
Is it default behaviour to (re)install the driver for every printer object that a user creates or can we infuence this behaviour with some configuration/installation option.