Print Drivers and windows 10

[JackT]

Not sure if this is a windows 10 issue or a server 2012 R2 issue but we've moved over to papercut over the past week and were having a small issue with mapping one printer using a mono only driver. Mapping the drives via a user gpo works fine for all the other printers but this mono only driver will not deploy. The error message we keep seeing in the event viewer is that the system cant find the driver needed but if you path to the printer manually it pulls down and installs the driver without issues.

 

Anyone got an ideas?

[ITJS2015]

I assume your hosting your network printers via a server, have you added both x64 and x86 drivers into the additional drivers tab on the printer ?

 

Are going through devices and printers or using the run method \\servername

[SHimmer45]

both driver versions for 64 and 32 bit need to match otherwise it will grumble when trying to install the printer.

[JackT]

Yes its on a brand new server running 2012 R2. Only installed the 64 Bit Drivers as we only have 64 bit clients. Works fine for all other printers apart from this one driver which is being a pain.

 

We are deploying via a gpo but i have manually done it via the \\servername and via the control panel. The machine will pull the driver down with no issues if you manually do it via \\servername but not via gpo.

[ITJS2015]

Usually before I image a machine is to install the printer drivers and then you can map via gpo in which case do you have sccm ? you can deploy a driver out to machine that way and map the printer via gpo

[ITJS2015]

Try This

[JackT]

Thanks for the video, i'd rather like to avoid using print management if possible since we are using papercut. It makes no sense that all the other printers work fine apart from this one driver which the clients are unable to location unless you do it manually.