Disclaimer: All credit for this method goes to
Greg Neagle for creating the amazing createOSXinstallPkg
and Rich Trouton for his First Boot Package Install.pkg.
Check the linked pages (if you don’t know them yet) to get an understanding of how we’re putting the pieces together.
Of course it would be possible to deploy the Mavericks installer as it is from the App Store.
However, as we learned, upgrading to Mavericks removed Java from your Mac, and the user would be greeted with the iCloud sign-in dialogue once the upgrade is completed.
Maybe you don’t want that. And maybe you want to add a “postupgrade” script to the installer to make Mavericks fit your environment. Maybe you want to tweak the authorization database since /etc/authorization is deprecated in Mavericks…
Lots of reasons not to go with the standard installer.
I’ll try to explain how to do this.
Building a payload-free package with Composer
We need our postupgrade configuration script to be wrapped in a pkg.
Launch Composer and create a new empty package.
Click the triangle next to your package in the sidebar, then right-click on “Scripts”, select “Add Shell Script” -> “Postinstall” or “Postflight”.
Then paste your script contents into the script editor and save it.
Select “Build as PKG” to finish the build process.
Preparing First Boot Package Install.pkg
Right-click the package you downloaded, select “Show Package Contents” and navigate to
You will find six numbered folders in there.
Each pkg we want to install on first boot goes into one folder.
Payload-free package to run the configuration script:
Java for OS X installer:
Of course you don’t need to have exactly six pkgs, however you can add additional folders as needed. Remember the 350MB size limit!
Building the Mavericks installer pkg
Here’s where createOSXinstallPkg comes into play.
We’re going to bake our prepared First Boot Package Install.pkg into the Mavericks installer.
To do that, fire up Terminal and run
sudo /path/to/createOSXinstallPkg --source /path/to/Install\ OS\ X\ Mavericks.app --pkg /path/to/First\ Boot\ Package\ Install.pkg --output /path/to/Output.pkg
Grab a coffee while it does its thing.
Deploying the Mavericks installer via Self Service
Once your package is ready, upload it to Casper Admin.
We’re almost done!
Now we’ll create a policy to cache the installer on our clients.
Create a new policy:
Add the Mavericks installer package we just uploaded: Choose “Cache” from the Options
Scope it to a group or single computersChoose a triggerAnd set it to “Once per computer”Give it a name and a categoryNow we need to know which clients are done caching the installer.
Therefor we need a create smart group:
In order to make the Mavericks installer available in Self Service, we create another policy.
Scope it to the smart group we created:Make it available in Self Service, upload an icon and add a description:Install the cached installer:Add “shutdown -r now” in the “Run Command” field to trigger a rebootOur policy should now show up on the clients on which we cached the installer!
When the user selects “Install”, the Mavericks will run for 5-10 minutes and reboot the computer afterwards.
It will then boot into the actual OS X installation environment and upgrade the OS which takes about 45 minutes, depending on the machine you run it on.
When the upgrade is done, the computer reboots again.
Now the First Boot Package Install.pkg kicks in and runs our script & installs Java,
plus whatever else you set it up to install.
During this, the end user will see the grey Apple bootscreen with the spinning circle.
Once all packages are installed, the Mac will reboot one last time and is then ready for the user to log in.
So far this method has worked very well for me, however
I’m sure there are smarter/better ways to achieve the same result and if you know one,
please let me know!
Same goes for any errors/mistakes you find in my posts.
Thanks to Mr Greg Neagle and Mr Rich Trouton for their amazing work,
and for sharing it with the Mac admin community.