Apple updates and update order

[Patrick Fergus]

[QUOTE][u]Quote by: patgmac[/u][p]
> Apple updates run before custom. iLife updates should be put into Apple updates. The current
> version of InstaDMG can install them fine even though it’s not the boot volume. [/p][/QUOTE]

There’s a special case for the Apple iLife Support 8.2. It can’t run on a non-boot volume as-is because of a scripting error inside the pkg. There’s posts on the forum for modifying the scripts to make it work correctly, or it can be installed at first startup of a freshly imaged machine.

– Patrick

[dano]

I’ve installed iLife as the first AppleUpdate using the original iLife package. Testing is on a MacBook Pro as my build machine for setting up my build workflow. Everything worked fine. Try this AppleUpdates order:

/{path to InstaDMG folder}/AppleUpdates/00/iLife ’08.mpkg
/{path to InstaDMG folder}/AppleUpdates/01/RemoteDesktopClient.pkg
/{path to InstaDMG folder}/AppleUpdates/02/iDVD_701.pkg
/{path to InstaDMG folder}/AppleUpdates/03/iMovie_710.pkg
/{path to InstaDMG folder}/AppleUpdates/04/iPhoto_710.pkg
/{path to InstaDMG folder}/AppleUpdates/05/GarageBand_411.pkg
/{path to InstaDMG folder}/AppleUpdates/06/iLifeSupport.mpkg
/{path to InstaDMG folder}/AppleUpdates/07/iWeb_203.pkg
/{path to InstaDMG folder}/AppleUpdates/08/QuickTime745_Leopard.pkg
/{path to InstaDMG folder}/AppleUpdates/09/iTunes.mpkg
/{path to InstaDMG folder}/AppleUpdates/10/AirPortUtility_Leopard.pkg
/{path to InstaDMG folder}/AppleUpdates/11/FrontRowUpdate2.1.3.pkg
/{path to InstaDMG folder}/AppleUpdates/12/MacOSXUpdCombo10.5.2.pkg
/{path to InstaDMG folder}/AppleUpdates/13/iMovie_711.pkg
/{path to InstaDMG folder}/AppleUpdates/14/GarageBand_412.pkg
/{path to InstaDMG folder}/AppleUpdates/15/iPhoto_712.pkg
/{path to InstaDMG folder}/AppleUpdates/16/LeopardGraphicsUpdate1.0.pkg
/{path to InstaDMG folder}/AppleUpdates/17/Time-Machine-Update.pkg
/{path to InstaDMG folder}/AppleUpdates/18/SecUpd2008-002.pkg
/{path to InstaDMG folder}/AppleUpdates/19/Safari311UpdLeo.pkg
/{path to InstaDMG folder}/AppleUpdates/20/iPhoto_713.pkg
/{path to InstaDMG folder}/AppleUpdates/21/RAWCamera.pkg

Note: Two packages needs “hacking” before they can inserted into the AppleUpdates chain. Details as follows:

iLifeSupport.mpkg (without this iLife apps won’t launch due to inability to find necessary app frameworks/libraries)
1. Open file – iLifeSupport.mpkg/Contents/Installers/iLifeMediaBrowser.pkg/Contents/Resources/postflight_actions/repairLeopardLinks
2. On lines 25 and 30, immediately following the equal sign, remove “$TargetDisk . ” ($TargetDisk – space – dot -space)
3. Save file

iTunes.mpkg (scratch disk image won’t dismount due to postflight action which launches iTunesHelper app)
delete – iTunes.mpkg/Contents/Resources/iTunesX.pkg/Contents/Resources/postflight_actions/runiTunesHelper

[dano]

I should add that I’m moving to Leopard and all my testing is on Leopard exclusively.

[Rusty Myers]

[QUOTE][u]Quote by: dano[/u][p]

/{path to InstaDMG folder}/AppleUpdates/16/LeopardGraphicsUpdate1.0.pkg
[/p][/QUOTE]

I’ve heard of some issues with Office 2008 and the Leopard Graphics update, I have done everything but this until that is fixed. Just my FYI!

[dano]

One more comment. I would install all Apple applications (Aperture, iLife, iWork etc) that are part of your base image into the AppleUpdates directory first. Make sure they are first in the order of install. Then install all applicable updates. If you are installing an Apple application that is not installed on all your workstations, I would place it in the CustomPKG folder and then add all the applicable AppleUpdates in the CustomPKG folder as well.

One other option would be to install the Apple application and applicable updates separately as part of your deployment process. In other words you would install your base image and then install separate packages comprised of this application and applicable updates after the image has been restored.

Of course, there are lots of ways to do this and ultimately it’s up to you!

[dano]

