Skip to main content

We are a University with open access labs with a lot of Macs.
There are no admins that use the computers, they are used by students who are restricted. It's therefore difficult to try to push macOS upgrade.

This is actually our first in place upgrade we are trying.

I want to deploy High Sierra, but have been hitting a wall at almost every turn.
What I want to do is wake the machines at 1am, and start the installation when nobody is logged in. Is that possible?

I tried simply uploading the installer app, caching it and then installing cached. It works under certain circumstances (seems OK directly after a reboot, on a VM), but caused no end of problems on real devices (reboot loops/panics even though the hardware is reasonably new and supported by the OS).

I've seen scripts around using the startosinstall command, but when I launch this when nobody is logged in (after deploying the app in a package nad testing with recurring checkin), it appear that nothing happens. And install.log doesn't really give you a hint.

I'm trying to find a definitive answer for upgrade; there's a lot of threads out there, but mostly seem to deal with self service...

Does anyone know how to FORCE a restart on the logged in user so High Sierra can install no matter what apps or files they have open?

EDIT: Never mind! I added (TOTALLY FORGOT ABOUT THIS!) a restart option in the scripts policy to restart immediately on No User and User Logged in. Which worked!


Does anyone know why the High Sierra installer (10.13.6), brings the workstation back to a login screen and when the user logs in, the install is still running with 12 min left to install? Like is this normal? See screenshot:


@monaronyc It happens in Mojave too.


@mark.mahabir OH! Okay? Glad its not just us. But good to know. Thanks for the heads up!


Hello. A few weeks ago I started testing my Mojave upgrade workflow using the MacOSUpgrade script from JAMF. I'm also experiencing the installation resuming for another 13 minutes after the user log in consistently. I just wanted to check in and see if this is still expected behavior of the installer if you do not use an auto login account as part of the upgrade process.

Thanks!


@Jalves As far as I can tell it's a timing thing. If the mac is left after the upgrade and then logged into several hours later you don't see that extra screen, it'll just log in.


@allanp81 Has this been tested extensively? We are looking to roll out upgrades overnight and I'm wondering what the exact number of hours would be.


@apunsal I've never tested it specifically but it felt like a couple at least.


Hello. Would any of commands above work for macOS Mojave installer?