I can't speak to if this will work or not, but you may want to repackage the update installer using this.
http://managingosx.wordpress.com/2013/10/22/mavericks-day/
There is a 10.9 update for v8 coming. I doubt it'll have the whole streamed workflow but might be worth waiting on just incase it fixes something that is hindering you.
...or wait for 9.2 and not have to reinvent the wheel. ;)
JAMF mentioned they'll be updating the 8.x series to bring compatibility for Mavericks, as well as version 9. Maybe not any new features in 8, but in some limited testing we did, 10.9 and 8.71 (same version we're running) don't play so well together. It mostly works, but some stuff doesn't. Given this, you may actually want to wait until JAMF announces a Mavericks compatible release of the Casper Suite before moving forward with anything.
Also remember that typically new OS installs blow away any hidden admin accounts, so if you're using one as your Casper management account, you'll need to account for that.
http://twitter.com/golby/status/392735213937508352
RT @golby Looks like Casper 9.2 and 8.73 have been released to support Mavericks.
So upload Install OS X Mavericks.app to JSS using Casper Admin and publish through Self Service. Done. User can upgrade w/o needing admin rights...follow usual routines to deal with the usual gotchas (hidden admin account, iCloud prompt...etc.).
Don
Damn that @golby.. To busy playing here. :)
Oh & this article has had an update. https://jamfnation.jamfsoftware.com/article.html?id=173
@donmontalvo. Lol! And I was just commenting on the other thread about the 5 day release cycle they mentioned to you. I had a feeling it would be sooner.
@mm2270 LOL...dude, you were very much missed at JNUC. :)
@donmontalvo Could you elaborate on the "usual gotchas"? I know the hidden jamf user gets destroyed. Is there a guide to work around that?
Thanks all for your feedback. I will be testing the upgrade process via Self Service with JSS 8.72 and 9.2.
So far i've found:
Java 6 is removed on upgrade.
Maven / Ant need to be installed (developers)
Any gotchas anyone sees--shoot them to this thread. Java is a good catch because we have several Snow Leo systems that it will affect. TYVM! ROCK ON JAMF NATION!
if you have been using a com.apple.SetupAssistant.plist to prevent iCloud setup from running, you have to get a new one of those, there are more keys and the last seen on version bit is important.
@denmoff We found the two issues I listed after an initial test. Hoping to get more testing done in the coming days.
@donmontalvo I could only find vague references to someone writing a script to elevate sub-500 user accounts to be above 500 and then drop them below 500 again after the upgrade. I suppose that would a solution.
Apple is removing Java 6 installations during the upgrade for everyone.
I had a non-managed system also lose Java. You then have to re-download and install it after the upgrade.
Alternatively, if you've installed Oracle Java 7, it is untouched by the upgrade and survives fine.
@denmoff Have you tested this workflow? If so what result did you get?
@donmontalvo I have it all set to go in self service and i've backed up my test laptop, but i've left my power cord at home. So, i'm going to run it from home. Which would be the best place to test it anyway. :-)
@denmoff I noticed Rich Trouton post somewhere that his hidden admin account didn't get hosed, so I suppose YMMV. We have a LAB specifically for blowing $#!+ up. :D
I just ran a normal "user style" upgrade to Mavericks against a test MacBook Air previously running 10.8.4 and fully managed by our JSS running 8.71. Our hidden management account and all other sub 501 accounts are still present and accounted for. I tested the accounts and they are fully functional from what I can tell.
There are compatibility issues with JSS 8.71 and Mavericks, but that's another story.
So consider this another "thumbs up" that the hidden accounts aren't being clobbered by this install.
@mm2270 Cool! Did you happen to have any admin accounts that were 500+? I'm curious if the installer looks for at least one 500+ admin account. In my area, we have only one standard user and one sub 500 admin user. Well...i should find out tonight if there's any issue.
@denmoff, other than my AD based cached mobile account, which is an admin account, no, I didn't have any other local admin accounts on the box I upgraded.
I plan on doing another test from another managed Mac to test a few more things. If I can remember to do it, I'll create a local 50x admin account and let you know if it survives the upgrade, but my guess is it definitely will. In fact, it would be downright strange if it affected any of those accounts.
I can confirm the sub 501 Casper admin account survived a normal upgrade on a MacBook Pro that had 10.8.5 installed. I tested the Casper admin account by setting up a new policy to install an Office 2011 upgrade at the every 15 trigger and it ran without any problems. Hopefully a "self service" initiated Maverick update will also exhibit the same behavior when run on a test system. I haven't had a chance to test that combination yet. Since I'm only on 8.72 I can't use the new method supported by 9.2. I guess I'll wait to hear what others experience when doing that style upgrade.
Our 500+ local admin account survived.
@mm2270 Sorry for the confusion, but i meant, if you do NOT have a local admin with 500+ uid, would the setup process try to create one? i.e., will the user be able to create an admin account. I'm wondering if the installer looks for a local admin and if there isn't one, runs the Q/A to create it.
