Sticky install for Office 2008 SP1 Update

[alantrewartha]

while running instaDMG, anybody else get the process stalling for a LOOOOoong time at the Office 2008 SP1 Update “Installing Standard SLTs…..”

sometimes it seems it will never recover, so i quit it, set off instaDMG again and it pushes through it in a few minutes. still pauses, just not for blimmin ever

seems very random

[edit: got it in the 12.1.1 update too just now ]

🙁

[Rusty Myers]

I would suggest re-packaging Office 2008 with it’s updates. It’s easier to push to upgrade older machines as well as the instaDMG build train. I’ve done it with success using JAMF Composer.

[alantrewartha]

Thanks, but i’m only repackaging where i really need to (CS3, Quark of course). The build train works OK, but you have to manually ctrl-C when each of the MS2008 updates (and it’s all of them at different times i see now) gets to the SLTs stage. and it’s not every time i do a build either :-/

i’ve got some time now, so i’m going to check the PKG scripts (postflight etc) to see what it might be

[Patrick Gallagher]

I frequently see status stuck on SLT too, but it’s always progressed eventually. I’ve never had to ctrl-c to get past it, and probably wouldn’t trust the install if I had to.

[alantrewartha]

what’s yr value of ‘eventually’? if i leave it really long, yes it does push through, but i’m talking hours! some times a whole working day i think 🙁

on the occasions where the install doesn’t stick it is the final thing that runs in the MPKG so i’ve just been digging around to see what might be stalling post-install. nothing so far.

the stuff being installed in these steps involves the SLT.bundle inside the setup assistant app – so I’m not that bothered by all of this – and i’m happy (so far!) that it’s not having an adverse affect on the installation of the main office apps

what’s bugging me (sorry for the repetition) is how inconsistent it is.

[Patrick Gallagher]

Eventually for me has been no more than 10 or 15 minutes on that one step. If yours is truly taking more than an hour, then yes, I would be concerned. Have you used the Office Patcher <[url]https://www.afp548.com/filemgmt/index.php?id=84&comments=1[/url]> on your Office updates?

[alantrewartha]

yes! that’s what makes this possible at all and i’m immensely thankful for it (my first post here was to give those thanks!)

Have you looked at the lsbom of those ‘SLT install’ PKGs? hardly anything there! it should take no time at all.

i’m going to try rearranging the build chain/train to see if it was an early install that made for a quicker SLT stage – it might be that the quicker installs happened before i got quark 7 and CS3 in on the act.

thank you everyone BTW

[samplem]

The install seems to be working a-ok for me, from versions 12.1.0 to 12.1.4. But after the compressed dmg has been created and deployed, I’ve been checking to see if the versions installed have been implemented and unfortunately none of the updates are applied when the application is launched. About Word reveals version 12.0.0, only. The pkgs are expanding, but not upgrading the app.

[alantrewartha]

now that does sound like you have yet to apply the Office Patcher – without which the MS installers don’t actually work, they just fail and instadmg carries on without them

[samplem]

My apologies, I forgot to mention that I did place the 2.1.1 updater first before the remaining pkg’s. I’ll need to run an isolation test to ensure the 2.1.1 take.

[alantrewartha]

but have you run the instaDMG PatchOfficeUpdate on the PKGs?

https://www.afp548.com/filemgmt/index.php?id=84&comments=1

[alantrewartha]

any progress samplem?

it might be coincidence but i’ve moved Office up the build chain (so there are a bunch of installers of lesser significance installing after instead of before it) and since then it’s pushed through in ~15 mins in the 12.1.1 (and then in no time in .2/.3/.4)

[Author]

Posts