No sweat MP, its a direct issue in the Applications design.
They need to separate Content Browser items for AEC libraries from standard block Palette handling for starters.
I have some suspicions it may be easier with the new strip replacing the dashboard.
Currently Palettes are a pain to handle updating but fairly easy to build.
The Content Browser is just too cludgy and doesn't import and export as nearly well as they claim either for shared content.
Networked items can really bog a system down when they reach these volume sizes as well.
So more or less there needs to be a centralized system created by the enterprise trying to maintain their libraries as local installations.
I've been contemplating local installations of the systems and creating an update utility through the company intranet that runs a file version check. Have it delete the desktop icon and replace it with another pointing to the new profile-Update-ID-##.##.arg
With the actual profile name changing the ID # this creates a new profile seamlessly without the user really having to worry too much.
The problem is capturing some more or less arbitrary preferences and retaining them it proves difficult because Engineers love to tweak and get miffed when their tweaks get wiped. I try to enforce people to save their workspaces, but I still have old school types that have to fight the system, create their own profiles then whine when it isn't working right. I don't have time to crawl into their workspaces with a microscope to trace a bug when I can blow out the profile, retain their workspace, and it works like everyone elses in one command.
Wow I just noticed I'm a Bullfrog, kewl!
I'll have to keep it a secret or the girlfriends going to make demands on my new tongue....