Thanks Spider….I’m just in the process of figuring out how to install user accounts. I haven’t gotten to Office yet but will keep this in mind when I get to Office.

[ewhite]

dano: Thanks for both the updates order & package hacks…

One question: When I image a machine with just 10.5 or 10.5.2 I haven’t been getting the GarageBand, iPhoto, iMovie, iDVD, etc updates pushed down to the computer (a PowerBook G4). Do you think it’s my hardware or did you choose to add those updates for another reason?

Edit: I just had a “duh” moment … I’m using Mac OS X Install DVD, so those parts of iLife aren’t included…

[dano]

better get to that coffee quick…. 😀

[ewhite]

After successfully creating an ASR image using an original Mac OS X Install DVD (Leopard), and InstallerChoices.xml file, the createuser.pkg and clearReg.pkg — I wanted to start applying Apple Updates.

So I
# Imaged my test machine (a PowerBook G4) with the working ASR (just 10.5.0, with no updates) and
# Ran Software Update on fresh image until there were none left
# Looked at the Software Update log and made notes on update order
# Downloaded updates from Apple
# (Performed tweaks on iLife and iTunes packages as specified by dano above)
# Put them into folders in Instadmg/AppleUpdates/ according to order noted below:

08-04-30
14:01:30
Beginning Installation from /Volumes/Mac OS X Install DVD
08-04-30
14:14:33
Beginning Update Installs from ./AppleUpdates
Installed ./AppleUpdates/01/AirPortUtility_Leopard.pkg
Installed ./AppleUpdates/02/RemoteDesktopClient.pkg
Installed ./AppleUpdates/03/iLifeSupport.mpkg
Installed ./AppleUpdates/04/QuickTime745_Leopard.pkg
Installed ./AppleUpdates/05/iTunes.mpkg
Installed ./AppleUpdates/06/MacOSXUpdCombo10.5.2.pkg
Installed ./AppleUpdates/07/FrontRowUpdate2.1.3.pkg
Installed ./AppleUpdates/08/Time-Machine-Update.pkg
Installed ./AppleUpdates/09/LeopardGraphicsUpdate1.0.pkg
Installed ./AppleUpdates/10/SecUpd2008-002Univ.pkg
Installed ./AppleUpdates/11/Safari311UpdLeo.pkg
08-04-30
14:21:06
Beginning Update Installs from ./CustomPKG
Installed ./CustomPKG/1/createUser.pkg
Installed ./CustomPKG/2/clearReg.pkg

I’m finding that the update order isn’t that sensitive, but that the Security Update 2008-002 seems to break my image every time (machine doesn’t boot after being imaged — stops at spinning gear & silver apple). When I used the exact same setup as above, but with folder 10 empty (so no SecUpd2008-002Univ.pkg), it boots fine and asks for the Security Update.

So, is anyone else having this problem or see where the problem might be?

[dano]

First….the disclaimer….I have no idea what’s going on.

If I were attemtpting to remedy this, the first thing I would try is to remove the user account setup packages. Then generate an InstaDMG image and restore to your test volume. Boot the newly restored volume and see if you can successfully boot your image (after manually generating your first user account). If you are successfull then it might be some sort of issue with your user account generation packages.

Second option would be to try generating your InstaDMG image on an Intel Mac if you have one available.

[ewhite]

Dano — Thanks for the ideas.

I wasn’t totally clear on how I’m doing this — I was building on an external drive connected to a MacBook Pro and testing on the PowerBook G4 — now I’m building on a drive connected to a MBP and testing on the same MBP.

Currently building an InstaDMG with all updates and no createUser.pkg or clearReg.pkg…

[dano]

An image generated on Intel hardware probably is not compatible with PowerPC hardware or vice versa. What this means is you should:

1. Deploy images built on Intel hardware to Intel hardware only.
2. Deploy images built on PowerPC hardware to PowerPC hardware only.

Note: There was some rumors that Apple was going to unify the partition mapping between PowerPC and Intel. Not sure if it happened. It’s safer to assume that Intel images won’t work on PowerPC hardware and vice versa. This is definitely the case under Tiger and I suspect the same applies to Leopard.

[Rusty Myers]

[QUOTE][u]Quote by: dano[/u][p]An image generated on Intel hardware probably is not compatible with PowerPC hardware or vice versa. What this means is you should:

1. Deploy images built on Intel hardware to Intel hardware only.
2. Deploy images built on PowerPC hardware to PowerPC hardware only.

Note: There was some rumors that Apple was going to unify the partition mapping between PowerPC and Intel. Not sure if it happened. It’s safer to assume that Intel images won’t work on PowerPC hardware and vice versa. This is definitely the case under Tiger and I suspect the same applies to Leopard.[/p][/QUOTE]

