Updating App Store iLife apps

jhuhmann
Contributor

I've searched extensively but I can't find an answer. iLife was updated on our computers before I made the image and distributed it. When teachers attempt to update the iLife suite they can't because they don't own iLife. They can't take ownership of it because they don't in fact own it, the school district does.

I tried updating it using the most recent package downloaded from Apple's site, but they won't permit it to install because it can "only update through the mac app store".

Is there any way to update iLife without essentially giving the program to teachers? It would also be great to update it on student computers, which don't have app store access. Is there any way to create or get a package that will update it outside the app store?

1 ACCEPTED SOLUTION

ernstcs
Contributor III

Mountain Lion is forcing this to happen now, I use to bake iLife into my main OS image along with iWork, but the installer now fails on ML. If you have purchased Apple Maintenance or Apple Education Licensing Program options you should be able to get them from the Mac App Store and then just package up the iMovie, iPhoto, and Garageband apps and push them out.

Unfortunately you'll need to always maintain versions through the JSS at that point since the Mac App Store, nor software update (as I understand it), won't see them to get updates. You'll just have to keep pushing out updated version as needed.

Garageband can be packed into two separate bits if you like. Don't launch the app and just package the Garageband app bundle, then do a standard composer package, launch Garageband so it installs the huge content install, and then make that package. I'm going to keep them separate so I don't have to keep pushing a huge package for a Garageband update.

View solution in original post

9 REPLIES 9

frozenarse
Contributor II

How did you install iLife in the image you deployed?

How are you trying to deploy the newest version?

I just used composer to make a DMG of the latest app and push that out.

ernstcs
Contributor III

Mountain Lion is forcing this to happen now, I use to bake iLife into my main OS image along with iWork, but the installer now fails on ML. If you have purchased Apple Maintenance or Apple Education Licensing Program options you should be able to get them from the Mac App Store and then just package up the iMovie, iPhoto, and Garageband apps and push them out.

Unfortunately you'll need to always maintain versions through the JSS at that point since the Mac App Store, nor software update (as I understand it), won't see them to get updates. You'll just have to keep pushing out updated version as needed.

Garageband can be packed into two separate bits if you like. Don't launch the app and just package the Garageband app bundle, then do a standard composer package, launch Garageband so it installs the huge content install, and then make that package. I'm going to keep them separate so I don't have to keep pushing a huge package for a Garageband update.

jhuhmann
Contributor
How did you install iLife in the image you deployed?

It was preinstalled on our new computers so I ran updates and then made the image. Evidently not a wise move on my part.

I'll try updating it on a local system, making a package from that, and pushing it out. if that doesn't work, which it sounds like it wont, I guess I'm down to not having it in the base image and installing it as a package. ugh. I hate the app store.

Thanks for the comments.

frozenarse
Contributor II

I should have mentioned that i'm dealing with Lion clients. Sounds like things are different in Mtn Lion country.

ernstcs
Contributor III

I was using an iLife install DVD up through Lion. And yes, ML turns the screws even tighter in forcing you to all the Mac App Store. Don't even get me started.

aaronk
New Contributor

I am able to install iLife from DVD on Mountain Lion and Software update finds and updates it just fine

ernstcs
Contributor III

Perhaps you have a newer version disc than I do?

arekdreyer
Contributor

Read this the Apple Software Volume Licensing page at http://www.apple.com/mac/volume-licensing/ very carefully.

Scroll down past the information about Lion and Mountain Lion to:

Downloading and deploying Apple software. If you purchase volume licenses for Apple software, you’ll receive one redemption code per license. You can use one of two methods to install the software on your licensed number of Mac systems: Redeem from the Mac App Store. On each target Mac, open the Mac App Store and sign in with the Apple ID and password provided by your organization. In the Quick Links section, click Redeem. Enter the redemption code when prompted. The application will download and install in the Applications folder. Software updates for these Mac systems will be provided automatically through the Mac App Store. Use Apple Remote Desktop, NetInstall, or NetRestore. On your administrator Mac system, enter one of the redemption codes provided. You can then copy the application to all the target systems using Apple Remote Desktop. Or you can use the System Image Utility included in OS X Server to create a NetInstall or NetRestore image. Software Updates for OS X Mountain Lion will be provided through the Mac App Store.

I might assume that instead of NetInstall or NetRestore, you could use Casper Imaging.

I don't understand why the method of distributing a single redeemed app doesn't include this sentence:

Software updates for these Mac systems will be provided automatically through the Mac App Store.

I was confused by the last sentence (Software Updates for OS X Mountain Lion...) but then I realized this simply applies for all scenarios.

mpermann
Valued Contributor II

Won't applying updates to apps installed from the App Store require that you put in the credentials used to originally download the app? We ran into a situation where I downloaded the Lion installer using my credentials and that installer was used to install lion on some other computers. When the user was notified of an update to the OS in the App Store he tried to download the update from the store and was presented with a login screen that already had my username filled in and it was wanting my password for my account since I had downloaded the installer with my account. Since the Lion installer is the only app that we have to date purchased from the App Store I am wondering if this same behavior is what we can expect when we begin purchasing more software from the App Store. What are others out there experiencing?