Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 30, 2014 2:39 PM
We are having an issue with a Kyocera driver. We recently started getting new models of some of these Kyocera copiers, and with it a newer version of the same driver. The new copiers are slightly different. The driver version went from 5.x to 6.x We soon discovered that the two don't work well together on the same print server. Some departments all of the sudden can't print. The error they get is "can't connect to printer". As if there is no driver.
On the print server I updated the driver for our printer here in the IT department. I didn't just update it from the existing printer (Properties>Advanced Tab>New Driver), I instead deleted the printer, recreated it, and used the new driver when I recreated it. That worked here in the IT dept. It does not work in other departments. A day later they still have the old driver. Rebooting does nothing. I got the new driver within 3 minutes of updating it on the server.
Seems like a rights issue. I give them "manage printer" rights. Still don't download the new driver. But... they can all of the sudden print - with the old driver! Makes no sense.
Under normal circumstances, shouldn't they get the new driver whenever I update it on the server?
All replies (10)
Thursday, January 30, 2014 4:54 PM
Typically the clients will not request the new driver until the next time they perform a print task.
What operating system on the print server and on the client machines?
If server 2008 or greater, is the print driver package aware? You can see this in PrintManagement.
Are you admin on your own machine? Are the users that are not in IT admins on their machines?
Alan Morris Windows Printing Team
Thursday, January 30, 2014 6:07 PM
Typically the clients will not request the new driver until the next time they perform a print task.
What operating system on the print server and on the client machines?
If server 2008 or greater, is the print driver package aware? You can see this in PrintManagement.
Are you admin on your own machine? Are the users that are not in IT admins on their machines?
Alan Morris Windows Printing Team
What operating system on the print server and on the client machines?
On the Server it's 2008 R2. Clients are all Windows 7
is the print driver package aware?
In Print Management>Server>Drivers, it says "true" in the "packaged" column
Are you admin on your own machine? Are the users that are not in IT admins on their machines?
I am an admin on my machine. The non-IT users are not admins.
FYI: if the user attempts to print, they do not pull the new driver after that. They still have the old driver
Thursday, January 30, 2014 6:22 PM
I assume the print driver is signed. Take a look in the Print-Service / Admin event log for errors.
Alan Morris Windows Printing Team
Thursday, January 30, 2014 7:00 PM
Honestly, I'm not sure if it's signed. I believe it is. I don't recall getting the warning that it's not when installing it.
In the Print-Service/Admin logs I see a bunch of these:
Failed to upgrade printer settings for printer \MC-PRINT\Building-CopyStar4550ci,0,LocalOnly driver C:\Windows\system32\spool\DRIVERS\x64\3\KMUU53CE.DLL. Error: 0. The device settings for the printer are set to those configured by the manufacturer.
That was probably when I tried to update the driver on the printer server yesterday.
It's been obvious that the 5.x and the 6.x can't be on a print server at the same time. Probably causing driver corruption. And maybe that's why the clients don't pull the updated version? I'm not sure.
Monday, February 3, 2014 8:11 AM
Hi,
Please refer to "Add drivers for client computers running 32-bit or 64-bit versions of Windows" part in this article:
http://technet.microsoft.com/en-us/library/cc732946.aspx
Also here is a similar thread:
Update printer drivers with Group Policy
If you have any feedback on our support, please send to [email protected].
Thursday, February 6, 2014 7:01 PM
Hi,
Please refer to "Add drivers for client computers running 32-bit or 64-bit versions of Windows" part in this article:
http://technet.microsoft.com/en-us/library/cc732946.aspx
Also here is a similar thread:
Update printer drivers with Group Policy
If you have any feedback on our support, please send to [email protected].
Yes, I'm aware of that. I always load the 64 bit driver first on our Server 2008 R2 box. Actually, you have no other choice - can't add the 32 bit drivers first.
This is a different issue. I update the driver on the print server to a newer driver version. The clients do not pull this newer version down unless they have local admin rights. Which is just wrong. They should pull it down no matter what. I'm guessing it has something to do with driver corruption or driver incompatibility.
Friday, February 7, 2014 12:21 AM | 1 vote
The clients do not pull this newer version down unless they have local admin rights. Which is just wrong. They should pull it down no matter what. I'm guessing it has something to do with driver corruption or driver incompatibility.
There are GPOs to allow users to install print drivers w/o admin. Take a read:
http://support.microsoft.com/kb/319939
http://support.microsoft.com/kb/2307161
http://technet.microsoft.com/en-us/library/cc753269.aspx
Wednesday, August 6, 2014 1:40 PM
I'm new at this, but we had a similar problem re similar devices with different/newer drivers. I had to ask the users to delete the printer and add it back. It worked. Not sure if there's another way, but that worked for us.
Tuesday, July 21, 2015 3:53 PM
It's been a while since his post but I don't see any update or whether you came to a resolution. I was wondering how you are pushing the printers to the end devices? Are you using GPPrefs at machine or user level? Or are you using GPPolicies side with Deploy printer? If you are using GPPref how are you pushing printer? With the Replace or Update?
Thursday, September 10, 2015 10:22 PM
We also had a tedious experience where a corrupted printer driver stopping the spool service on a number of Windows 8.1 clients. While troubleshooting and fixing the issue, we tried to figure out how and when the clients get an updated print drivers from the print server. We are running a Windows 2008 R2 print server with printers deployed to computers through Print management. Appreciate if some one can explain how clients get the drivers or point to a KB article.
We have plans to implement location (sub net) aware printer deployment using Group Policy Preference and also upgrade the print server to 2012 R2. Are there significant changes in the way clients download printer drivers on a 212 R2 print server?
Thank you.