Dislikes: 0
Driver isolation doesnt make a difference.
Enforcing CSR via GPO doesnt make a difference.
The only thing that helps is manually disable and enable CSR on the specific printer on the printserver. ("canon method")
The thing is that even then the spooler gets f*cked sometimes and has to be restarted, CSR on that printer has to be re-dis-and-enabled which makes it work againg for a while.
Strange that Sharp cant get this to work properly...
Last edited by boutn; 12-18-2023 at 10:38 AM.
We just installed 4 Sharps in place of 4 Kyocera's that were from us as well. All drivers are from the server, and now all of them are having issues with printing jpegs from emails. It's clogging up the queue and they have to restart the print spooler, same thing on all 4.
They had issues with the Kyocera drivers that forced them to move a lot of people to local printing because of weird issues they encountered over the years.
I still think this is a server issue as we have no issues with a lot of our customers that print through server and such.
And do they use authentication/usercodes?Originally Posted by ihatefinishers13
They do. User numbers paired with Print Release. The numbers are put it on the client side within printing preferences.
It appears the people having trouble while printing and binding up the print queue were printing with the microsoft photos app, but going through a VPN. Only then would it have an issue. We just set those users up with CSR and didn't have any issues after that.
and how did you ‘just set them up with CSR’?
By default when you share from the server, it already has "client side rendering" on, so I guess the guy who went out just set them up with a local driver to use while using VPN from home.
In the end, it was the way the VPN was interacting with the print jobs, and it's rarely ever a good idea to print through any VPN.
Alrightyyyyyyyy so what we did, did not fix anything. They had issues before with Kyocera's, not the same thing, but it got resolved when they installed drivers locally. One of our thoughts is that there's just too much data for the print side of the server to handle with image files AND user codes. I know their server is virtual, so it could be something where some of their ram is failing, or the drive(s) for storage are failing. I'll let you all know whenever we get more info.
Normally, installing a local driver instead of printing via a printserver should resolve your problem.
Normally that would be the first thing... but, 4 machine's drivers need pulled down to each computer... at least 30 devices. We have a batch file that will install a single driver with all the defaults you want, but doing that for 4 drivers, plus that many PC's will be...fun. And half are remote a lot, so they probably won't even be in the office at the time. It's a cluster f...
Thanks: 
Likes: 
Reply With Quote
Bookmarks