iLife '11

Not applicable

Anyone got a copy of iLife 11 yet? Looks like all of the apps are
individually packaged now and not combined into a mpkg. It wouldn't be
too bad except that there's 20+ individual pkg files.

23 REPLIES 23

Not applicable

I am trying to create a pkg for iLife 11 and I have one that almost works.
However, iPhoto will not open. Everything else including iMovie works fine.
I've tried everything I can think of to no avail. Any idea?

Thanks,

Glenn J Burns
Computer Technician
Snyder ISD
325-574-8793
gburns at snyder.esc14.net
• Certified Mac Technician

Not applicable

I know this has been covered before, but I don't recall if anyone ever
found an answer (and I cannot find one in the mailing list archives).

We are trying to create a DMG of iLife '11 for deployment, and having
mixed luck. We can create a DMG and successfully deploy it to the latest
Apple hardware, however on anything older than about a year or so, iPhoto
in particular blows up with the spinning beachball of death. This is
regardless of what hardware the software DMG was created on (older
MacBook, or brand new MacBook Pro).

So aside from including iLife '11 in the base image, has anyone
successfully created a DMG for iLife '11 and deployed it?

Thanks,
Steve

--
Steven Diver
Network Manager // Adlai E. Stevenson High School
Email: sdiver at d125.org // Phone: 847.415.4304

This email and any files transmitted with it may contain confidential
information. It is intended solely for the addressee. If you are not the
intended recipient, you should not disclose, copy, distribute, or use any
of this information. If you received this communication in error, please
contact the sender immediately, delete this email from your system, and
destroy any material in hard copy form.

stevewood
Honored Contributor II
Honored Contributor II

I've had luck following the instructions that Craig Ernst laid out in his
post titled "iLife 11 - Option 2":

Hello All,

I started working on iLife 11 and I recall the threads early in December
going around and then that last one sent by Robert which basically had his
old school composer package method. At this point because our maintenance
agreement allows us to deploy iLife and iWork everywhere I've just added it
to my base OS package now. However, I still have some systems to update in
offices prior to doing that.

I have an alternative for anyone who would like it, and I somewhat prefer it
since it still utilizes the PKGs installing abilities.

Someone had mentioned that all the installers were PKGs on the DVD and that
triggered an idea, shocking I know.

  1. Create a folder at, or where you like: /private/var/tmp/iLife11_Install_Files/
  2. Dump all of the PKGs in there from the install DVD packages folder (so you don't have 20 PKGs to add to the JSS)
  3. Open Composer and drag the folder made into Composer
  4. Create a DMG of your PKGs and Upload it into Admin
  5. Create a script with the following that just runs after you've deployed the package, adjust your path if necessary based on step 1

#!/bin/sh

. /etc/rc.common

/usr/sbin/installer -pkg /private/var/tmp/iLife11_Install_Files/iLife.pkg
-target /

/bin/rm -rf /private/var/tmp/iLife11_Install_Files/

This of course assumes 10.6.3 or later. It was tested as a new install and
upgrading existing versions of iLife 08 andiLife 09 on the box. If you
wanted to have this install as a part of imaging you could have the DMG of
the install files copy over during imaging and just keep your script marked
as an At Reboot.

Cheers,

Craig E

tanderson
Contributor

This is how I am handling it as well.

Tom

Not applicable

Did you try the Composer Diff file I sent last week?

I suggest using the Diff file on a clean install as it does include items out of the Users home directory... incase you want to push that out to all users.

Expand the attached and install this into the directory
/Applications/Casper Suite/Composer.app/Contents/Support/NewPackageOptions/Software/iLife 11.composer

Open Composer and look for ilife11 in the preinstalled software section.


Not applicable

Awhile back, I sent a procedure to this list detailing how to make a pkg that should work in all circumstances. It basically involves putting all the packages in /tmp and using a postflight to run the install.

ToriAnneke
Contributor II

I package it the old skool way also….

Run composer.
Install iLife. Launch all apps and set prefs, splash screens, etc. as the first run.
Build the package in Composer …. I call it iLife11-rePack.dmg
Upload it to CasperAdmin ( <-- FEU FUT both true!!) and badda-bing!! It's deploys nicely and our internal SUS pushes all the updates after it reboots from imaging process.
iWork also!!

Been doing it like this since iLife 8… Also managed to get CS4 & 5 MC to deploy this way, as I've been doing it since CS3. Far easier than geeking around with Adobe Deployment methods.
:)

