![]() ![]() You do have the choice of running just the second policy and skipping the first policy (downloading/deploying through a JSS policy), but you would need to ensure that the macOS installer app is already downloaded to /Applications folder through some other mechanism.ĭownloading the installer is the first part we want to take care of. The second policy is meant to run the actual script that will ultimately kick off the upgrade. ![]() The first policy is a custom trigger policy that deploys the macOS installer. There are two policies that this process was designed with in mind, but you can do this in one policy if you want. But do keep in mind that older versions of the Jamf Pro may not have support for the newer versions of macOS. Perform a jamf recon immediately after upgrade.īefore we begin, note that the following script was designed on Jamf Pro v9.97 initially and continues to work through Jamf Pro v10.16.Make sure that the macOS installer app does not have expired certificates.Allow use of an install package that can be used with macOS 10.13+ installers.Provide logging to see where failures may appear.Make use of Jamf Pro script parameters to allow for customization and potential re-use for future operating systems releases.Provide dialogs to give the user feedback such as a time estimate and dialogs on what to expect next.Provide a way for the end user to do FileVault authenticated restarts if possible.Confirm that the volume is not presently undergoing encryption/decryption. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |