New iWork/iLife Updates (Mavericks)

[kempt]

How is everyone deploying the new updates to iLife and iWork? We've successfully deployed the suites on all of our user machines (after downloading it on our imaging machine using a department Apple ID), however the updates prompt for that Apple ID password, which we obviously aren't going to give out.

[cbrewer]

I've had success using this method to get the .pkg installer and then create a dummy receipt file to keep the apps from wanting to update/reinstall.

http://derflounder.wordpress.com/2013/10/19/downloading-microsofts-remote-desktop-installer-package-...

[kempt]

I used that, too. I got the installer, and once pushed to the user machine, it divorces the App from our department Apple ID and allows the user to input their own Apple ID and password. However, once they press "update", it tells them the app wasn't purchased with this Apple ID and cannot be updated using it. What is the dummy receipt your mentioned?

[bentoms]

We have run a weekly update, we advise our users that when an update for a company app comes out.. We'll update it accordingly.

We cache all required updates & install @ logout.

[jcarr]

Why wouldn't you use VPP Managed Distribution?

http://www.apple.com/business/vpp/

[bentoms]

For some of us VPP doesn't work: http://macmule.com/2014/01/23/vpp-2-0-a-question-of-morality/

[jcarr]

Ahh. Good point.

[kempt]

Still not sure how to approach this. We're new to Casper; I've seen mention on other posts about "doing it the standard Casper way", but I'm not even sure what that consists of.

[stevewood]

@kempt you basically use the same method to deploy updates that you do to deploy the actual apps. Using the method that @cbrewer pointed to (http://goo.gl/85uCCR), you drop the packages downloaded into Casper Admin and deploy them that way. When there are updates, rinse and repeat the process.

Scope the updates to machines that need them, etc. That's the "Casper Way" of deploying.

I have not tried it yet, but @athomson uploaded a script to JAMF Nation that is supposed to take the nitty gritty out of Rich's method (the link above). Test it, and if it works it might make things a lot easier.

[clifhirtle]

Mirrors similar steps I originally found over at Jon Brown's blog as well: http://www.jonbrown.org/10-9-deploying-appstore-packages/

So have we confirmed there is definitively no MAS app updaters available on vendor sites (i.e.: iPhoto 9.5.1 updater)? Alternatively, are newly shipping Macs including updated iLife/iWork from factory?

While I generally don't wipe-reimage Macs much anymore, in the past I've simple packaged apps off new Macs, then included any updaters in the Casper Imaging workflow.

[afej]

Newly shipped Macs have iLife & iWork included.

[Chris_Hafner]

Yea. I use Rich's method (linked above) but I do NOT create dummy receipts. I deploy them receipt-less and let the users authenticate those apps against their own appleIDs. It's annoying though, because it causes the app to be re-downloaded when the first update appears. In any event, yes I have my reasons for doing it this way and they are not shared by many of you.

That said, all I really want is to deploy these apps like Apple does on a new unit. I've got a small new fleet on it's way to me now and I'm hoping to have at a few of these 'virgin' systems.