[Rusty Myers]

Ah, egg on face. I actually thought you were talking about the track pad. I had no idea the back story! Ha ha. Good stuff! Cheers!

Rusty

[Rusty Myers]

I believe that 10.5.6 does update the image to include the new Macbooks and Macbook pro trackpads.

[Rusty Myers]

I just finished testing the SIU and netinstall of my InstaDMG image and found that it worked ok.

Yes, netrestore is in limbo at this point. Although it continues to work and probably will through out the next few operating systems. However, if it does fail, I am also working on developing a Deploy Studio install to replace my NetRestore. I suppose I should have mentioned that before hand! =)

[Rusty Myers]

What version of SIU? OS version? Is it a custom Net install?

My disk is almost 300GB too, it’s just an set size that the disk image can grow to, not necessary the actual size of the contents or the actual dmg. If I’m wrong, I hope to be corrected.

What about using NetRestore? It’s really not that big of a leap from NetInstall and can take a dmg strait from InstaDMG. Saves a bit of time if your updating the image regularly.

[Rusty Myers]

Check out this thread:

https://www.afp548.com/forum/viewtopic.php?showtopic=23151

[Rusty Myers]

Here’s how I’m doing it:

I package a script called systemsetup.sh and install it in /Library/Scripts/ folder. I also install the launchdaemon for that script in /Library/LaunchDaemons. I have other packages that install scripts and launchd items for AD/OD binding and setting computer names. My systemsetup.sh script runs a few first boot settings, then installs the launchd item for a second script which binds to AD/OD. It also removes itself and it’s launchd item. The AD/OD binding script runs and then also clears itself and then installs the last few launchd items that I want to run at login or system boot. The last few launchd items are for keychain minder, an apple script to check ad password expiration, and a script to set the computer Sharing name.

My package is NOT being installed at first boot. I run it within the build train for my image. I find that the easiest.

Here is the trimmed down script:

[code]#!/bin/bash

#System Setup for COE

#Time Zone Setup
systemsetup -settimezone America/New_York

#Set to use Network Time Server clock.psu.edu
systemsetup -setusingnetworktime on
systemsetup -setnetworktimeserver clock.server.com

#Enable ARD for admin
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -allowAccessFor -specifiedUsers
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -on -users “admin” -privs -all -restart -agent

#Start Remote Login
sudo /sbin/service ssh start

#Set SUS to Viper
sudo defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL “http://server.com:8088/”
sudo defaults write com.apple.SoftwareUpdate CatalogURL “http://server.com:8088/”

#Set hard drive name
diskutil rename / “Macintosh HD”

#Set hostname
hostName=InstaDMG
/usr/sbin/scutil –set ComputerName $hostName
/usr/sbin/scutil –set LocalHostName $hostName

#Remove Launchd item
sudo rm /Library/LaunchDaemons/com.server.systemsetup.plist

#Set AD/OD Bind Launchd item
mv /Library/Scripts/ETC/adodbind/com.server.adodautobind.plist /Library/LaunchDaemons/com.server.adodautobind.plist

#Make sure the permissons are correct
sudo chown root:wheel /Library/LaunchDaemons/com.server.adodautobind.plist
sudo chmod 644 /Library/LaunchDaemons/com.server.adodautobind.plist

#Reboot in 1 minute
#sudo shutdown -r +1
sudo reboot

#Self Destruct
srm “$0″[/code]

Well, there it is. I’d like to add variables later. I think all the commands were found somewhere on this forum, so thanks to all.
Rusty

[Rusty Myers]

I actually find it easier to run the scripts at first boot. I use Launchd and shell scripts. Lingon is a GUI for creating launchd items. Use a test machine and run a simple script at boot. Create a shell script with this code:

[code]
#!/bin/bash

osascript -e ‘tell app “System Events” to display dialog “This starts at boot.” buttons “OK” default button 1 with title “Boot” with icon stop’
[/code]

Use Lingon to create a launchd item that will run the script. I think the best way is to type in this code:

[code]
sh /path/to/script/[/code]

Now package both the launchd item and script. That’s about it!

[Rusty Myers]

I would guess that it’s running the commands on the local system, not the Image. You have to preface the commands to point to the InstaDMG Image. Use a $3 to specify the image.

See this thread:
https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=22379&highlight=$3

OR, run the script at first boot of the image with a launchd item.

[Rusty Myers]

jcontessa,

I run a system modification script at boot. It sets all of these settings. I install the script to /Library/Scripts/ETC (ETC being the department I work in). Then I use a launchd item to run the script. I used Lingon to make my launchd item.

Here’s a good thread on the commands to run in your script.
https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=22379&highlight=systemsetup

I can share my script if you want to check it out, email me.

[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.

[Rusty Myers]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]1.3 and 1.5 are the public releases. 1.4 was a non-public interim release.

If the hand-copied version works, but the pkg-installed version doesn’t, it seems to point to the pkg. But I’m at a loss as to what the problem might be, since I’d guess you’re only installing KM and nothing else fancy.

To double check, what does the following code report for you?[code]lipo path/to/Keychain\ Minder.app/Contents/MacOS/Keychain\ Minder -info[/code]Mine says:[code]pfergus$ lipo /Applications/Utilities/Keychain\ Minder.app/Contents/MacOS/Keychain\ Minder -info
Architectures in the fat file: /Applications/Utilities/Keychain Minder.app/Contents/MacOS/Keychain Minder are: ppc7400 i386[/code]- Patrick[/p][/QUOTE]

I get the same thing: Architectures in the fat file: MacOS/Keychain Minder are: ppc7400 i386

[Rusty Myers]

[QUOTE][u]Quote by: MacTroll[/u][p]1.4 might not have been officially released, so yes, try with 1.3.

Strange that hand copying it works… I’d diff the binaries between your hand copied version and the one that your pkg installs.[/p][/QUOTE]

Keychain Minder 1.3 works as expected. I built a new package and recycled old scripts and launchd item. I’ll have to check the other suggestions.
Thanks!

[Rusty Myers]

[QUOTE][u]Quote by: MacTroll[/u][p]1.5 is still a fat binary for 10.4+ and lipo confirms that.

Have you tried with 1.4?[/p][/QUOTE]

Testing with 1.3 now. Didn’t find a 1.4 dl link.

[Rusty Myers]

[QUOTE][u]Quote by: Patrick+Fergus[/u][p]What happens if you replace KM with a hand-copied version rather than a pkg installed one?

– Patrick[/p][/QUOTE]

Hand copied (installed after restore) works fine.

[Rusty Myers]

[QUOTE][u]Quote by: akinspe[/u][p][QUOTE]Does this apply to hashes created by the shadowHash script, or just to cleartext passwords entered into the USERDATA file? I has assumed this statement applied only to the USERDATA file. My password has several special characters.[/QUOTE]

you may need to enclose your password in quotes depending on the characters used. This is not a function of shadowhash, but rather a consequence of the shell interpreting your characters.

i.e.

./shadowHash “yourpassword”>password_hash

Hope this helps[/p][/QUOTE]

I’ve found that it is required to escape special charachters in the hash, quotes did not work for me. I could have quotes or no quotes, but unless I escaped those characters, it failed. Example:

If your pass =
“mypass|word”
then
your password must have characters escaped like:
“mypass\|word”
else
fail
fi

[Author]

Posts