--
Pat Camporeale
"You don't need to be a mechanic to drive a car."

Jedberg
New Contributor III

Here is a 3rd way of deploying iLife '11:

Step 1. Create a .dmg of the disc put it in the /private/tmp directory,
then drag into composer.
Step 2. Add a postflight script with the contents below:
#!/bin/sh

## postflight

cd /private/tmp

hdiutil attach "iLife '11 Install DVD.dmg"

if (test $? = 0) then

date '+%A %m/%d/%Y %H:%M:%S iLife 11 Dmg mounted successfully.'

'/var/log/Casper Logs/iLife 11 Install.log'

else

date '+%A %m/%d/%Y %H:%M:%S iLife 11 failed to mount dmg.' >>

'/var/log/Casper Logs/iLife 11 Install.log'

fi

installer -pkg "/Volumes/iLife '11 Install
DVD/Installer/Packages/iLife.pkg" -target /

if (test $? = 0) then

date '+%A %m/%d/%Y %H:%M:%S iLife 11 was installed successfully.'

'/var/log/Casper Logs/iLife 11 Install.log'

else

date '+%A %m/%d/%Y %H:%M:%S iLife 11 failed to install.' >>

'/var/log/Casper Logs/iLife 11 Install.log'

fi

hdiutil eject "/Volumes/iLife '11 Install DVD"

exit 0

Step 3. Build .pkg to preserve the script. Upload and ready for
deployment.

Note: If any settings need to be made to the preferences for first run
etc. I scipt that as well to write any .plist files needed.

This process has worked great for us and I do it for several of our
packages and updates...
-- Jesse Edberg | UHG IT
Sr. Macintosh Engineer

k12techman
New Contributor

Anyone have a recommended method for creating an iLife '11 package for Self
Service installation? I've tried creating DMGs and PKGs neither of which
seem to make all of the applications functional when installed under Self
Service.

rob_potvin
Contributor III
Contributor III

There is a good how too in the deploy studio forum. I followed it and created in .mpkg that I now use with instaDMG and Casper. When I get back to the office tomorrow I can post what I did.

Cheers

Rob

rob_potvin
Contributor III
Contributor III

How to roll ilife 11 into an installable mpkg

http://s.sudre.free.fr/Software/Packages.html

Download Packages

Drag ilife packages in order into program packages

iLifeRegistration iLifeCookie AppleIntermediateCodec RAWCameraUpdate3 iLifeMediaBrowser iLifeSlideshow_v2 iLifeFaceRecognition iLifeAudioAnalysis iPhoto iPhotoContent iPhotoLibraryUpgradeTool ProAppRuntimeFlat iMovie iMovie_PreviousFolder (only drag this if there is a previous install of iLife)
iDVD GarageBand GarageBand_Instruments GarageBandFactoryContent GarageBand_LTPContent GarageBand_Loops GaregeBand_MagicContent iLifeSoundEffects_Loops iWeb iLifeRegistrationPost
Once everything is in Packages (the program) build it to an mpkg and you can install it with RDC, Deploystudio, instaDMG, and Casper. I have no issues with it, but I am using it with instaDMG

Cheers

Rob

iamkmc
New Contributor III

I used Pacifist to install is package individually, and composed each
separately.

Kevin Mc

*From: Rob Potvin [mailto:bisjamf at bis-school.com]
*Sent
: Saturday, November 05, 2011 10:26 AM
*To: Drew Lane <dlane at usd260.com>
*Cc
: casper at list.jamfsoftware.com <casper at list.jamfsoftware.com>
*Subject*: Re: [Casper] iLife '11

