Matthew Byers
asked on
Printing a pdf file from a Remote Desktop session from a Mac results in a huge file.
We have a few Macs on our network that Remote Desktop into a 2008 R2 server. When we print from a pdf document, the file it spools is so large it takes 15 min or more to print locally. If I print the exact document from a Windows PC using Remote Desktop the file may be 40kb vs 15MB if printed using redirected printer from the Mac, and prints instantly. I'm not sure what I am doing wrong or how to fix. Any printing from word, excel is fine, prints instantly. Just pdf files.
Tony J
It's not specific to Mac, but have you seen this: https://support.microsoft.com/en-us/help/919543/the-size-of-the-emf-spool-file-may-become-very-large-when-you-print-a
Expanding Tony's comment.
If your PDF file actually prints, then you're pretty much stuck with time required to print, using the method you're using.
There is likely a better way.
Ensure your .pdf files are on a file store shared by all machines, then issue a remote command to do your .pdf file printing.
Experiment with different commands till you have one which works well.
The big win using this approach is... no big temp files generated... file printing begins instantly...
If your PDF file actually prints, then you're pretty much stuck with time required to print, using the method you're using.
There is likely a better way.
Ensure your .pdf files are on a file store shared by all machines, then issue a remote command to do your .pdf file printing.
Experiment with different commands till you have one which works well.
The big win using this approach is... no big temp files generated... file printing begins instantly...
Without any info as to make or model of printer:
The problem is related to Postscript processing Macs use Postscript printing by default.
PDFs are Postscript files.
The solution in the link is not a good fix.
To totally disable EMF spooling, in the print driver>advanced tab, untick "Advanced printing features"
Try changing the spool setting in the print driver on the server to "start printing after the last page has spooled".
Ensure that you are using a Postscript driver on the server, as a PCL driver will require more processing to convert from postscript to PCL.
The print driver may have an SNMP option in the ports tab or elsewhere, if so, disable it.
Disabling "bidirectional communication" may also help.
Some printers have an option to set the buffer size, set it to the maximum.
The problem is related to Postscript processing Macs use Postscript printing by default.
PDFs are Postscript files.
The solution in the link is not a good fix.
To totally disable EMF spooling, in the print driver>advanced tab, untick "Advanced printing features"
Try changing the spool setting in the print driver on the server to "start printing after the last page has spooled".
Ensure that you are using a Postscript driver on the server, as a PCL driver will require more processing to convert from postscript to PCL.
The print driver may have an SNMP option in the ports tab or elsewhere, if so, disable it.
Disabling "bidirectional communication" may also help.
Some printers have an option to set the buffer size, set it to the maximum.
ASKER
I am not sure if its because it's a redirected printer but the options to go into advanced printing features is grayed out. I haven't found any such setting yet on the Mac they are using. Most of our printers are Kyocera FS-2100DN or M6535cidn. With the Kyocera driver installed on the Mac, the driver it seems to use via Remote Desktop is MS Publisher Imagesetter.
What driver is installed on the server?
Have you also installed a Kyocera driver on the Macs? If not, that may be the problem.
Have you also installed a Kyocera driver on the Macs? If not, that may be the problem.
Yeah the drivers all need to be installed and the same
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.