Launch via Jamf (or other MDM) policy

[PhillyPhoto]

I created this script to consolidate a few things. First, it calls the custom trigger of the standalone erase-install policy in Jamf so the latest version in your environment is always installed at run time. Then, if it on Big Sur, it will call the custom trigger for SwiftDialog 2.2.1 since newer versions aren't compatible.

It then checks that both erase-install.sh and SwiftDialog are found and reports their versions for logging purposes. It then does some checking around the macOS version that was passed; if it's blank it uses the current version, if it was asking for an older version, it will quit, you can pass sameos as well.

I then threw in a function that outputs the exact command that is going to be run to a file with the date & time stamp in /var/log/erase-install/ (this folder is created if needed). This can be useful if you want to recreate any failures on the machine. The main log file is /var/log/EraseInstallPolicy.log.

Finally, it runs the erase-install script with the flags that work for us and the reinstall/erase flags and macOS versions that were passed in the policy.

Feel free to try it out and modify to fit your needs!

https://github.com/PhillyPhoto/erase-install-policy

[Juub1990]

I created this script to consolidate a few things. First, it calls the custom trigger of the standalone erase-install policy in Jamf so the latest version in your environment is always installed at run time. Then, if it on Big Sur, it will call the custom trigger for SwiftDialog 2.2.1 since newer versions aren't compatible.

It then checks that both erase-install.sh and SwiftDialog are found and reports their versions for logging purposes. It then does some checking around the macOS version that was passed; if it's blank it uses the current version, if it was asking for an older version, it will quit, you can pass sameos as well.

I then threw in a function that outputs the exact command that is going to be run to a file with the date & time stamp in /var/log/erase-install/ (this folder is created if needed). This can be useful if you want to recreate any failures on the machine. The main log file is /var/log/EraseInstallPolicy.log.

Finally, it runs the erase-install script with the flags that work for us and the reinstall/erase flags and macOS versions that were passed in the policy.

Feel free to try it out and modify to fit your needs!

https://github.com/PhillyPhoto/erase-install-policy

It's been months and you probably won't answer but I find sporadically an error where the script fails to overwrite older installers present in /Library/Management/erase-install

2024-02-09 20:14:22 | v32.0 | [find_existing_installer] Installer sparse image found at /Library/Management/erase-install/Install_macOS_12.3.1-21E258.sparseimage.
2024-02-09 20:14:23 | v32.0 | [check_installer_is_valid] Checking validity of /Volumes/Install_macOS_12.3.1-21E258/Applications/Install macOS Monterey.app.
2024-02-09 20:14:23 | v32.0 | [check_installer_is_valid] Mounting /Volumes/Install_macOS_12.3.1-21E258/Applications/Install macOS Monterey.app/Contents/SharedSupport/SharedSupport.dmg
2024-02-09 20:14:24 | v32.0 | [check_installer_is_valid] Using Build value from com_apple_MobileAsset_MacSoftwareUpdate.xml
2024-02-09 20:14:25 | v32.0 | [check_installer_is_valid] ERROR: Installer is incompatible with system
Volume Shared Support on disk3s2 force-unmounted
2024-02-09 20:14:26 | v32.0 | [compare_build_versions] Comparing (1) 21G83 with (2) 21E258
2024-02-09 20:14:26 | v32.0 | [compare_build_versions] 21G83 > 21E258
2024-02-09 20:14:26 | v32.0 | [check_installer_is_valid] Installer: 21E258 < System: 21G83 : invalid build.
2024-02-09 20:14:26 | v32.0 | [erase-install] Existing installer OS version does not match requested OS (14).
2024-02-09 20:14:26 | v32.0 | [erase-install] ERROR: Invalid installer is present. Run with --overwrite, --update or --replace-invalid option to ensure that a valid installer is obtained.

2024-02-09 20:14:26 | v32.0 | [erase-install] attempting to terminate the 'caffeinate' process - Termination message indicates success

I find the cause is that there is a sparse image of an older OS in that folder but it's supposed to overwrite it. In this case, it seems to attempt to mount it and fails.

[grahampugh]

To address both posts:

Erase-install handles swiftDialog versions so you don't have to. If the incorrect version is installed it will grab the correct one.

The package for v33.0 now includes both versions so there's nothing to download.

The erase-install script also outputs the exact command in its output, so you don't need another script to do that.

V33.0 also now ignores sparse bundles so you won't get that error any more.

I'll move v33.0 to production in the next day or two (it's currently in beta).