'os X \'open Pdf In Adobe\', Printer Dialog'
Users can convert documents into PDF files using Adobe Acrobat’s PDF Printer feature; this can be a useful method of distributing compatible documents to customers or clients running different operating systems or software suites on their own computers. However, if the Adobe PDF Printer doesn’t show up on your workstation’s list of connected printer devices, you may need to repair your Adobe Acrobat installation. If repairing the installation doesn’t work, manually install the Adobe PDF Printer driver.
I have a Mac OS X and am trying to open a PDF file using Adobe Reader instead of Preview. Any suggestions - Answered by a verified Mac Support Specialist. All of a sudden my mac is not talking nice with my canon mx7600 printer. It will not print pdf documents.
Hi Anyone & Everyone, I have this very annoying issue which occurs randomly and so far i have been unable to fix; I have users at different Branch locations using different virtual terminal servers on the same hosts, print server hosts all the companies printers and they are distributed to each branch via Group Policy, E.G. A user in London who logs on to any terminal server will only have London printers and so on.
Adobe Reader DC is installed on all 2012 R2 Terminal Servers as the default application for PDF's, however now and again users are unable to print PDF's, PDF's are usually always scanned images sent via email (Outlook 2010). When printing a PDF in AR DC you get a progress bar, this disappears when it stops working.
Guy's working before me advised the user to delete the printer and re-install, due to group policy this only made things more messy in my opinion as now they get duplicate printers which i have since deleted. I found deleting the printer, having the user sign out completely from their session and back in again fixed the PDF printing, however this has served well as a fix it's not a permanent fix. So i was wondering if anyone has come across this problem before with Terminal Servers and PDF printing and if they had a more permanent fix for it, any other printing works absolutely fine, I use a laptop when I'm working so i never encounter this issue. Thanks in advance for any answers or advice! Ok so I failed to give an update.
Turns out Google Chrome had an update the previous week that for some reason broke printing from Chrome. I had to go to a previous week's VM backup to see what version was running when everything was working. There was indeed a previous version which meant chrome had an update since then. I reported the issue through the option on the browser settings. I created multiple reports. I'm sure my request fell on deaf's ears, but after a few days chrome had another update and BAM! Printing through chrome was working again.
Users get sent PDF's via Email as an attachment, they'll either use the quick print function within Outlook or open up the attachment in Adobe, go to print and nothing happens. They'll be a group of users using the same printer yet only one of them gets the problem, the rest are fine. Delete the printer, sign out and back in and they're back working again.
Then weeks later they'll email in again telling me they have the same issue, they can't print a PDF. I know it's a strange one and can be exhausting to explain, I've also found when viewing devices and printers the green tick next to their default disappears but adobe still defaults to the same printer.
Mac hard drive needs scanned for virus using windows 7. You've stated that the old OS partition is still accessible.
I have had this problem constantly in my 2012 R2 Remote Desktop Services Environment. It all started when Adobe implemented their 'Protected Mode' setup. However, even after switching to Foxit Reader I still intermittently have the issue. It only happens with PDF viewing software, users are always still able to print in Office applications without issue.
I have googled high and low, and the only solution I have found is to run a script that deletes all of the user's printer connections and logs them off. Then after logon they run another script that re-installs their printers. That usually remedies the problem for a period of time.