[Greg Neagle]

Use nested computer groups so you don’t have to duplicate things.

[Greg Neagle]

[QUOTE][u]Quote by: andyboutte[/u][p]So I fixed my symlink and now my link looks like this:

lrwxr-xr-x 1 andyboutte staff 30 Feb 2 23:43 iLife.pkg -> ./Installer/Packages/iLife.pkg

but I now get this error in the instadmg logs:

Install failed: The Installer can’t locate the data it needs to install the software. Check your install media or Internet connection and try again, or contact the software manufacturer for assistance.

and to test to make sure my ilife dmg was working I ran this which worked fine:

sudo installer -pkg “/Volumes/ilife11/Installer/Packages/iLife.pkg” -verbose -target “/Volumes/Macintosh HD”
[/QUOTE]

Does this work, though?

sudo installer -pkg “/Volumes/ilife11/iLife.pkg” -verbose -target “/Volumes/Macintosh HD”

If not, your symlink is still broken. You could just double-click on the symlink and see if it opens the iLife 11 installer as well.

[Greg Neagle]

[QUOTE][u]Quote by: andyboutte[/u][p]So I tried that but am still having problems. Here is what ls looks like for my symlink:

lrwxr-xr-x 1 andyboutte staff 59 Jan 29 11:51 iLife.pkg -> /Volumes/iLife ’11 Install DVD/Installer/Packages/iLife.pkg

here is the entry from the log:

Working on folder 08 iLife11 (22:57:38)
Mounting the package dmg: iLife11.dmg (/private/tmp/idmg_temp.UjapA1/items-ESF5fm/08 iLife11) at: /private/tmp/idmg.MIsU/idmg_mp.YYIb
Installing iLife.pkg
Folder 08 iLife11 done (22:57:40)

its obviously not being installed because its only taking 2 seconds. when trying to manually install ilife11 on my instadmg boot system it only give me the upgrade option. should this matter for instadmg?[/p][/QUOTE]

Your symlink is only valid when the disk image is mounted at /Volumes/iLife ’11 Install DVD. With InstaDMG (and munki) it gets mounted at a random path. So you need a relative symlink:

iLife.pkg -> ./Installer/Packages/iLife.pkg

[Greg Neagle]

[QUOTE][u]Quote by: andyboutte[/u][p]Does anybody have any updates for this? sounds like the softlink is the easiest and most manageable. [/p][/QUOTE]

Yup. Just make a read-write disk image of the install DVD and replace the alias at the top level that points to Installer/Packages/iLife.pkg with a symlink. Optionally convert back to read-only compressed disk image.

-Greg

[Greg Neagle]

Here are some resources for Local MCX:

http://apress.com/book/view/9781430229377

MCX, dslocal, and Leopard

You can’t add MCX info to the built-in localhost computer object; you’ll need to create another computer object.

-Greg

[Greg Neagle]

You’ll get more and faster help on the munki-dev mailing list: http://groups.google.com/group/munki-dev

…but you set up multiple manifest files just by creating them and saving them in /manifests/. They are just plist files…

But I think you are confusing catalogs and manifests. So ask again on munki-dev with a little more details and we’ll see if we can get you on the right track.

[Greg Neagle]

$USER is not defined when the loginhook runs.

loginhooks are passed the shortname of the user as the first argument, so using “$1” instead of “$USER” should fix that.

Also, if you really posted the entire script, you need to add a “she-bang” line to the beginning, ala:

#!/bin/sh

-Greg

[Greg Neagle]

The “right” way to remove receipts going forward is

pkgutil –forget com.myorg.somepackage

I think doing so in a package postinstall script is a bad thing to do, however.

-Greg

[Greg Neagle]

“I create my user accounts using InstaDMG + createUser, so I can set the GUID to be identical. Could I use OD to manage that shadowhash like I would a plist, or does it not handle that type of thing?”

No, you can’t manage this using Open Directory. You’ll need to find another method to deliver changed versions of this file to all your machines. How do you install software on 400 Macs?

-Greg

[Greg Neagle]

1) ssh in and change the password.

2) If all the local admin accounts have the same GeneratedUID, push a new shadow hash file to /var/db/shadow/hash/

3) Write a script that normalizes the local admin account’s GeneratedUID for all machines, then #2.

4) Visit each machine in person and change the password manually.

[Greg Neagle]

I can’t imagine why the method you are using to get the MAC layer address would matter, but here’s how I currently do it in my equivalent script:

macAddress=`/sbin/ifconfig en0 | /usr/bin/awk ‘/ether/ {print $2}’`

-Greg

[Greg Neagle]

That would seem to imply that some other process is deleting the Desktop computer record _after_ your script creates it, since your script echos back the results of dscl . read /Computers/Desktop, proving that the record has been created.

-Greg

[Greg Neagle]

That hard-coded receipt path probably won’t exist under Snow Leopard.

As for suppressing the Office Setup Assistant:

Managing Office 2008

[QUOTE][u]Quote by: sgstuart[/u][p]Hi all and Greg,
I was able to get the installer to work, and place things in their appropriate place by changing $RECEIPT_PATH to its absolute path /Library/Receipts/Office2008_en_required.pkg/Contents/Resources.

In the appropriate place above, I also kept what I had from my changed script so not using $HOME, and I also had to copy the OfficePID.plist file to the same location as the SetupInfo.plist. This allowed the installation to work.

I am now having one problem left and that is it. How do I get rid of the First Time Run, so it does not ask any user what their name, company… and needing to click on each of those continue buttons, and having to close out of the Auto Update window?

Thanks,
Steven Stuart[/p][/QUOTE]

[Greg Neagle]

Looking at that Postflight script; it’s going to have problems running correctly under Snow Leopard, which, to be fair, didn’t exist when Office 2008 shipped.

The biggest problem is the reference to

bom_path=”$3/$RECEIPT_PATH/../Archive.bom”

Which simply does not exist on Snow Leopard, as the package is not copied to the Receipts directory, and in Snow Leopard, $RECEIPT_PATH ends up pointing to the original package. It’s possible that this might work, but I doubt it. This change in the definition of $RECEIPT_PATH ends up affecting the definitions of
bom_path
icon_path_partial
icon_path_full
and most importantly:
office_root_folder

The other possible issue is here:

source_pid_file=”$HOME/Library/Caches/TemporaryItems/Microsoft Office 2008/Office/OfficePID.plist”

When there is no GUI user, $HOME is undefined. In this case, it’s not clear to me if there is a valid OfficePID.plist at /Library/Caches/TemporaryItems/Microsoft Office 2008/Office/OfficePID.plist; if not, there’s nothing to copy…

IMHO, the easiest fix is to create a separate package that you run _after_ the Office 2008 install that installs your correct OfficePID.plist and SetupInfo.plist.

[Greg Neagle]

And you have this in /Library/LaunchDaemons/ ?

The permissions errors would imply that the script is running as a user other than root…

-Greg

[Author]

Posts