Ideas on "How to Upgrade Mavericks via Self Service"?

Graphical editors and my more Macized colleagues drive me nuts. If you want to do scripting, learn vi people :)

@nessts

+1

Or use BBEdit. Editing files correctly since 1991.
(TextWrangler (same company) is free)

@rtrouton - used text wrangler. I will mess with it s'more and see what I can see (read: flop and twitch like a fish out of water)

@nessts you're right, but I'm really bad at scripting, but am slowly picking it up. don't knock my crutch :) But I'm glad to help drive you nuts. I'll even throw some cashews in for good measure.

vi vs pico vs nano....FOOD FIGHT!!!

+1 for vi...gets the job done (and shoved down our throats by *nix admins in the 90's).

+1 for BBEdit...I never have a Mac without it. :)

pico and nano are the same editor on OS X. Wouldn't be fair to gang up on vi like that.

vi clearly wins, it solves mazes for goodness sake!

http://www.flystrip.com/~corby/vi/solve_maze.html

And I've been shoving vi down people's throats since the late 80's! ;-)

@jwojda thanks for the reply. So is there any way to get such a script to run after a Self Service upgrade?

/url][/url">@gajones][/url][/url you could leverage this:
[http://derflounder.wordpress.com/2013/05/13/first-boot-package-install-pkg/
using a PKG that runs whatever commands you like as a postinstall script.
Then bake it into the OS installer using createOSXinstallPkg

BTW, @rtrouton][/url][/url, @gregneagle][/url][/url thanks for everything you're doing. I love you.

@Chris thanks!

i noticed that after I did the createOSXInstall w/ the afore mentioned first boot package install that while the system upgraded and did it's thing, I was removed from the sudoers file. My account page showed I was an admin, but whenever I tried to do sudo through terminal it said I wasn't part of it.

Anybody else run into that?

Anyone figure out how to skip the iCloud setup when upgrading via Self Service? (and get java installed)

I understand the First Boot script idea which works great for a full image. But is there any equivalent when done via Self Service?

Tools needed:
- Install OS X Mavericks.app
- createOSXinstallPkg
- First Boot Package Install.pkg
- Java for OS X 2013-005
- Script to disable iCloud (and set whatever other prefs you like), wrapped in a .pkg

-> Stuff Java and your script (as a .pkg) into First Boot Package Install.pkg
-> run

sudo ./createOSXinstallPkg --source /path/to/Install OS X Mavericks.app --pkg /path/to/First Boot Package Install.pkg

-> upload resulting PKG to Casper
-> cache resulting PKG on clients
-> create Self Service policy that installs cached PKG, add

shutdown -r now

to the "run command" field in your Self Service policy
-> boom, done!

So ok let me resumerize and see if I understand.

Collect all the things I need and a First Boot Package from an imaged machine pre-boot?

Make 1 package with those.

Then make a huge package with those and the 10.9 installer.

Do all the policy stuff to cache it and stuff. Then add shutdown -r now command to the actual install policy.

I take it this will boot into a First Run package and install Mavericks behind the scenes?

If you follow exactly what @Chris posted above you will have a working Policy to install 10.9 in self service with Java, First Boot, and Disable iCloud. Should be a solution on this thread.

Edit. I missed stuff way above. So I think I'm good.

We did this the very easy non-scripted way, Two policies, first one caches the installer and then calls the second to run the install. User can see the progress whilst it downloads then will be down for just over an hour whilst it upgrades and wont be prompted with any questions.

1) Download installer from the App store 2) Upload whole downloaded installer from Applications in to casper admin (dont run it just upload it)

3) Create 1st policy to cache the install. ie add the installer with cache set only rather than install, set it to also run a command "sudo jamf policy -trigger cachedmavericks" , make it available as a self service option to whoever you need , with whatever warnings you need.

4) Create 2nd policy to install the cached installer, untick all triggers except other with name "cachedmavericks", set to reboot immediately. This one doesnt need to be available in self service, although teh scope needs to be the same as the first.

utilizing @rtrouton 's script, I want to add a line to turn on the firewall, but i'm not seeing what the command is in my 10.8 script, maybe I'm not looking for the right thing - anybody got it off the top of their head?

also, I noticed on his website and mentioned in his script he has the com.company.initialsetup.plist file - is that required? if so, do i just copy it, modify what needs modifying and use a DMG to put the plist and fb script down in the proper locations? Or do I remove those from the FB script and just use the script I U/L to casper and run that?

This is what I'm using to enable the firewall, with logging enabled and stealth mode disabled

# Enable Application Firewall
defaults write /Library/Preferences/com.apple.alf globalstate -int 1
defaults write /Library/Preferences/com.apple.alf loggingenabled -int 1
defaults write /Library/Preferences/com.apple.alf stealthenabled -int 0

@wyip thank you! that works perfectly!

as far as the firstboot script from the 2nd part of my question. I got it working by putting them into a dmg file and then putting them down on the box. however it seems to interrupt the adobeinstall from Casper... is that expected behavior?

I'm getting this error when testing deployment of a package I created using the instructions @Chris posted:

Installing InstallOSX_10.9_13A598_custom.pkg.zip...
Installation failed. The installer reported: installer: Package name is OS X installer: Installing at base path / installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

All I've put into the First Boot Package Install is Java.

Have you tried installing the PKG manually, without Casper?
Any clues in /var/log/install.log?

Apparently there's a bug in installing pkg.zip files over 4gb

I'm stuck also because of that. If I manually install it, it works. But installing via casper self service policy, no luck.

Just hit the same issue. I'm going to wrap my pkg in a dmg, cache it and install via JAMF's installpkgfromdmg script a la my CS6 deployment.