I pulled the 10.13.2 Combo Updater from here, uploaded the package to Jamf Admin, created a policy to cache it, and then another one to install cached once the updater has been cached.
This has worked for all prior versions of the OS, like the 10.12.6 combo updater, the 10.11.6 combo updater, etc. With the 10.13.2 updater, it caches fine, the second policy sees that it's cached (via smart group) and installs, but the install doesn't work. The log says it's successful, and the MacBook reboots, but when it comes back up it's still on 10.13.0. I tried it multiple times. Here's the log from Jamf:
Executing Policy Install 10.13.2 Combo Updater
Verifying package integrity...
Installing macOSUpdCombo10.13.2.pkg...
Successfully installed macOSUpdCombo10.13.2.pkg.
Checking for patches...
No patch policies were found.
Running Recon...
Retrieving inventory preferences from https://mycorp.jamfcloud.com/...
Locating accounts...
Locating package receipts...
Locating software updates...
Searching path: /Library/Application Support/Microsoft
Locating plugins...
Locating printers...
Searching path: /Applications
Gathering application usage information...
Blessing i386 macOS System on /...
Creating Reboot Script...
And when it comes back up, it's still on 10.13.0. Any ideas as to what's going on here? Obviously we can't have a Mac on 10.13.0 running in our environment, unpatched. I'm currently attempting a manual install of 10.13.2 via software update as a last ditch effort, but I would like to know why the combo updater didn't work from Jamf.
