[mgb123]

The patches don’t seem to alter the 14.1.3, and 14.1.4 packages correctly – they seem to error out when the image is built – with an error in the preinstall script Outlook2011_all_quit.14.1.4.combo.pkg.

I’ve taken the script from a patched 14.1.2 and use it in place of the scripts that are there by default, AND the version that is created when 14.1.3/4 are patched. This seems to result in the App successfully installing.

I’m on 10.7.3 – so perhaps the OS changes something relative to the scripts, as the previous poster mentioned that 14.1.4 is patchable for him on 10.7.2

Thoughts?

[mgb123]

[QUOTE][u]Quote by: mgb123[/u][p]Thanks Allister –

So I just repackaged the scripts – along with the postinstall script with Composer (figured, I might as well take my own stupidity out of the equation) and then installed manually into a firstboot-free new image. On a reboot – seems as though everything went as expected. Seems to indicate that I fudged up the first boot pkg at some point. I’m guessing that I must have fiddled with the pkg and just not remembered it.

I’m baking out a new image currently – will post results once re-imaged.

[/p][/QUOTE]

All is well – script worked out A-OK. Issue was somewhere between the keyboard and seat.

[mgb123]

Thanks Allister –

So I just repackaged the scripts – along with the postinstall script with Composer (figured, I might as well take my own stupidity out of the equation) and then installed manually into a firstboot-free new image. On a reboot – seems as though everything went as expected. Seems to indicate that I fudged up the first boot pkg at some point. I’m guessing that I must have fiddled with the pkg and just not remembered it.

I’m baking out a new image currently – will post results once re-imaged.

[mgb123]

That much I’d figured out – but as far as how to actually use PlistBuddy – I’m suuuuuper ignorant. (Like, silly sad puppy dog eyes ignorant.) I’ve been searching for tutorials, but I’m coming up a little dry in terms of something I can actually wrap my head around…

[mgb123]

Thank you sir. 🙂

[mgb123]

Totally does make sense- though I’m fuzzy about the way to ensure that I include all the necessary catalog files. Say I have 3 catalogs, and a vanilla, would I just make a base, and then just put in the top

include-file: 10.6_vanilla.catalog
include-file: (Catalog to install 1st after vanilla)
include-file: (Catalog to install 2nd after vanilla)
include-file: (Catalog to install 3nd after vanilla)

Would this be correct?

[mgb123]

So if I need to create multiple purpose built images, the best way to do so is to create multiple Base.catalog files, and then add or remove specific customizations as I see fit?

I was doing a much less elegant call file 1, which calls file 2, which calls file 3, which calls file 4 sort of setup. Made it cumbersome to decide the order of things.

So what’s the best way to organize the Base catalog? Just call things in order, Vanilla, then common, then (exploded) iLife 11, iLife updates, then regular app load?

Do I need to do any fancy footwork with regards to calling the installer disc in the Base catalog?

[mgb123]

Nate,
The restart command you posted works perfectly. Thanks!

[mgb123]

Nate,

We’re looking into DeployStudio, or JAMF, but right now it’s a good ‘ole firewire drive.

Understood on the permissions warning. In this case, it’s a command line install that lives on a disk image that will be plopped down on disk via a package. Not the most elegant thing in the world. 😉

[mgb123]

Can those defaults be set in a preboot script, of are they only available post boot?

[mgb123]

[url]http://pastebin.com/embed_js.php?i=pkfvFnrw[/url]

[mgb123]

Genius. I’m a dumbass.

[mgb123]

Nate,

thanks very much. I’ll post the script shortly. I do have a number of installs in there that seem to drag on forever – that’s the issue with post boot installs taking place in the background- I have no idea when they’re done.

I’m wondering if I should also be looking for some sort of way to indicate when installs have completed in the background, like a popup or something similar…

[mgb123]

Allister- I ran through the edits listed on OXDep but wasn’t sure how to incorporate the result into my build.

Looks like I’m left with a revised iLife.pkg, and a subfolder full of additional packages. Should I drop them all in my build? Should I put them into another catalog file? I’m just unsure exactly of what the iLife pkg edits did for me, and unsure how to incorporate those packages from the install disc into my build- manually or otherwise…

[mgb123]

I’ve attempted to drop the ‘Office Installer’ file from the original install media onto the patcher.

I only see it for a second or so in my Dock and then it disappears. Is this the expected behavior?

[Author]

Posts