How to roll ilife 11 into an installable mpkg

http://s.sudre.free.fr/Software/Packages.html

Download Packages

Drag ilife packages in order into program packages

- iLifeRegistration - iLifeCookie - AppleIntermediateCodec - RAWCameraUpdate3 - iLifeMediaBrowser - iLifeSlideshow_v2 - iLifeFaceRecognition - iLifeAudioAnalysis - iPhoto - iPhotoContent - iPhotoLibraryUpgradeTool - ProAppRuntimeFlat - iMovie - iMovie_PreviousFolder *(only drag this if there is a previous install of iLife)* - iDVD - GarageBand - GarageBand_Instruments - GarageBandFactoryContent - GarageBand_LTPContent - GarageBand_Loops - GaregeBand_MagicContent - iLifeSoundEffects_Loops - iWeb - iLifeRegistrationPost

Once everything is in Packages (the program) build it to an mpkg and you
can install it with RDC, Deploystudio, instaDMG, and Casper. I have no
issues with it, but I am using it with instaDMG

Cheers

Rob

ToriAnneke
Contributor II

I do Composer for these apps:
CS3/4 and now 5 <--- I have a Core as the .dmg and the individual apps as pkgs (so I can bang them out with ARD as well if needed)
FinalCutStudio <--- similar to CS but I strip out the AudioLoops, LiveType, DVD Studio Content which slims down the wanted part of FCP to about 5.5 GB dmg.
iWork <-- this winds up as one dmg file
iLife <-- this winds up as one dmg file
![external image link](attachments/8ba055ed0e064692986a94e33583ffdc)

In this case of iLife, there are User objects made. So I build anything that installs objects in /Users as a .dmg in order to populate: FUT and FEU
Before I Build within Composer, I launch every app and set all preliminary defaults.

I can send the entire index as well so you can peek completely!
Lemme know!

PS: Apple SUS senses the install of iLife 11/iWork and FCP and delivers updates accordingly.

--
Pat Camporeale
"From now on I will be referred to as Mister Pastulio"
![external image link](attachments/06ffe09867ef4ec0b07545a1f9be1954)
Herengracht 258
1016BV Amsterdam

taugust04
Valued Contributor

I've been using this method for a while now for iLife '11 with good results, similar to Craig's towards the beginning of this thread:

1.) Create a folder in /private/tmp called ilife11
2.) Copy all the packages from the iLife '11 installer disk/dmg into this folder
3.) Drag this folder into Composer, in preparation of creating an installer.pkg from it
4.) Create a postflight script with the following command:

installer -pkg "$3/private/tmp/ilife11/iLife.pkg" -target LocalSystem

5.) Finalize the package.

The iLife.pkg package looks to the folder it's in to install all packages that are contained within it, regardless of whether it's on its original disk, .dmg, or a folder somewhere on your hard drive.

I've done several upgrades of iLife '08 and '09, along with clean installs, using this method, and I haven't had any problems yet. It's more reliable than most of the snapshotting methods, as it allows all the perl scripts that Apple includes in these installers that detect other hardware and software to run properly. The installer folder will get deleted at next boot when /tmp gets cleaned out.

Hope this helps,

-- Ted August
Salve Regina University

Not applicable

I do something similar and as you say it works reliably and is
On 18 November 2011 07:47, Ted August <taugust04.lists at gmail.com> wrote:
clean. Currently an *older* Mac licensed for iLife '11, which we have
purchased a Lion license for can use this method. ie. NetInstall 10.7.2
then install iLife '11 package, created as above, by policy. My concern is
when the next version of iLife is released, and what challenges that will
hold in store for us who have to manage enterprise deployments,
particularly in terms of updates.

Cheers,
Doug

rtrouton
Release Candidate Programs Tester

I'm doing something very similar, though I'm building it with Iceberg:

http://derflounder.wordpress.com/2011/08/07/repackaging-ilife-11-for-deploystudio/

The original deployment mechanism was DeployStudio, but it also works fine with Self Service.

Thanks,
Rich

rob_potvin
Contributor III
Contributor III

