10.14.3 deployment issue anybody?

Same issue here.

10.12.6 for life

@mhasman On which vintage of hardware are you experiencing this error?

(In updating to 10.14.3 via a Software Update policy in Self Service, I've noticed what appears to be another firmware update for the hard drive on newer hardware.)

@dan-snelson There is no vintage hardware here :) tested on MBPs model 2016/17, iMacs 2017.

Update via App Store with Software Update works fine, no issue. Downloaded macOSUpdCombo10.14.3.pkg manual installation also works. But the same package deployed by Self Service fails.

I heard this is a known issue where only certain builds of macOS passes their validation check (and others don't). Software Update works, but Apple needs to update logic in their Combo Update package.

The other option involves deconstructing the package and adding validation for other builds, but I'm not getting into that business personally.

It's possible that the Self Service policy is doing a traditional restart when that update might really need shutdown-with-an-automatic-startup. I am very roughly summarizing and interpreting what others have been discussing on Slack. I suspect Jamf may need to add support for the "-R" option that Apple added to the softwareupdate command.

@jhalvorson Why full shutdown is necessary? What deference does it make vs. doing full restart? - Thanks!

This sounds like the combo update issue some have reported in the forums:

https://forums.macrumors.com/threads/apple-releases-macos-mojave-10-14-3.2166339/page-2

@mhasman it might be related to the new security chips in the newer models. Some Apple patches do not require a reboot, some require a restart, and now there are some that require a shutdown.

Might be, but seems unrealistic as the same one package installed on the same computer manually makes Mac restarted, not shouted down

#fullInstallerFTW

@mhasman check out this thread: https://discussions.apple.com/thread/250106871?answerId=250193891022#250193891022

Apparently Apple just pulled the 10.14.3 combo installer and issued a new one.

@sshort Stephen, thank you for letting me know! I appreciate that!

>Apparently Apple just pulled the 10.14.3 combo installer and issued a new one

Seems like it haven't been happen yet. I just downloaded 10.14.3 Combo image; it shows the same .pkg file size, same date Jan 15

The one I downloaded here in Texas is dated January 24, 3:21 pm - 2.51 GB

It may have to do with which CDN you're on.

Be happy to send you this one if you need it.

Maybe just URL, please? If you do Get Info on .dmg file, it shows "Where from" under "more Info"
Thank you!

Here ya go:

http://updates-http.cdn-apple.com/2019/macos/041-32279-20190124-BBE902D6-D788-11E8-B555-8E91F34A5CAA/macOSUpdCombo10.14.3.dmg

I have the same issue with patch management policy to update to 10.14.3
For me it worked fine, also rebooted the Mac automatically. I was on 10.14.2
For a colleague, same HW model, who was on 10.14.1, the update did not work:
Executing Patch Policy macOS
Downloading macOSUpd10.14.3.pkg...
Downloading https://euc1-jcds.services.jamfcloud.com//download/bcdd1517c59d4a1d8334a552e2e1c17a/macOSUpd10.14.3.pkg?token=04dcab1e3297494db21a0677a44e3f8fewmkkj2acqvqk6ctai3itvo3z5lzk2ch...
Verifying package integrity...
Installing macOSUpd10.14.3.pkg...
installer: Cannot install on volume / because it is disabled. installer: This volume does not meet the requirements for this update.

@SGill Thank you for URL!

Yes, it was slightly deferent in size than one I downloaded, and build date was 2 week after.

But seems like it does not fix the issue. Deploying, still get the error in log:

Installation failed. The installer reported: installer: Package name is macOS 10.14.3 Update
installer: Upgrading at base path /
installer: The upgrade failed.

@mhasman Sorry that didn't fix it, but overall you might want to consider retiring the non-local usage of the Apple Combo updaters, both in a policy, and in any Self-Service portal. There have been so many recent changes with what is required for an Apple update to succeed (ie shutdown instead of restart, etc), that is largely better handled by the softwareupdate command set, and the Apple App Store installers. I manage many macs here, and haven't used the combo updaters in years.

Hi all,

My first day of test macOS Mojave 10.14.3 combo update. It fails for me too. I am using the same copy of macOSUpdCombo10.14.3.pkg to update my Mac at home. This was successful on a 2013 Macbook Air and a 2016 Macbook. But when uploaded to our JAMF Pro v10.8, Macbooks in our office install fails via Self Service.

Are we sure it is the macOSUpdCombo10.14.3.pkg that is causing issue? Or something to do with JAMF Pro version? Maybe I need to upgrade JAMF Pro again to make Mojave 10.14.3 combo update work?

@Bernard.Huang Seems like there is nothing to do with Jamf PRO, issue is with Combo PKG somehow.

I have to agree with @SGill. Run this policy as a script that calls

softwareupdate -i ${updatename} -R

Make sure you pop a message to the user that their computer is going to restart, either through Jamf Helper or your preferred method.

Thank you!
I tested that one:

softwareupdate -i -a --restart

What I do not like is each Mac is going to download update from outside instead of using internal distribution point, and that I can not caching the image. When installer is bigger that 1GB, I prefer to cache it in background first, then make the policy available to make sure it installs anyway as package is already present locally.

It is possible to use Server.app to act as a caching server and it will be automatically seen by all machines unless this functionality has been removed. It's been a while since I've set up a machine to do this. Worked well for small environments with limited external bandwidth.