[freepms]

Does anyone have a working Lync 14.0.1 updater or a recipe for modifying it so it will work?

And, what does it take to get an InstallerChoices file to be honored?

[freepms]

Allister,

Could you post recipes for those two methods you mention? I’ve not been able to get an other-than-everything MS Office install in my 10.6.8 build…it’s ignoring InstallerChoices altogether, and my attempt just now at modifying the distribution.dist in an intuitive way succeeded in omitting the items I wanted omitted (Messenger and Communicator), but the rest of the apps are unlaunchable.

And if there’s a modification to the Lync 14.0.1 Updater known to get it to run that would help too…Lync is still 14.0.0 on the image, and I couldn’t find anything obvious in the updater package to cause that.

Thanks very much, and thanks again for last time!

[freepms]

Your 14.1.3 Updater worked for me. Thanks again!

This was on top of an SP1 Installer which I manually modified (preflight and postflight, $3’s added, launchctl lines commented).

All that’s left is to get it to honor the Installer Choices. I generated one to get it to omit installing Messenger, Communicator and RDC (for which I did a separate install), but they got installed anyway.

[freepms]

I dropped the SP1 Installer on that patcher, then checked the postflight. The $3’s have not been added nor the launchctl load line commented out.

[freepms]

That’s a big step, Goldberg, huge thanks!

Next question: which patcher, if any, can be successfully applied to the SP1 Installer?

[freepms]

Can’t say, because the SP1 Installer didn’t run at all. Apparently it really doesn’t like having the Communicator package remove. I tried again using the -f flag but that made no difference. Back to the drawing board.

That’s what I want, though: SP1 Installer minus Communicator, then 14.1.3 Updater. I hope there are lots of eyes on this.

[freepms]

For safety I just looked in my allegedly patched SP1 installer, and the postflight had not been modified! So I’m putting the mods into it by hand.

[freepms]

I just went digging into the 14.1.3 Update, and can’t find anything in there that says “licensing”. So I’m about to try a new InstaDMG build with the Office 2011 SP1 installer (patched by the Installer droplet, and then the Communicator package removed as I’m building for a Lync environment), followed by the unmodified 14.1.3 Updater (which doesn’t seem to include a Communicator package either). Wish me luck!

[freepms]

Two questions:

1) Does the patchOffice2011_1410Update_v041.dmg patcher (stated to work on the 14.1 and the 14.1.2 updaters) work on the 14.1.3 updater?

2) Has anyone yet dealt with the new MS Lync application (a replacement for Communicator), either manually or through a patch script? It’s only available through the VLSC site, I believe.

[freepms]

Extracted the packages from the dmg’s, and then then it ran to conclusion. Haven’t tested a restore with the resultant image yet but I have good confidence in it.

It’s possible I truly don’t get it about InstaUp2Date. But it seems to me that it imposes *extra* work. Instead of just downloading packages, putting them into the requisite folders and kicking off the build, I have to download the dmg’s, checksum them, add them to a catalog file, then throw them away and let InstaUp2Date re-download them.

Or is that just for stuff from Apple? And everything else goes into CustomPGK regardless of InstaUp2Date or not? Sorry to be a noob, but I’m a noob.

[freepms]

GRRRR. Spoke too soon.

It found the BaseOS, and wrote a cache image from it. But then:

09:59:19 ###### Beginning Update Installs from ./InstallerFiles/BaseUpdates ######
Working on folder 01 (09:59:19)
###### There were no items to install in: /Users/exadmin/instadmg/InstallerFiles/BaseUpdates/01 ######
09:59:19 ###### Cleaning up ######

…even though MacOSXUpdCombo10.6.8.dmg is sitting in that exact folder.

[freepms]

That nailed it.

I had done the reimage – svn – import sequence again and had run through some of the flags (-b and -I, with and without -f) to no effect. But renamed the imported image to “Mac OS X Install DVD.dmg” and it’s running.

Thanks for working through this with me!

[freepms]

Latest status:

Moved entire InstaDMG folder to a different box. No change.

Took that box outside the company firewall, svn’ed v.425. InstaDMG.bash still cannot find installer disk.

Rebooted. Trashed installer disk image, imported a fresh one. Rebooted. InstaDMG.bash still cannot find installer disk.

Ran InstaUp2Date.py 10.6_Vanilla –process (still outside the firewall). This succeeded. I don’t understand why InstaDMG will find the Base OS image when called by InstaUp2Date but not when run directly.

Took the resulting image and restored it to a partition of my original build box. Created fresh admin account. Everything from here down was done on this freshly-imaged partition.

Copied over the InstaDMG folder from the other box. InstaDMG.bash still cannot find installer disk.

Rebooted. Trashed installer disk image, imported a fresh one. Rebooted. InstaDMG.bash still cannot find installer disk.

Moved InstadDMG folder aside and svn’ed v.428. Trashed installer disk image, imported a fresh one. Rebooted. InstaDMG.bash still cannot find installer disk.

Ran InstaUp2Date.py 10.6_Vanilla –process (still outside the firewall). This succeeded (though process, and logs, say that it’s still v.425)

So as of v.428, on two different boxes, one freshly imaged, InstaDMG.bash still cannot find a Base OS image when run on its own, but when called by InstaUp2Date, it can.

Here are my donuts. I await your dollars. 😀

[freepms]

Sorry to be unclear. Still not working; I was just replying to your post asking me to svn -checkout the latest, which I did manage to do.

[freepms]

Today’s post: all steps done after taking computer outside company firewall and using svn to get 425.

Fully updated OS X 10.6.8, Python 2.3, 2.5 and 2.6.

I’ll see what I can do about IRC. Thanks!

[Author]

Posts