Hey guys,

I’ve been building all y images (leopard only) on a G5 xServe and it has been booting a macbook pro fine. The only thing that doesn’t work is DVD player. At least that’s all I’ve found. Here’s my order:

08-04-29
10:07:46
Beginning Installation from /Volumes/Mac OS X Install DVD
08-04-29
11:41:36
Beginning Update Installs from ./AppleUpdates
Installed ./AppleUpdates/01/MacOSXUpdCombo10.5.2.pkg
Installed ./AppleUpdates/02/Safari31UpdLeo.pkg
Installed ./AppleUpdates/03/
Installed ./AppleUpdates/04/Time-Machine-Update.pkg
Installed ./AppleUpdates/05/SecUpd2008-002.pkg
Installed ./AppleUpdates/06/QuickTime745_Leopard.pkg
Installed ./AppleUpdates/07/iLife ’08.mpkg
Installed ./AppleUpdates/08/iTunes.mpkg
Installed ./AppleUpdates/09/AirPortUtility_Leopard.pkg
Installed ./AppleUpdates/10/FrontRowUpdate2.1.3.pkg
Installed ./AppleUpdates/11/Safari311UpdLeo.pkg
Installed ./AppleUpdates/12/iDVD_701.pkg
Installed ./AppleUpdates/13/iPhoto_712.pkg
Installed ./AppleUpdates/14/iPhoto_713.pkg
Installed ./AppleUpdates/15/GarageBand_412.pkg
Installed ./AppleUpdates/16/iWeb_203.pkg
Installed ./AppleUpdates/17/iLifeSupport.mpkg
Installed ./AppleUpdates/18/RAWCamera.pkg
08-04-29
12:32:14
Beginning Update Installs from ./CustomPKG
Installed ./CustomPKG/01/createUser.pkg
Installed ./CustomPKG/02/Office Installer.mpkg
Installed ./CustomPKG/03/ARD Kickstart.pkg
Installed ./CustomPKG/04/Kidspiration 2.1.pkg
Installed ./CustomPKG/05/Firefox.pkg
Installed ./CustomPKG/06/Adobe Reader.pkg
Installed ./CustomPKG/07/VPN.pkg
Installed ./CustomPKG/08/Inspiration 8.pkg
Installed ./CustomPKG/09/Studiocode.pkg
Installed ./CustomPKG/10/
Installed ./CustomPKG/11/Office 2008 for Mac 12.0.1 Update.mpkg
Installed ./CustomPKG/12/TextWrangler.pkg
Installed ./CustomPKG/13/OfficeAutoUpdate2.1.1.pkg
Installed ./CustomPKG/14/iMovieHD6.pkg
Installed ./CustomPKG/15/clearReg.pkg
Installed ./CustomPKG/16/Office SetupInfo.pkg

[Patrick Fergus]

[QUOTE][u]Quote by: dano[/u]

> An image generated on Intel hardware probably is not compatible with
> PowerPC hardware or vice versa. What this means is you should:
>
> 1. Deploy images built on Intel hardware to Intel hardware only.
> 2. Deploy images built on PowerPC hardware to PowerPC hardware only.
>
>
> Note: There was some rumors that Apple was going to unify the partition
> mapping between PowerPC and Intel. Not sure if it happened. It’s safer
> to assume that Intel images won’t work on PowerPC hardware and vice
> versa. This is definitely the case under Tiger and I suspect the same
> applies to Leopard.[/QUOTE]

You can use the same Leopard build on a PPC or Intel Mac. In Tiger, you had to manage both PPC and Intel images, but the same bits that run Leopard on one processor architecture run it on the other. Apple Software Restore (ASR)/Disk Utility/NetRestore will use the hard drive partition scheme already on the drive, so your out-of-the-box Mac Pro with a GUID partition scheme will remain GUID, and a G5 will remain APM.

Regarding new internal drives–since I’ve never had a problem with the partition scheme, I have to imagine that OS X uses GUID by default on Intel Macs and APM on PPC Macs. New [i]external[/i] drives appear to be APM by default to retain compatibility with older versions of OS X.

– Patrick

[Patrick Fergus]

[QUOTE][u]Quote by: thespider[/u]
> I’ve been building all y images (leopard only) on a G5 xServe
> and it has been booting a macbook pro fine. The only thing that
> doesn’t work is DVD player.
[/QUOTE]

This has to do with whether the build machine is capable of playing DVDs–something about DVD licensing requirements. I know I had a G3 iMac with an CD drive that went funky, and when I replaced the CD drive with a DVD drive and reinstalled OS X, the DVD software appeared without any conscious effort.

– Patrick

[Author]

Posts