@richies113 I would like to create a policy to upgrade to 10.14.5 what do you currently have in place to accomplish this?

I uploaded the .dmg to JAMF via JAMF Admin and even created a policy it says it installed but if has not.

Executing Policy macOS Patch Updates
Downloading https://use1-jcds.services.jamfcloud.com//download/19727f945eb74fb797d9d257fa52498e/macOSUpd10.14.5.dmg?token=689de70203904bb682ed91ae0e0e233b7tp5sgnys4g0rvbs9zg6eegbns35y4py...
Verifying DMG...
Verifying package integrity...
Installing macOSUpd10.14.5.dmg...
Closing package...
Blessing i386 macOS System on /...
Creating Reboot Script...

I want to deploy this, I even tryed issuing the command to download and install via a action and that did not work.

I really wish there was a way to force this update without user interaction.

@richies113 you could also deploy the software update policy or send the update OS software command through ARD to the workstations.

Hello Guys, am a newbie with almost the same problem. I have Mojave.app update sitting on /Application folder. My problem is to run that update through Policy. Hoping for your suggestion.
Thanks

for upgrades I run this command "Files and Processes" ..

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

For wipe and reload add --eraseinstall before --application

Here's my solution: https://babodee.wordpress.com/2019/11/05/revisiting-a-macos-upgrade-method-using-jamf-pro-self-service/

I know I'm resurrecting an old thread, but I am running into an issue with Self Service.
Installer is installed in the Applications folder, no worries. Run /Applications/Install macOS Mojave.app/Contents/Resources/startosinstall --agreetolicense --nointeraction through a Self Service policy, logged in as local admin, no worries.
Self Service fails to quit, which means the whole thing falls over. What do I do? I can't include a command for it to quit, because that would kill the process, right? I'm pulling my hair out!

EDIT: I found the solution! In this thread. Should have gone through a bit slower, but that's not my style. Thanks to @therealmacjeezy for the but of script I needed and@dmitchell for posting it!

If anyone is wondering, here you go:

# Runs the startosinstall binary to start the upgrade
"/Applications/Install macOS Mojave.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS Mojave.app" --rebootdelay 0 --nointeraction --agreetolicense

# Pulls the current user
currUser=$(scutil <<< "show State:/Users/ConsoleUser" | awk -F': ' '/[[:space:]]+Name[[:space:]]:/ { if ( $2 != "loginwindow" ) { print $2 }}      ')
currUserUID=$(id -u "$currUser")

# Kills self service to allow the installer to continue with the update
/bin/launchctl asuser "$currUserUID" sudo -iu "$currUser" killall "Self Service"

# Exits the script
exit 0

@a.holley I get a little over anxious too! Thanks goodness I'm not the only one! ; ) Thanks for your post. We're using the kc9wwh/macOSUpgrade script to do our Sierra to Mojave upgrades and stuck at Self Service not quitting out too. Where in this kc9wwh/macOSUpgrade script would we add this kill self service string?

# Kills self service to allow the installer to continue with the update
/bin/launchctl asuser "$currUserUID" sudo -iu "$currUser" killall "Self Service"

I already queried on one thread but replicating here for relevance and redundancy to ensure anyone who has a solution sees it and posts it:

Has anyone come up with any good ways of getting upgraded to and/or deploying a current 18G2022 build of Mojave that don't involve multiple layered policies and smart groups and packages? The latest full installer is only 18G103, and then Security Update 2019-002 needs to be applied to that, along with Safari 13.0.4 and other updates as will no doubt come out down the road; it would be nice if Apple supplied something akin to the old Windows rollup releases or provided a way to "slipstream" the latest updates so that user downtime for upgrades and tech wait time for clean installs was minimized.

In our environment we can't just use Apple's Software Updates, we end up pushing the SecUpd2019-002Mojave.pkg to any Mac that has Mojave but isn't running build 18G2022. Unfortunately, while systems seem to get updated, they report to Jamf that the upgrade has failed.

I was disappointed that running this didn't work for a clean build - it feels like it ought to, but as with all things Apple does lately, this is not the way:

/Volumes/Install macOS Mojave/Install macOS Mojave.app/Contents/Resources/startosinstall  
--agreetolicense --volume /Volumes/Macintosh HD  
--installpackage /Volumes/Install macOS Mojave/SecUpd2019-002Mojave.pkg

It yields an error:

macOS could not be installed on your computer ERROR_ABA5BBBB51F Quit the installer to restart your computer and try again.

Unfortunately this Mac that I experimented on had to be restored via Internet Recovery.

I have followed the steps (as posted by boon12345 on 11/18/2018 above - really helpful by the way as I have NEVER done this before and needed the step-by-step) to set up the smart groups, create/paste the script, and set up all the policies. The High Sierra (or Mojave) app installs properly on my test device using the first policy. However, when I run the second policy, which runs the script (macOSUpgrade downloaded today 2/6/20 on GitHub), all I get is the message:
Error Downloading macOS High Sierra
We were unable to prepare your computer for macOS High Sierra. Please contact the IT Support Center.
I did not modify the script at all. Is there something I am doing wrong? Any help is greatly appreciated!

Random question for anyone: using the method from kc9wwh/macOSUpgrade - it has worked amazing. I have been able to successfully deploy this update using 2 policies, one for the pkg file of the installer and the other containing the script. I've been able to update multiple Macs off our university campus network since many are working from home. I have 150 iMacs now to update on campus. The pkg file pulls from the SMB share just fine, but then the script calls out to Jamf Cloud based on the network logs and I know scripts are stored in the database. During testing, I have only done 5 Macs one at a time and I am ready to do the remaining 150 on campus. Has anyone who has used this specific method (or any scripted macOS upgrade method) notice any networking issues or a major impact on their network? Jamf Support says it should not have any impact on the network for this many Macs. Trying to plan accordingly and am open to any tips. Thanks!