Hello Grad,
So far what I found useful was creating the ABS.cui as my enterprise cui with the users sharing the same profile on the network. In the ABS.cui I placed a few default workspaces as well as all partial cui's loaded. This enterprise cui insures those default workspaces always look the way I intended.
On initial load from startup, even if you select that default workspace you created, some items must still be tweaked locally the first time it is setup. After that, the user can create their own workspaces in their main cui from the initial layouts of the enterprise cui.
I created a central server location mapped drive containing every users own username folder.
i.e.
P:\
(\\servername\personal\username)
This references their main cui file, so no matter what machine they log into from active directory to windows, when they click the custom shortcut, they always get their workspaces.
The menu's I loaded from partial cui's had to be set prior to creating the workspace.
Before I forget, the other advantage of a central networked profile:
I can control custom palettes for all users without the need for manually updating every workstation.
Message was edited by: CCMoor