![canon scanner drivers are shit canon scanner drivers are shit](https://tipsonubuntu.com/wp-content/uploads/2016/08/canon-mg5720.jpg)
![canon scanner drivers are shit canon scanner drivers are shit](https://i.pinimg.com/736x/b9/16/41/b916417b767019bd0aee2dedd2682653.jpg)
90% of the time with 90% of the users, this works just fine.
![canon scanner drivers are shit canon scanner drivers are shit](https://www.hippo-deals.com/products-images/1500/388362.jpg)
I have a share with all printer drivers used. Right now I'm installing all printers with TCP/IP. The control file should contain useful information for debugging.Įmpire_Wesley wrote:Since everyone on here has said something about print servers, is that the "best practice" for printers in a network? I am slightly new to IT, so I'm still trying to figure out a few best practices to make sure I'm doing everything the best I can. There should be a control file and then the print job file. You might be able to look in the spooler folder for the job it was working on when the spooler crashed.
#CANON SCANNER DRIVERS ARE SHIT DRIVER#
We are still running a dedicated print server but we haven't had any printer related reboots on this machine since we migrated and consolidated drivers.īut in your case it is probably a bad printer driver for a printer that is used infrequently. We are mainly an HP shop and the HP universal driver was a great help for us since it supported almost 95% of our printer fleet. With that said when we migrated to 2008 on the back end we limited the number of drivers we loaded on the server. It was easier to reboot the dedicated print server. It was a PITA to perform an emergency reboot during operation hours for the the drive shares. This is when we pulled the printing from the file server and put it on a dedicated server. We typically had to manually flush the spool directory to clear the job that crashed the spooler. Sometimes we could just restart the spooler but most of the time a reboot was required. Their port monitors would crash and the only way to recover was to reboot. We fought this issue a few years ago with bad deskjet drivers.