I know how shitty this thing is. If they solved it, itās going to be massive!
Thereās a big technical gap in printing and thatās the size of the file while it gets spooled. PDFs or documents with embedded pictures are the ones creating issues.
I saw countless cases of 10-20 pages being printed by the user and the printer ends up with a 4GB spool file. Thatās outrageous and again, I doubt that Microsoft has a fix for this and I wonāt be the one sending Terabytes of data on a daily basis to the cloud and then back to the printers š
Printing is like capacitors on a mainboard. The dinosaurs of the IT environment.
Iāve seen improvements in printing and drivers but theyāre all prone to issues since these are all tweaks. Things need to be re-architected and this should have happened 15 years ago but everyone predicted that printing will slowly die. Aaaand it didnāt! And it wonāt die.
With Follow me, the situation is even worse because the job is pulled by the printer from the print server when the user is already in front of the computer. The waiting time is higherĀ because the user needs to wait for the whole job to be transferred to the printer then get printed when for normal printers, the user would probably have a certain percentage of the job already printed when (s)he gets to the printer.
Printing isnāt āhardā on all users categories working in the enterprise. IT is the least affected. IT people print in average, about 50 pages per month, the average in an enterprise is 500 pages per month and procurement & finance jump to āthousandsā. Thereās a productivity impact that needs to be calculated too and probably most people wonāt feel a change like that, most of the time but there are those documents that will drive people mad