Now that we have the packaged Mojave installer and the two scripts in Jamf Pro, we’re ready to create a policy. There’s quite a bit the Mojave installer can do, I suggest checking out the various usages by entering this in Terminal: /Applications/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall -usage Applications/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall -agreetolicense -eraseinstall -newvolumename "Macintosh HD" -nointeraction And it’s a pretty simple thing, really: #!/bin/bash The post install script is where the real magic happens. Otherwise we’re doing nothing… and making a note of either case. So we’re just checking to see if there is a Mojave installer already present, and removing it if so. Note: I probably place way too many echoes in my scripts, but I like feedback for testing. Sudo rm -rf /Applications/Install\ macOS\ Mojave.appĮlse echo "Mojave Installer was not present, so it could not be removed." So the pre-install script is simply this: #!/bin/bash You want to make sure your policy is always installing the latest version of macOS. We don’t want to use an old installer for, say, 10.14.1 when 10.14.3 is out now (at the time of writing this). This way you can have a single Mojave package but have multiple policies to install Mojave.īecause Apple decided that everyone needs Mojave and downloaded the installer automatically to everyone’s machine (ugh), you need to make sure any Mojave install that is already present is erased first. I would suggest NOT bundling these in the package and instead utilizing the before/after script features in Jamf Pro. In addition to the Mojave installer packaged, we need to write two scripts: a pre-install and post-install script. It will take a bit to download, package and upload to Jamf Pro. As previously stated, this is a 6.0 GB file, so the package is rather large. I use Composer since it’s straight forward and easy, but feel free to use whatever packaging tool you prefer. Once you have the full Mojave installer, we just need to package it and upload it to Jamf Pro. We’re just utilizing the built-in tool to grab the full installer. Don’t worry, we’re not doing anything crazy with this. If you’re having trouble getting the full installer to download, check out DosDude1’s macOS Mojave Patcher tool. Just something to keep in mind.įirst, download the Install macOS Mojave.app. One further thing to note: this method only works for APFS formatted drives. This is BY FAR the best way I have found to mass install Mojave which seems to be future-proof in regards to machines with the T2 chip. Well, there’s a really great way to image macOS Mojave (by “image” I mean erase and install) on machines now using Jamf Self Service. Not that there was a great way to do this in the past either DeployStudio had its multicast that was quite the enigma. This may not be too bad a solution for a single machine, but what about a large number of machines? Not exactly a streamlined solution. You have to wait to for your target machine to boot up and then click through the various install screens. Let’s be honest though: this is annoying. Because machines with the T2 chip don’t support netbooting and only support booting to an external drive by booting to Recovery and changing some security settings, most are relying on booting to Internet Recovery to reinstall macOS. With the introduction of the Device Enrollment Program (DEP) and more recently the T2 Chip, we’re treacherously close to the death of imaging (although I can still image most of my machines, more on that another day).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |