While on the outside, it would appear nice that Adobe now provides an Apple Installer, the truth is it's just a wrapper for some proprietary installer by some loser company called iNOSSO.

Indeed, the installer doesn't work when deployed through Apple Remote Desktop - it needs to be run locally via the GUI, which is unacceptable for large-scale deployments. Or even small ones for that matter. What is the point in making it "look" like a pkg, when it really isn't and doesn't work like one?

Additionally, the installation is incomplete. Even after running it "properly" (using its own version of the word "properly"), starting up Adobe Reader results in an admin password request to install something for Safari. Why on earth did the installer not do that in the first place? Not only does the installer apparently require interactive operation to install, afterwards you also need to interactively, one at a time, authenticate to finish what the installer didn't do the first time around.

This is poor. Very very poor. I realize many ppl will wonder what the big deal is, but if you were expected to deploy software to 2000 workstations, you'd be annoyed about this too.

So, now I have to deconstruct what actually gets installed, and build my own installer that works correctly. Because Adobe couldn't do that themselves. I don't know who comes up with your installers, but they need to be removed from the human gene pool. And I haven't even got to the program itself. Not looking good at all...

Adobe, you're seriously pathetic. I've already been laying the groundwork for discontinuing use of your Acrobat products, since you refuse to make a version of Acrobat Standard for Mac (we are site licensed for "Standard", but this is now worthless to our Mac users), so hopefully we should be able to run both Acrobat and Reader out of our network on a big fat rail.