Self-Service 10.9 install problem

[justin]

I know there has been a lot of discussion about how seamless and easy it's supposed to be to upgrade to 10.9 by just copying the installer over and creative a self-service policy for it, however we've not had that experience at all, it simply never worked. the policy would run, it would appear to download, and then either say that it completed but upon (manually) rebooting (auto rebooting never worked as part of the script) it just restarted to the 10.8.5 install, and option-booting to the 10.9 installer was never an option either.
the workaround that we are having luck with is to have a policy in place to cache the 10.9 installer, and then create a self-service policy to install the cached installer. this is working in most situations, but we're finding that some computers by default have rebooted to the installer. disruptive to say the least.

we've got no policies in place that would trigger it to install, is it just a weird bug? has anyone else run in to this? i assume not because it seems most people are fine with just running the install from self-service..just hoping someone might have some ideas.

[golbiga]

This is how we're installing Mavericks with createOSXInstallerPkg.

1. Run a policy that caches the installer to the machine so it resides in /Library/Application Support/JAMF/Waiting Room based on smart group membership.
2. Once it's finished caching the user will see a Self Service policy that will kick off the cached installer and I've added a /sbin/reboot to Advanced commands to reboot when finished
3. The machine will reboot to the 10.9 installer
4. Installation finishes, reboots and then I have a firstboot script that finishes up the whole process.
5. User logs in to an upgraded machine

Hope this helps,
Allen

[wmateo]

@golbiga what about if the disk is encrypted? I tried this and it brought the mac to the recovery partition. Which tells me it could not mount the drive