[pepijn]

I have successfully integrated the MSM 1.0 install packages, albeit into my DeployStudio workflows and not InstaDMG directly, but using a vanilla 10.6 InstaDMG build. I am using an ePO server for our deployments so to install the CMA component I grabbed the “install.sh” off the server since it includes the appropriate cma config for our ePO environment. I wrapped the “install.sh” executable script in a pkg and fire it off in the postflight script with “./install.sh -i”. The main MSM Malware mpkg gets set to install at first boot where it picks up on the existing CMA install and drops in the other moving bits, after which everything registers with the ePO server within a few minutes. I have not had any issues with this method.

HTH,

Pepijn.

[pepijn]

FWIW, and two and a half years later, instead of running the changesecret script like this:

[code]changesecret $(defaults read /Library/Preferences/DirectoryService/ActiveDirectory “AD Computer Password” | /usr/bin/tr -d “< >” | /usr/bin/xxd -r -p)[/code]

which causes it to ingest an empty string and thus to effectively replace the hash in /var/db/samba/secrets.tdb with a null \00, running it like this:

[code]sudo changesecret `sudo defaults read /Library/Preferences/DirectoryService/ActiveDirectory “AD Computer Password” | /usr/bin/tr -d “< >” | /usr/bin/xxd -r -p)`[/code]

will properly pass the required pw hash to the script, append its \00 and exit. It’s a bit dirty with the double, embedded sudo but that did the trick for me and I wasn’t going to spend more time pretty-fying it further. 😉 Hope it helps someone searching the forum for a solution.

Pepijn.

[pepijn]

I went with doing full installs of CS3 and CS4 on my build box and building a pkg with Composer 7. The standard template creates separate “All installed CS4 apps” and “Adobe PCD” packages. Neither seem to include the required FLEXnet files though, so I’ll add it manually and see what gives. Not looking forward to having to do complete installs of all CS3/CS4 Design/Web Standard/Premium apps plus any other standalone ones like After Effects… thanks Adobe, keep working on the deployment-friendly installers.

Pepijn.

[pepijn]

FWIW, I created a single installer from the complete disc set which comes in at a monstrous 48 GB but it does install just fine. There isn’t that much to it, just a matter of substituting the x-disc:// stuff with the path to a local common Packages folder in two files, FinalCutStudio.dist in FinalCutStudio.mpkg and AudioContentForSoundtrackPro.dist in AudioContentForSoundtrackPro.mpkg. I created a DMG of the whole thing to allow for a network install but it would be just as simple to store the entire Packages folder inside the FinalCutStudio.mpkg package and repointing the appropriate paths in the .dist files to it. I’ll probably try that route and do a package deploy as part of a DeployStudio workflow… 48 GB for a full install ought to be a fun exercise 😀

Pepijn.

[pepijn]

I recently passed the ACTC exam with just the book and a spare server to tinker with, it was not that hard to get through. I didn’t have a lot of options as far as taking the classes as no local AATC offers the IT classes, only the Pro Apps. I am currently working with the ACSA-specific books the same way and hopefully I’ll be able to take the three remaining ones (Directory Services, Deployment, Advanced Sys Admin) in the coming months.

HTH,

Pepijn.

[pepijn]

This method actually let me tackle an unwilling vanilla 10.5.0 installer that would not let me nix the language translations using the “old” format. Even using multiple entries for them, in just about every permutation possible and the output of showChoicesAfterApplyingChangesXML happily showing me no language were to be installed, *promise*, it still insisted on installing them all come InstaDMG build time.

After a quick conversion from the “old” format to this one (thank you Textmate) and making sure to triple up on the negativity (selected, enabled, visible) the InstallerChoices.xml file now works out the way I want it to, skipping language translations and their fonts (as well as a few other minor items). So thank you for figuring this one out, I’m very much looking forward to wrapping some kind of GUI around the whole InstallerChoices.xml-creation process but I hadn’t started yet due to the seemingly unreliable outcome in the past. This might work better.

Pepijn.

[pepijn]

After trying to make Leopard’s PM work and failing, I have switched back to using the previous version 2.1.1 which works fine with Leopard. It seems like the version bundled with Xcode 3.x needs some work still.

p.

[pepijn]

I guess that explains it then, one more self-contained update to switch to a pkg-based model. As mentioned, there’s tools available to wrap up the contents of this last pre-PKG updater into its own .pkg for inclusion in the InstaDMG build train, in my case I’ll probably use the logGen/pkgGen/Packagemaker trifecta.

Cheers,

Pepijn

[pepijn]

Just to second that, the download link for AutoUpdate 2.1.1 on the MS site results in a DMG containing an Installer Vise installer which is a self-contained application, not an Apple Installer-compatible .pkg file. Confusing moreso because the 12.0.1 updater is a proper Apple .mpkg file. 😕

Anyone else know of an alternative link/method to obtain an InstaDMG-friendly .pkg for this one (besides the more laborious pkgGen method)?

Cheers,

Pepijn.

[Author]

Posts