@psherotov I'm faced with the exact same issue and I think the blame lies with Apple, not Jamf.

I believe this isn't a JAMF issue. Instead it's the way Apple applies this update to machines. I have no idea why this Apple install waits to the first login to complete but I have see this same behavior whether I use JAMF or not to update systems to High Sierra and/or Mojave.

It's a pain in the bum to be honest as to the end user it looks like we don't know what we're doing!

The Mac goes through the upgrade process and shows the Mojave desktop with login. The first user to login (whoever they are) sees another black screen come up saying 13 minutes remaining. After that process completes then they can login to Mojave.

I've seen reports of this behavior on the MacAdmins Slack across multiple MDM services (or even without MDM, just double-clicking the macOS Installer from /Applications to run the update). I agree it's frustrating, but Apple needs to resolve this issue.

A colleague of mine who is an admin at an all mac school who is using Munki said he has not seen that issue on any Macs he has upgraded? And if this is an issue originating with Apple, for the purposes of not sticking end users with 13 minutes of downtime, isn't there some auto login script that could be pushed out so the install would finish? I've googled and gone through the message boards here and have not found a solution/work around along those lines.

I would presume part of the issue is that Apple have decided that a user needs to be logged in to initiate the upgrade.

A colleague of mine who is an admin at an all mac school who is using Munki said he has not seen that issue on any Macs he has upgraded? And if this is an issue originating with Apple, for the purposes of not sticking end users with 13 minutes of downtime, isn't there some auto login script that could be pushed out so the install would finish? I've googled and gone through the message boards here and have not found a solution/work around along those lines.

I will put it to the test to see by just installing Sierra/High Sierra from USB and then double click the installer and see what happens.

You may want to test how this is different on macs with and without SSD drives keeping in mind that only SSD drives are auto-magically formatted to APFS during the upgrade to High Sierra and above. Perhaps the friend that uses Munki and doesn't see this has only HDD drives?

Also you can test rebooting the computer when it's at that first login screen to see if that kicks off the "wait 13 minutes more, please" process.

Jamf is not to blame here. Committing 100% to a Free alternatives isn't the answer either. The answer to solve these problems are "JAMF plus All other tools available to use as MacAdmins." ex. Jamf & Munki & etc.

The blame lies with Apple. Quite frankly as much as I love Jamf, Apple should really offer a 1st Party MDM Solution.

@lynnaj All of my Macs I've tested the upgrade process on are SSDs and I see the extra 13 minutes behaviour on all of them.

@allanp81 --- I too have seen this on all the SSD macs I upgraded last summer from Sierra to High Sierra. However, I have not seen this extra time when taking a mac from High Sierra to Mojave. I wonder, therefore, if the "wait 13 minutes more, please" is the APFS reformat process ???

Here's the original thread on this.

I've heard of this when the currently logged in user is not an admin like if they run it through Self Service. But if an admin user runs it through Self Service it works great. So maybe that's a piece of the puzzle.

@lynnaj i dont think this its the reformatting to APFS. I've had devices which i've install both HDD and SSD formatted as APFS for High Sierra. When i trigger the Mojave update and it reboots im still getting that 13 minutes crap.

@lynnaj You may be right as you can SSH in to a device while the progress bar is shown and the only obvious task doing anything is mdworker I think.

@boberito i've seen this in threads but that a real stupid way of managing student labs. if i execute this command in a script " /Applications/Install macOS Mojave.app/Contents/Resources/startosinstall --agreetolicense --nointeraction " i'm automatically triggering as root so why would i need to make the current user an admin to trigger an update flawlessly. That's a really poor design by Apple.

We have 100's of macs that don't have JAMF on them and we saw this behavior on 10.13 and 10.14 if you attempted to log back in quickly after the upgrade. If you waited a day or so to log back in, the issue was gone, so if you can arrange a bigger window of downtime for your upgrades, it's easier.

@SGill

idk, i cannot schedule an upgrade today in an organization then tell employees they cannot login until the following day. I believe for now the best way is to auto login with a service account have it complete then disable auto login. But it also surprises me that JAMF does not have a solution for this because every post for upgrades has this issue.

I didn't test how little time after the completed upgrade you needed to wait, but it was longer than you might think on most macs. Any attempt to log in within, say, 2 hours of 'upgrade complete' got the additional progress bars on login for sure. I was also using a mass-login to finish them until I realized that all I really had to do (for computer labs at least) was wait.

Just to summarize responses to some of what people have posted so far:

Even manually triggering it logged in with an admin account still causes the same behavior (13 additional minutes). So admin rights doesn't seem to be the issue.

The behavior occurs even on mac that are already formatted APFS--so the conversion doesn't seem to be the issue either.

I am intrigued about there being a period of time that has to elapse before the installation completes after it completes and if end users wait they won't experience the additional installation period.

Circling back to my frustration with Jamf, why don't they have some of this information readily available to mac admins in documentation or via tech support? Zero Day? Mojave has been out how long? 4-5 months? Also, as a work around, a script that automatically logs in a local user?

Thank you everyone for contributing your experiences, I've gotten farther in 30 minutes than I have in two weeks, at least in having some options or possibilities. Keep the information and ideas coming please! :)

I also want to add that my colleague has SSDs and HDD Macs and has not experienced the behavior at all.

Echoing what some others have said.

On a Mac I have at home, saw this exact thing. No MDM component there, just a plain old (2012) laptop. We have also seen it on some devices here when running an in-place upgrade from HS to Mojave through Self Service. On some devices, if we logged in immediately after the final reboot of the upgrade, this happened. If the device sat for 2-3 hours after the upgrade, did not see it. Certainly seemed to be more prevalent on the older devices but all models have done it from time to time.

I'm going to run an upgrade on a Mac and let it sit overnight and see what happens tomorrow morning. Stay tuned :)

Thanks again to everyone who contributed their knowledge and experiences. If anyone has something to add please share!

Joining you with that as well @psherotov . My test will be on a Fusion drive. This should cover all types of drives we've experience this scenario.

I also have seen this, but even it stands a 15 minutes or thereabout it only takes only 3-5 minutes and it is done as the minutes goes Down very fast But Strange apple Cannot get rid of this. I have same issue on clean mac without any Jamf at all installed