Logic Extra Content "bundle": how to deploy per-machine location to all users?

I sent the bundle to /Users/Shared/LogicLoops. The Shared folder is easy for permissions management, so I tend to put all shared music libraries in there.
If you download the full library you want to a Test device, you will find you can right click on it and then choose to show package contents. Now you can see what files are in there.
I then used Composer to build 12 installers. I like to keep them under 5Gb in size. Upload these packages to Jamf and set them to install. Just drag them in from the package view into composer.
Once complete you will have the full bundle in one location, and a series of package installers to put them there on any computer.

Next, and this bit you will need to take care with, I am allowed to do it, but I did have to check in with management for it. Some institutions do not allow this sort of thing. I also had to clearly inform the staff of this and what to do.
I have a script, which sits in a policy that runs at every login.

#!/bin/sh


# Checks for the existance of the logic loop bundle, and bins it

if [ -e /Users/$3/Music/Logic\ Pro\ Library.bundle ]
	then
	rm -Rf /Users/$3/Music/Logic\ Pro\ Library.bundle
fi

This script will find and delete any version of the bundle that appears in the users own folder. $3 resolves to the Username.

The Users can choose where to locate and point to the bundle in Logic, So all staff were told to teach their students how to do this and where the central located bundle is.
Did I get any complaints? Yes, right up to me pointing out when they were sent the instructions on how to do it.
Users can pull down their own version, but Logic will put it in the default location, and next time they log in the script will delete it. If they are pointing to the Shared version, and they download something extra, it will work because the Shared folder permissions will allow it, and the new loop should also be available to all Users.

Users have to change where their version of Logic is pointing to for the bundle. I have not found a way to get it done from the server end. As you have found out, changing the location sets Logic off to scan the bundle and find all loops in it. If it hasnt scanned it, then it doesnt know anything about it.

Hope this helps
 

Oh, that's a clever workaround. If I can't figure out how to tell Logic where to look, I'll go with this. Thanks for that.