How to make the packages

[Danberms]

I'm looking at trying to use your script and have a couple questions.

Is the difference between Forced, Self Service, and Classroom is that Forces is for a policy to auto trigger the scripts and start the install, Classroom to be started by a tech on the machine to run without intervention, and Self Service for the end user to start the install when they are prompted.

I see references for the QuickAdd.pkg and the OS installers to all be in the /tmp folder. How are you getting them there? Are the separate policies setup to do a Cache install of the app? Or are they full installs. Are the packages for each setup to drop the files into /tmp? Are you just using composer to make these packages?

[MLBZ521]

Hey @Danberms,

Sorry for the delay, I don't get notifications for issues unfortunately.

For the Forced, Self Service, and Classroom options, yes that's the general idea. However, after testing I do not believe Forced will actually work.

For the packages, yes, you could just use Composer, or any other method to create the packages to drop the files in /tmp. I have a Policy for each OS Version that "installs" the files to this location. This script, install_macOS.sh, calls the Policy for the specific OS Version desired via custom event/trigger.

I have plans to revise this script hopefully in the near future, just haven't had time with some other projects I'm working on.

[scriptsandthings]

I'm looking at trying to use your script and have a couple questions.

Is the difference between Forced, Self Service, and Classroom is that Forces is for a policy to auto trigger the scripts and start the install, Classroom to be started by a tech on the machine to run without intervention, and Self Service for the end user to start the install when they are prompted.

I see references for the QuickAdd.pkg and the OS installers to all be in the /tmp folder. How are you getting them there? Are the separate policies setup to do a Cache install of the app? Or are they full installs. Are the packages for each setup to drop the files into /tmp? Are you just using composer to make these packages?

Flatten your QuickAdd.pkg
productbuild --package /path/to/installer.pkg /path/to/installer_flattened.pkg
Sign it with an Apple Developer ID cert - I used Handcock.app to sign it once I got the cert from developer.apple.com
Make composer package that places your signed QuickAdd.pkg in the path of your choice
I add that to my erase/re-enroll install_macOS.sh policy with priority of 1 so it only does the QuickAdd for that specific type of install via self service.

https://github.com/ShitttyScripts/install_macOS
My branch/push request has Jamf params to customize where you place the QuickAdd.pkg