If you Set view options to calculate all sizes, you are looking for the really fat folders.
#DOWNLOADING GARAGEBAND FOR MAC INSTALL#
this is then just like they have been installed by the App and thy fill in their install receipts with the apps properly. You can copy these away to a safe location and then put them into Jamf Admin to install. If you say yes to this, but do not put in your admin password when it asks for authorisation to install, you will find that it has downloaded all of the original installer pkg files for the libraries. If you run GarageBand or Logic after a fresh install, it will want the Libraries to be installed. I hope that helps or at least point you in the right direction When it comes to checking in that the package has installed and then deploying the app, you could make this more of an automated process by making use of smart groups. Since the additional content is already on the machines GarageBand will have all the content and extra sounds. Once this package has been installed on the target computers then install the GarageBand App through VPP as usual.
Package the contents of these locations or at least the locations that have content in them using Composer or which ever tool you useĬreate a policy to deploy this package to your target computers but remember this might take awhile since you’ll be looking at ~20gb worth of content. Once installed they should be located in any or all of these places (last time I checked) Open up GarageBand and download the additional sounds On a test machine download GarageBand through the Mac App Store Would you not want to deploy the actual app through VPP?Ī workflow that we have used in the passed for Logic, and should work in the same way for GarageBand is