Skip to main content

So today we are packaging GarageBand 6.0.5 (current version) for deployment, using a multi-user redemption code purchased by the company of course.



On first launch it goes out and downloads roughly 1.2 GB of "extra content"...bah.



I didn't see it in Composer under Pre-Installed software, even after installing GarageBand and letting it download the "extra content".



So I'm using Composer (surprise, ey?!) to take a snapshot in the hopes of capturing the "extra content" for deployment, I really was hoping not to have to do that. :(



I'm noticing it pulled down a bunch of stuff to:



/Library/Application Support
/Library/Audio
/Library/Preferences
/Library/Printers
/Library/Receipts
/Library/Updates


I also noticed the snapshot captured stuff in:



/Users/testuser/Library


I'm hanging it up for today, before I begin work on this tomorrow, do I need to include the stuff in the /Users directory? If so it's easy enough to deploy with PKG and loop script, but hoping not to have to. :)



TIA
Don

I am not doing FUT or FEU with my 6.0.5 GarageBand AddOns DMG.


I had to do the same thing, but sort of regret not trying other things as this makes for a big package. I packaged mine as a DMG with FUT/FEU. Next time it updates, I am going to try to break it into 2 packages and see how it goes.



Packaging the app without the extra content should make upgrading easier down the road, as well as enabling you to be more nimble with your deployment.



According to /Users/user]/Library/Preferences/com.apple.garageband.plist, the content is located at [http://downloads.apple.com/static/gb/gb11bc/GarageBandBasicContent.pkg. I would think that this could be dropped right into Casper Admin and deployed along side the app without the need for any scripting.



If you go this route, I'd love to hear about the results.


@ernstcs and @msblake Thanks! I tried to find the file when it downloaded, but didn't have any luck. I'm downloading it now, will test tomorrow (along side the snapshot test).



I read somewhere that the GarageBandBasicContent.pkg package doesn't always push cleanly, as I discovered at the end of the day today. It was as if Ruth Ann Buzzi wound up and smacked me with her purse. Maybe it's one from the Package Apocalypse era?



http://managingosx.wordpress.com/2012/03/24/fixing-packages-with-expired-signatures/



I'll shout back after testing the package that @msblake pointed me to, and also the snapshot (if the former doesn't work).



Thanks,
Don


@donmontalvo



There are two packages that I found on my ASUS



There was one that was called GarageBandBasicContent.pkg (1.57GB) and another that was called GarageBandExtraContent.pkg (1.2GB)



Now they both have different stuff in em too. Once has a bunch of extras while one is just the instrument library



GarageBandBasicContent



external image link



GarageBandExtraContent



external image link



So I dragged both of these packages to composer, converted to source and then merged them.



Created a DMG and I then just add that to my imaging workflow and I have no troubles with Garageband asking for extras.


@rpotvin Danke! I'll check SUS for those.



Don
Schweinfurt 1983-1985


<dupe>


I had good luck with dmohs' method in https://jamfnation.jamfsoftware.com/discussion.html?id=679


Perhaps this is of interest:



http://afp548.com/2012/08/07/garageband-deployment-quick-tip/


Wow you guys are awesome! These are almost done downloading, got a late start:



http://downloads.apple.com/static/gb/gb11bc/GarageBandBasicContent.pkg
http://audiocontentdownload.apple.com/lp9_ms2_content_2011/MGBContentCompatibility.pkg



I'll have to test first thing on Monday, I guess I'll need to sort out which order the patches are applied after the GarageBand package is installed.



I will shout back with results. :)



Thanks,
Don


Hey Don,



Did you sort out the order of the patches? Were you able to successfully deploy the content after downloading from the links you provided?



Thanks,
Curtis


Yep, we're pushing the latest GarageBand.app and we're caching/installing GarageBandBasicContent.pkg and MGBContentCompatibility.pkg using a post-installation script. No hiccups...and when GarageBand.app update is released by Apple, our packaging workflow makes it a breeze to update our existing package (using Packages).



Don


Thanks Don! Do you mind sharing your script?


installer -pkg /path/to/package/pkg -target /

Like @donmontalvo, I use Packages to create my installations. In Packages, you add GarageBand.app into /Applications in the Payload and the extra content files into Additional Resources, then add a postinstall script like the following to initiate the installations.



#!/bin/sh

/usr/sbin/installer -pkg GarageBandBasicContent.pkg -target "$3"
/usr/sbin/installer -pkg GarageBandExtraContent.pkg -target "$3"
/usr/sbin/installer -pkg MGBContentCompatibility.pkg -target "$3"

exit 0


This can also be done in Composer with a little work.



Copy GarageBand.app into Applications and the extra content files into a temporary folder (I always used /tmp) then add a postinstall script like the following to initiate the installations.



#!/bin/sh

/usr/sbin/installer -pkg "$3/tmp/GarageBandBasicContent.pkg" -target "$3"
/usr/sbin/installer -pkg "$3/tmp/GarageBandExtraContent.pkg" -target "$3"
/usr/sbin/installer -pkg "$3/tmp/MGBContentCompatibility.pkg" -target "$3"

rm -rf "$3/tmp/GarageBandBasicContent.pkg"
rm -rf "$3/tmp/GarageBandExtraContent.pkg"
rm -rf "$3/tmp/MGBContentCompatibility.pkg"

exit 0

The /tmp directory is purged at reboot.


I know, but it's a habit that I don't mind. In some cases, the information contained in those files could be sensitive, and it could be weeks before the machine is restarted.



Plus, I just don't like leaving remnants.


Wow, thanks a ton @msblake and @donmontalvo! Thanks for turning me onto Packages. I have been trying to do everything with Composer but I can see where Packages can save me a few headaches.


What is MGBContentCompatibility.pkg for? Is it needed for Magic GarageBand in general or only for compatibility with certain other programs?


It's a compatibility pack between Magic Garageband and Logic Pro.


Ah, I thought that might be the case. Thanks!


@rpotvin, & all.. if the content can be found on your ASUS will the clients pull it from their ASUS?



Just looking @ this myself, deploying the .app via Self Service seems fine.. if the additional content is from the macs ASUS then i'm done.


Sorry, newbie here....What are you guys talking about when you reference using "Packages" to create these push-outs. I am familiar with Composer and that's about it so far.


Packages is an application to create an installer package, you can download it from http://s.sudre.free.fr/Software/Packages/about.html



GarageBand 10 Extra Contents can be download from the following links and use Packages to create an installer package:
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GarageBandCoreContent.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GarageBandPremiumContent.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GB_StereoDrumKitsSongWriter.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GB_StereoDrumKitsAlternative.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GB_StereoDrumKitsRock.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MAContent10_GB_StereoDrumKitsRnB.pkg
http://audiocontentdownload.apple.com/lp10_ms3_content_2013/MGBContentCompatibility.pkg


Reviving this old thread...does anyone have the latest download URLs for GarageBandBasicContent.pkg, MGBContentCompatibility.pkg, and the loops stuff?


Reply