Posted on 10-23-2013 06:53 AM
Hi.
I wanted to look into options to all our designers to upgrade there machine using Self Service.
We looked into "createOSXinstallPkg_20131007.zip" as it should be able now to support Mavericks.
The PKG installation was working fine.
But deploying this package via Self Service totally failed.
Is https://jamfnation.jamfsoftware.com/discussion.html?id=6430 the way to go?
Thanks for any input on that.
Cheers
Posted on 02-04-2014 10:19 AM
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?
Posted on 04-10-2014 01:12 PM
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.
Posted on 07-24-2014 07:41 AM
@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.
Posted on 07-24-2014 09:08 AM
@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.
Posted on 09-04-2014 08:55 AM
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.
Posted on 09-22-2014 09:27 AM
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
Posted on 09-22-2014 09:51 AM
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.
Posted on 09-23-2014 12:11 PM
@stevewood Thanks Steve that helped. I already had cached package.