HP Photosmart Premium Fax C410a driver Downloads for Microsoft. Sketchup for mac google. High Sierra, Macintosh OS X v10.8.x Mountain Lion, Mac OS X v10.9.x Mavericks, Mac OS. Hi All, I have an interesting issue that I'm hoping to have some input on. I have been doing just fine with our existing printer setup with drivers and such. We run a bunch of different models(school district) of HP. My issue is with the newest models. HP is no longer posting the drivers to do the installs and push them with Casper, instead they are posting some garbage application that identifies the printer and then puts the drivers where they need to be. I have tried a capture after doing this yet on a test machine it always shows up as a generic with a message that I need to install the manufacture software. Anyone have any insight to this? The printers we are using are the M452 and the M402 newest models. I noticed that Apple recently updated their HP driver package to version 5.0 (August 2016). I just released it on my SUS last week. But this new.pkg still doesnt contain drivers/PPDs for the fairly new HP M577 printer - which happens to be my company's default printer model, of course. Luckily, the older M575 driver/PPD (Which is available from Apple) seems to work OK. I can forsee a future AutoDMG-like project that 1) Downloads the latest version of HP's craptastic 'Easy Start' app, 2) Iniates a download of HPs drivers into $TMPDIR *, 3) captures them and 4) Bundles them into a.pkg. (*or skips HPs app altogather and downloads the drivers from HP's cloud repo). The HP Easy Start app is a joke. A sad sad pathetic little joke. I'm not looking forward to running/hacking the HP Easy Start app to poop-out a Mac PPD every time a new HP model gets deployed into production. Ain't got time for that! I submitted a support ticket with HP USA. Boy - That was a lot of fun. Took almost an hour to navigate thier vast sprawl of portals and sites and forms to submit a ticket. HP has no desire to talk to their customers. Pretty sure the HP support call center is located near Pyongyang, North Korea. The most recent (possibly final?) printer update from Apple/HP is the HP Printer Drivers v5.0 for OS X (dated: Aug 30, 2016): Ill report back if I hear anything from HP's USA support team. Another (more detailed) update from HP. • Apple has decided to discontinue printer driver update through Apple Software Updates. Vendors will now be required to supply their own install bundles to users. ASU support officially ended this month, but Apple has not been allowing new devices to be added for several months. • We did one last update to v.5 of the ASU bundle but did not add printers just fixes for macOS Sierra 3.This is the package for all the Postscript Printers only. The package from Apple included all HP Devices. If you need device specific installer let me know to try to braek down the install package for you. • Still need to find out about PPD´s, however our guess is that they are actually in the com.hp.print.ps.support packages embedded in the installer. The essentials package installs more components than the Apple installer because we include scan support and the HP Utility. This is the deployment method going forward for macOS. Deploying just the PPD is risky because we have other components that enable the advanced features of the printer and are exposed to the user by using the printer specific PPD. So that actually works or worked for people? I gave up on doing printers through Casper admin long ago because it never did point to the correct driver after capture.it was always generic. Once I learned how to configure through a command line statement I not only made deploying printers easier in that regard but it also allowed me to move to domain based printing from ipp and lpd. When I tried capturing through Casper admin and then would deploy it, the print jobs would hang. At any rate I'm now a proponent of doing printer installs with a simple one line script. No capturing necessary but, yes, I still need to install the pkg on the station so the driver is there. I don't remember when I started switching over but your process is the same as mine was. If I went into JSS and looked there, it would always be configured for generic. The printers worked and no one complained but in my environment some users would rather complain than report issues so I didn't like deploying them like that. Like I said though it helped move things along to run printing through our domain print servers so that printing could be audited. It worked out best this way in the end. Some day maybe I'll come back and check it out again. It might make it easier for the non-Mac folks if I'm not around. We supply an IP because that's what we've done in the past.
0 Comments
Leave a Reply. |