kyocera print issues
Just wanted ask if anyone has ever had the same problem as us.
During the summer our servers where migrated to 2008r2 and CC4 Management for a W7 desktop enviornment. Our printer fleet is uniform, all Kyocera which we have been quite happy with. All the relevent drivers were installed and all seemed fine during the holidays. One of my first tasks i undertook was to install papercutNG which we used on our W2003/CC3/XP enviornment with no issues. All our printers are spanned over servers 2,3 & 4 (we didn't wish to use the primary DC for obvious reasons). All was fine until WSUS restarted one of the servers (we left it at the log in screen, not logged in) and then the whole fleet starting slowing down to the point that after a day and a half, nothing would print.
When we uninstalled papercutNG and suddenly the printer queues started to jump back into life *YAY*, but it was short lived as the speed degraded again and does every 24 hours with some printers throwing up errors. We chop and change between the universal drivers and the KX drivers but after a short while is slows down again.
Current speed is around 90 secs for a test page to hit the printer to get the data LED flashing on the panel.
This effects all 3 servers and are showing indentical symptoms, do you reckon i have mangled the print spooler?
Just deploying a load of kyocera's now. With PaperCut on the server. So I read this question and get a sinking feeling...
Have you tried installing the hotfixes mentioned in:
Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2
(they may even come down with Windows Updates now, so in fact it may be more relevent to ask, have you tried uninstalling the hotfixes mentioned in that article!)
Are you running the latest release of papercut? Have you raised a support ticket with them?
Is it the length of time the spooler is up, or the number of jobs printed that is the factor? Might there be one particular job that is causing it?
It's the free version with the NG suffix of papercut, hence no support, but there is quite a lot of factors where things could have gone wrong (papercutNG/CC4 Printer credit service/drivers/print spooler)... Just installed our colour printer on our DC thats never had papercut installed I am going to roll out this printer site wide and see what happens!
I think its definately down to the papercut fudging the print spooler service. I migrated our main colour printer to our forest route (which never saw papercut) and its still sending rapid prints. I have a MS hotfix which I am going to roll out across the servers- this should repair the spoolers.
We are having the same issue here. Our printserver restarted after a WSUS update and then we started getting the slowness. We have installed Papercut since we have had problems but I think it was definitely the update that has caused issues - not papercut
Just applied the MS rollup that psydii across all the servers now. Going to be testing tomorrow.
We had a migration to CC4.3 with 2008 R2 servers over the summer and have had many problems with slow printing and printers not mapping.
We found that using the Kyocera universal driver and the KX driver resulted in the printers mapping slowly (or not at all) and taking a long time to print. We've now moved nearly all over the KPDL versions of the driver if available. These seem to have the printers mapping and printing much quicker!
Hi Chris, we had changed all ours to the universal driver, but being generic it stopped staff and pupils printing double sided etc, just moved back all printers to the KX driver after updating the servers and will see how things run....
recently migrated our kyocera drivers to 2008R2 and the performance has been very poor compared to the old setup on 2003, there appears to be an improvement in priting speed when using the classic PCL kyocera drivers. have not tried the KDPL drivers as found the KX ones are more user friendly for setting options at print time.
found these posts on technet which might be of interest.
Delayed Print Jobs
Print Spooler slowdowns
the last one has an interesting point about the printer port dns.
with this im assuming the client is setup with local port printing to a printer share?
printing direct to IP doesnt have the same problem so that does narrow it down to actually being forwarded from the server to the printer.
ahh the march of progress lol
the universal PCL driver does have 2 sided printing? with version 2.42
Originally Posted by andyturpie
We found issues with the universal driver not letting people print colour on the colour printers.
Originally Posted by andyturpie
If you still have issues with the KX driver try the KPDL :)
having switched to the PCL driver on the server have spent the last couple of days with very swift printing have been keeping an eye on it to see if its an issue of connections not being dropped etc but so far looking alot better
We have A similar problem. We installed A managed print soloution in June 2012 with XP clients and PapercutMF and server 2008R2 All was great until summer when we began migrating clients to windows 7. The Client PC's running Windows 7 would error print jobs and then delete them. The only solution I have found is adding users to the built in print opperators group. This solution works great from staff but doesn't work for students as membership of built in groups breaks delegate control for non administrators. ( teachers could no longer reset passwords.) So at the moment our student workstations are stuck at XP. Antone have a solution that works with this.
What did you guys find to be the eventual solution here?
I've recently run some MS updates (I was a little behind) and we are now experiencing the delaying printing too.
Hi Enjay, not found a solution to the problem as yet apart from move printers from a 64bit OS to a 32bit OS. We are a bit stuck though as as a CC4 network, all our servers are 64bit members. Our print lease runs out in 6 months and will possibly move to papercut and sack RM Printer credits completely (If we feel that follow me printing is for us).
We ran a trial of papercut on a vanilla 2003 server and it worked a treat. The main issue for us is that the database behind papercut and the printer credit system are not compatable. The only thing I can suggest is to recreate new printer queues if you are in the same boat as us.