Sometimes, speed isn't of the essence ...Yes, OSx might be awesome because of the free upgrade to the latest and greatest. But with any software, there's that might in the sentence. It might go sideways too. So why don't we put a pin on that little bugger and wait until the more gullible in the world figure out if they just got hosed?
No. that wouldn't happen. Sometimes, but not to your customers. They just trust you to make sure everything is OK before, well, everything is OK. So you do our own testing, break your own equipment so our customers don't break theirs.
You're babbling Todd, what does this have to do with Mojave?
Right. Sorry -
So let's do a quick breakdown of how the install process works ...
Yup, lifted right from www.MacWorld.com. Sorry guys I just need to get to the good part.Your RMM tool, Kaseya VSA allows you to script anything. So what's more important then the clever explanation above is the things going on behind the scenes.
Mac won't automatically install an upgrade like Mojave, but it will download the files to make it ready to do so. So, let's stop that, shall we?
Here's what you need to write (look really closely so you don't misspell anything!) -
|Click to expand the procedure editor capture|
No you don't have to type it all out, just download the file and import it here -
Then create a View that filters out all your Mac machines and apply it.
This simply looks for, creates, and LOCKS the files necessary to upgrade to the latest release from the Orchard; so now you can make sure your customers don't run into something before you can run into it first.
This procedure should be accompanied with the appropriate communication to your users. After all, they won't be able to upgrade after this has been applied.
Then to "undo" this process, you simply change the Shell Command statements to chflags nouchg and the files will be unlocked.