[mgb123]

This functions perfectly!

I have a pkg that puts the cert down, and then the 1st boot script installs it and deletes it from the temp location.

Perfect!

[mgb123]

Commented out the reboot command, and un-commented the shutdown command. That did the trick.

Building the entire shebang into an image now, will re-image and test.

[mgb123]

Running with local PackageMaker 3.0.4 seems to have corrected the odd owner/group issues – Root/Wheel is correct now.

It does appear that execute permissions are required though – RW-R–R– didn’t work for me, but RWXR-XR-X did.

Now making change to the sequencing of the kill/reboot in the script.

[mgb123]

So – turns out the version of PackageMaker I have was running off a 10.5 partition on the same physical disk.

I’m going back through everything, will re-build with a local version of PackageMaker on 10.6, with the original 644 permissions (root/wheel), and report back. I’ll build the package and run on a partition and reboot – if it works, I’ll try inserting into build.

I’m going to be more than a bit embarrassed if that turns out the be all that’s going on here.

Should that not work, I’ll attempt rwxr-xr-x (root/wheel). Run on partition and then insert into build on success.

[mgb123]

Tried marking the script as executable – no luck there. (Root/Wheel RWXR–R–)

[mgb123]

Nate – Got the note – just to be clear, though my permissions are correct, the script doesn’t run at all unless I run it manually after booting. All settings are Running the script manually is odd too – – the script won’t run with the plain ‘ole ./firstboot.sh – it requires that I specify sh./firstboot.sh – is that normal?

I’m going to make the change to the running of the script in the .plist and see if that will resolve the running- I’m curious as to why my script requires this but no one else seems to have encountered it.

I’ll make the adjustments to the reboot/kill sequence that you specify.

Thanks for your help on this!

[mgb123]

I tried posting my code but it doesn’t seem to work – append this to the end of the pastebin dot com site name /pB25VVjU

[mgb123]

I tried to post my code, but it’s getting flagged as spam- any ideas.

[mgb123]

[code]

Label
com.mycompanyisbetterthanyourcompay.firstboot
ProgramArguments

/Library/Scripts/firstboot.sh

QueueDirectories

RunAtLoad
WatchPaths

[/code]

[mgb123]

Nate- first off thanks very much for your time on this.

The script and the plist both exist. The error that I was getting in console is: Permission Denied, so chmod’ed the permissions to 644 – then I tried to run the script from the command line and got the following error: command not found – which was Odd, since I was looking at the firstboot.sh script.

One last attempt prior to calling it a night – sudo sh./firstboot.sh – and BAM everythign ran, and the machine rebooted. The changes implemented in the script have applied.

As a side note, the script deleted the .plist file, but the script didn’t self destruct- it’s still there in the directory.

So – I’m guessing that I’ve missed something in my plist – maybe?

[mgb123]

Nate,

I checked my permissions, everything seems to be in order- any chance that the 10.6.5 update hosed something with regards to Launchd?

[mgb123]

I checked my permissions, they seem fine- one followup question then is, how do I set the permissions for the folder that I’m putting the script in?

For instance, if I tell Packagemaker that I want the script in /Library/Scripts/The_greatest_company_ever/firstboot.sh – by selecting the firstboot file and then listing /Library/Scripts/The_greatest_company_ever/ as the destination, my firstboot.sh permissions are fine, but the folder The_greatest_company_ever is marked as no access.

I thought perhaps the best way to deal with this would be to put the folder itself in the package, and then mark the permissions as 644 (which is drw-r–r– right?) but this didn’t seem to work either.

I’m doing another test image right now, I’ll post my progress. Thanks very much for the response!

[mgb123]

Totally successful with the EWS version. Drag and drop the Entourage EWS updater on, and blammo- success! (yes you have to say or it won’t work!)

So 3 parts:

-Office 2008 SP 2 installer
-12.2.7 Update
-EWS Update

All dragged on to the Office patcher, and then installed in that order.

[mgb123]

Since 12.2.7 and Entourage Web Services updates have come out since this post was first written -what’s the appropriate way to update? EWS requires 12.2.7 – but 12.2.7 doesn’t require 12.2.5.

So- drop in 12.2.7 and EWS updates, and run the patcher on them both?

[mgb123]

Fantastic, thanks for the info!

[Author]

Posts