Skip to main content

I've been using Neagle's great tool "InstallOSXpkg" to deploy Lion and have now begun testing with Mountain Lion. That tool is introduced here: http://managingosx.wordpress.com/2012/07/25/son-of-installlion-pkg/



The problem: I can't get the right policy settings to both properly reboot the mac into its install environment AND log the policy as completed. Instead, what happens is one of three things:



1) If I set the policy to "reboot only if a package or SWU requires", the copy of the install is made but the installation of the OS never happens. The computer remains booted, just now with an "Install OS X Data" folder in the root directory.



2) If I set the policy to "reboot only if a package or SWU requires" AND also add "/sbin/reboot" into the RUN COMMAND field in the advanced tab, the copy will occur, the mac will reboot into the right environment and the new OS will install! However... the policy won't log that it's completed so, 15 minutes later, it repeats itself.



3) If i set the policy to "reboot immediately" and include the "/sbin/reboot/" command, the computer just keeps rebooting in an endless loop.



JSS = 8.5.2
pkg was NOT tagged in casper admin as "requires reboot" at the time of this posting but i'm experimenting with that next.



thoughts?

I use this in my advanced tab for the SS policy.
jamf recon | /sbin/reboot, and set the rest of the reboot radio buttons to not reboot.



I also only tested in 8.6, so I don't know what running as 8.5x will do.



Also, are you using the current version of the createOSXinstallPkg_20120831



http://code.google.com/p/munki/downloads/list



---
That being said, I haven't been able to get a reliable upgrade out of it. If I do a fresh built 10.7.x system and do the upgrade it's fine, but it seems that when I do a users machine i get the multi-language screen of death.

dang, hit the wrong buttons.



yes: i have the most recent version of the tool.
no: haven't tried piping the reboot via the recon command line tool but will.



then i'll report back.

well, here's the good news:



the installations all appear to be running exactly as i'd hoped with this newer command line modification.



the bad news: the policy isn't logging. so there's no way to track what's been done and then it tries to re-run the policy indefinitely.

Is updating to 8.62 out of the question? In order for me to ever get InstallLion.pkg to ever log I had to rely on our users to manually reboot, which works just fine for us. I haven't deployed ML yet with createOSXinstallPkg, but I know that 8.6 fixed the reboot immediately option in a Self Service policy. Might be worth trying on a test JSS.

not out of the question. just not going to happen currently. but i can say this much: i've been using installLioin.pkg with no problems whatsoever on a JSS v8.52 so i'm surprised that i'm having issues with the new OS packaged in about the identical way.



and yes: a self serve policy seems to work differently than an automated/timed policy. which is fine if you'd like to provide that kind of policy. we'd prefer a timed/automatic policy.



:)

Thanks for the suggestions here. I was having the same experience as themacdweeb. The installation policy would install the proper files, but reboot back to a login window instead of into the 10.8 installer. Adding jamf recon | /sbin/reboot to the policy's Advanced tab worked well.

I do a multi-group setup.



A static group details who is allowed the install the new OS (based on purchasing and licensing requests). JSS then caches the installer on their drives and runs recon.



A smart group then looks for the cached installer (and the OS < 10.8) and adds a self service option to do the install (install cached package). My policy is set for reboot if required but I do run /sbin/reboot to be sure.



The install does report as being completed, and because of the OS change, the user is no longer in the smart group to be presented with the install option.

Terms & ConditionsCookie settings