careful with this type of build because I have done the same but now have iMovie not showing its main window.

I am not sure if its a font problem or something to do with iLife but at the moment since doing a pkg build iMovie doesn't work with Lion and the new macbook airs. The same package work fine on 10.6.8

taugust04
Valued Contributor

My best guess is that the policy for the next versions of the iLife apps (iMovie, iPhoto, GarageBand - I'm pretty sure iDVD and iWeb are EOL), would be similar to the Final Cut Pro X recommendations for deployment:

http://support.apple.com/kb/HT4781

So you'll need a master computer/app store account that you use to redeem the volume license redemption codes and download the newest versions to, and then use it to package up and send to other computers with standard package deployment methods. Client computers will no longer receive those iLife updates via Software Update, so you'll have to push down your own packages each time the apps are updated in the App Store.

With Final Cut Pro X, the first time you launch it, it writes some receipts to /private/var/db/receipts that Software Update uses to pick up any additional downloads (such as codecs, media content) the next time it runs. Again, I would imagine the same could be done for anything extra needed for iLife to run.

Of course, you never know with Apple until it actually happens! :-D

--
Ted August
Salve Regina University

Not applicable

My best guess is that the policy for the next versions of the iLife apps

On 18 November 2011 09:34, Ted August <taugust04.lists at gmail.com> wrote: (iMovie, iPhoto, GarageBand - I'm pretty sure iDVD and iWeb are EOL), would be similar to the Final Cut Pro X recommendations for deployment:

That was my assumption too.

With Final Cut Pro X, the first time you launch it, it writes some receipts

to /private/var/db/receipts that Software Update uses to pick up any additional downloads (such as codecs, media content) the next time it runs. Again, I would imagine the same could be done for anything extra needed for iLife to run.

We will be purchasing bulk licenses (>20) of Final Cut X in the new year
and will need to package it for mass deployment. Given what you've said
about the need to run it prior to software update, could you have a look
for me to see the way that process is implemented? Is there a nice little
script in the Final Cut Pro X.app folder which could be called from a
package postflight script? Could we *easily* write receipts manually to
emulate this process? Or, maybe do something like this in a postflight
script:
open /Applications/Final Cut Pro X
sleep 20
kill-all 'Final Cut ...
softwareupdate -ia

Another option may be to capture the changes Final Cut Pro X makes when it
first runs and when software update installs things, and put that in a
package along with the Final Cut Pro X application.

Has anyone implemented any of these alternatives, or another method with
success?

Cheers,
Doug

taugust04
Valued Contributor

Hi Doug,

Actually, the receipts are generated by Apple Software Update automatically. I just deployed Final Cut Pro X today to a computer without opening it, and noticed that the additional packages and content were installed without any intervention. It must be doing a scan for the presence of Final Cut Pro X somewhere in the Applications folder.

Thanks,

-- Ted August
Salve Regina University

Not applicable

Actually, the receipts are generated by Apple Software Update

On 2 December 2011 08:23, Ted August <taugust04.lists at gmail.com> wrote: automatically. I just deployed Final Cut Pro X today to a computer without opening it, and noticed that the additional packages and content were installed without any intervention. It must be doing a scan for the presence of Final Cut Pro X somewhere in the Applications folder.

Excellent, that's great news.

Thanks,
Doug

k12techman
New Contributor

If I understand this correctly (big IF), Final Cut X can be installed using
Casper by doing this?

  1. Begin a snapshot of your master system using Composer.
  2. Use the App store as described in the KB to actually get the app such as Final Cut X on your "master" computer.
  3. Run the app one time and set defaults, write receipts, etc.
  4. Finish your snapshot and package the results.
  5. Deploy to other Macs using Casper.

Is that about the sum total of it all? Did I miss something?

Drew

taugust04
Valued Contributor

That should work, though I haven't tried it. Another option, if you run a local Apple SUS at your site, is to extract the extra packages from the ASUS server, and deploy them along with Final Cut Pro X in a policy, and avoid snapshotting entirely.

-- Ted August
Salve Regina University