Skip to main content
Question

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

  • October 23, 2013
  • 87 replies
  • 308 views

Show first post

87 replies

boberito
Forum|alt.badge.img+22
  • Jamf Heroes
  • November 11, 2013

Any luck doing it with the installpkgfromdmg?


Forum|alt.badge.img+23
  • Esteemed Contributor
  • November 11, 2013

Plenty! Works a treat!

Works so well one of the 2nd line started deploying it before I'd finished my own testing ...


ImAMacGuy
Forum|alt.badge.img+23
  • Esteemed Contributor
  • November 12, 2013

Initial testing under 9.21 seems to resolve the pkg.zip file issue in 9.2.


Forum|alt.badge.img+13
  • Contributor
  • November 15, 2013

From Support:

We had filed a defect on this behavior - in 9.2 and below we used Apple's built in zip utility to compress and decompress files, and noticed that it has a hard time with bigger files like Adobe Installs - in 9.21 we switched to the built in ditto utility which handles these files much better.

@jwojda Did you have to re-zip your packages? It seems like packages that were zipped with the built-in Apple utility would still be broken under 9.21, and you would have to re-zip under 9.21 in order to get a working package that was zipped with ditto.


Forum|alt.badge.img+6
  • Contributor
  • February 4, 2014

I'm trying to create a Self Service item to upgrade to Mavericks. I'm also getting an Admin password prompt after the installer copies.
The way I have it set up is; it copies the installer from the app store onto the local machine, then uses a script to launch the installer.
Any way to avoid the admin prompt?

I have tried to use https://jamfnation.jamfsoftware.com/article.html?id=173 as a guideline as we are still not on 9.2 or 8.73. The Mavericks Installer popped up and sadly it asked for the admin password to run. Even if run from Self Service as a Command (and not as suggested as a Script). Anything that I can change to make the progress better?

antoinekinch11
Forum|alt.badge.img+9

You can upload the InstallESD.dmg to Casper Admin. Then create a Self Service policy to install the package and reboot to the installer. That will NOT ask for admin credentials before upgrading the OS! Make sure the restart is set to boot from the OS X installer. Worked for me and I am using Casper Suite 9.3.


Forum|alt.badge.img+13
  • Valued Contributor
  • July 24, 2014

@Banjankinch. To be clear, the installesd.dmg and NOT the .app file?

Maybe I'm an idiot, but any of the suggestions saying you can "just drop the Mavericks install.app or install.dmg" file into Casper Admin and go... aren't working. All it does is mount and copy the installer but it never reboots and installs.


mpermann
Forum|alt.badge.img+22
  • Valued Contributor
  • July 24, 2014

@tnielsen, I followed the instructions at http://resources.jamfsoftware.com/archive/Deploying-OS-X-v10.7-or-Later-with-the-Casper-Suite.pdf to upgrade computers to Mac OS 10.9 through Self Service. You could also look at using createOSXinstallpkg by Greg Neagle to create an installer package. Check out https://code.google.com/p/munki/downloads/detail?name=createOSXinstallPkg_20131007.zip for more information.


Forum|alt.badge.img+13
  • Valued Contributor
  • September 4, 2014

So, in the end I went with createOSXInstallPKG. The reason I could not get the "drop installer into casper admin and be done" method to work was that I distribute via AFP. That was causing the problem, apparently.

In the end, it's a two step process. 1) Cache your installer PKG 2) Create a policy to install the cached package in self service.


Forum|alt.badge.img+12
  • Contributor
  • September 22, 2014

has anyone tried this without user interaction? like a script to trigger the policy or Installer? I dont rely on my users to actually do the upgrade via self service policy


stevewood
Forum|alt.badge.img+38
  • Hall of Fame
  • September 22, 2014

Since doing it via Self Service is just a policy kicked off by a user, just set the policy to kick off at logout, @wmateo. You'd probably want two policies, one to cache the installer down to the machines and then one to kick off the upgrade on logout.

I'd make sure to warn my users that it was going to happen at logout then throw up a jamfHelper or cocoadialog window letting them know once they clicked Restart/Shutdown/Logout that the upgrade was then going to take place and to NOT force shutdown or unplug the computer or close the lid.

Otherwise the upgrade should go find from there.


Forum|alt.badge.img+12
  • Contributor
  • September 23, 2014

@stevewood Thanks Steve that helped. I already had cached package.