Mojave In-Place Upgrade

I have not tried Mojave yet but have a modified verison of the script you mention in a Self Service policy for Sierra and High Sierra. Are you running yours in Self Service?

Correct, I have been running it through Self Service.

Now that you mention it, I will try just pushing it down to see if that changes anything.

EDIT: Same behavior when run at check-in.

Found a solution for this. Let me know if you are still stuck, i'll share what we did.

@mack525 I would be interested in hearing about your solution.

Just push the installer with VPP/Package and then call the startosinstall binary with a script in self-service.

What we did in our environment was use two policies:

1) Create a dmg that has the "Install macOS Mojave.app" located in /Applications/. At this point, it should already be cached to your devices, but we did deleted what was there previously and to ensure all computers updated to 10.14.2

2) In Self Service we have an upgrade button that runs the following command

/Applications/Install macOS Mojave.app/Contents/Resources/startosinstall --applicationpath "/Applications/Install macOS Mojave.app" --rebootdelay 1 --nointeraction --agreetolicense

I think that's going to run into the same problem of needing administrative privileges to begin the installation. I'm not really sure what your options are without administrative privileges to be honest.

One thing that comes to mind is a macOS provisioning tool that would make an "upgrade" disk our Apple engineer has told us about, but that does mean touching all the computers.

I'm testing the --startosinstall command for the first time. I've cached the Mojave installer to Waiting Room and am running the command manually before I create a policy. I'm getting an error that "--applicationpath is deprecated in 10.14 and greater. Please remove it from your invocation". When I run the command with --usage, --applicationpath is not listed. Has the required command changed?

I was able to install mojave with the following command, i.e. the --applicationpath switch appears to no longer be needed.

/Applications/Install macOS Mojave.app/Contents/Resources/startosinstall --nointeraction --agreetolicense

@mack525 I saw your response and wanted to just ask what your solution was for the in-place upgrade? I'm running into issues with this.

@msample @m.donovan By using and following Joshua Roskos macOSUpgrade and this Jamf Self Service upgrade pdf guide walkthrough really made this less painful for us.

Since the majority of our users are not admins, we also used this temporary admin script to grant temp admin access that runs before the installmacos installer app gets placed. Once the OS installation is finished and the machine logs in/checks in/logs out, user would be demoted.

This has worked for High Sierra 10.3.6 and Mojave 14.1 so far. Let me know if any of you get stuck.

@mack525 ..Nice. Thanks, this very helpful. I've got Josh' script connected in along with the policy for the in-place upgrade. However with the test runs it kept throwing up an error. So this is where we got stuck, but looks as if the Jamf Self Service upgrade pdf guide you've shared my give us an alternative approach for resolving the task of in-place upgrading. The test macs I have are already running 10.13.6, so no worries there. I'm not sure we'll need to grant the end-users temp access, because techs here will handle the task of self-service initiations. I'll definitely review the pdf and run test.

@msample Nice! Once you've configured all the parameters within JAMF, its as easy as creating a composer package with the installmacos installer in the /Applications folder and you should be all set.

@mack525 I know you aforementioned that your temp admin script runs before the macosinstaller initiates, but did I miss where you placed the script in sequence? Or is it added independently as along with the policy? Just curious.

@msample Ahh sorry i did not mention this. If you are following this Jamf Self Service upgrade pdf guide You'll see that there are two policies needed for the script to work properly. What we do is add the temp admin script in that download policy and set the priority of the temp admin script to "before". So to answer your question, it's added independently.

Heres what I did to get around the admin prompt. (https://www.jamf.com/jamf-nation/discussions/31006/upgrading-to-macos-mojave-without-ss-and-100)

Only issue I'm having is after the update starts it installs for about 30minutes then the login screen appears but when you login it continues the installation for another 10-12minutes. Anyone knows why that happens

Just grant the end user admin access as part of the process, then strip the admin access away after the upgrade. Works.

Well in my scenario I did not grant anyone admin access. I ran the OS install by using the "File and Processes" section and running the command "/Applications/Install macOS Mojave.app/Contents/Resources/startosinstall" --rebootdelay 60 --nointeraction --agreetolicense &" which will be ran as the root user.

The installation runs as expected but after 30min it goes back to the login screen and when you login it completes the installation for another 10-12 minutes. this is the part I'm trying to understand whits doing this.

@kroberts1 I haven't yet tested Mojave but saw the same behavior with High Sierra where the first user to login after thinking I was done with the upgrade had another 13 min for the installation. I was hoping this was gone with Mojave but apparently not. The odd thing is that not all of my High Sierra upgrades did this and, unfortunately, I didn't document them to try figuring out why some did and some didn't. Also, subsequent user logins by other user accounts didn't trigger this installation behavior when the first login had done this.

@cdenesha I was able to also use the command

#!/bin/sh
/Applications/Install macOS Mojave.app/Contents/Resources/startosinstall --nointeraction --agreetolicense

but it only works in a self service scenario. When i try to push it via a policy at check-in with no user logged in (Lab deployment scenario)

I get the following in the Logs.

Here is the log when it works from Self Service for coparison

Also @kroberts1 and @jhuls the 13 minute screen is also in Mojave 10.14.3 after first log in, just tested it :/

Just thought of testing it with a user logged in and noticed my restriction for 10.14.3 blocked it. Wonder why using Self Service didn't stop it.

I removed the restriction and it seems to be working with out a user logged in now =)

-Peter

@szultzie yes, i also did a few more testing and got that stupid 13min remaining after log in. Idk what the machines are doing at this stage which is very frustrating. Is anyone else experiencing this with other MDM platforms?

So update, no user logged in doesn't work anymore. Not sure what i did. lol