Working off a networked Workspace for one specific client (we do outsourcing), our current setup is through the mslocal.cfg pointing to the shared workspace.
However in future each new Client is highly likely to have their own Workspace with own standards and Datasets etc.
Editing the mslocal.cfg for each Client Workspace does not seem very practical although for the moment I cannot find any other way....Any suggestions out there?
We do it by setting the Windows variable _USTN_WORKSPACEROOT to the networked workspace.
This is the only thing which is done on the client, the rest is configured on the server.
No need to do anything when a new Microstation is installed on the client either.
I mean i want each user to have the choice of workspace - choose between 4 or 5 diferent workspaces typically...
What do you mean by "Windows" variable anyway?
Eric, understand your way but I do need full independant Workspace per Cient, each have their own standards etc.
Andreas, still completely unclear on your Windows Control Panel thing - aside from the fact that I am reasonably happy with my solution of individual shortcuts, still curious...
Bear, I have no idea why this is the case. Look forward to read your ideas on subject anyway.
I got cha.
There probably is many ways to do it.
I could have a full standards file but right no only two lines
And all the users point to what I'd need. If they needed a different dataset a single setting change and it would be done.
I am playing with this now as for years I've had just one standard file and nothing else. then years before that only the msconfig file.
My big but slow process is to figure this into three groups.
Standards for all
User Config per project group or client, or maybe even year.
then Job set for very few items I don't want to use.
I've got the idea but it is slow growth.
Ustn since 1988SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64bEric D. MilbergerArchitect + Master Planner + BIMSenior Master Planner NASA - Marshall Space Flight CenterThe Milberger Architectural Group, llc
Sure Eric, understand. However I find that in the end a lot better for me to have the entire Workspace per AECOSIM Building Designer Client - in outsourcing, our Clients send their own data (full Workspace inc. Building Dataset, Company Dataset Extensions etc) and it would really be way too complicated to try and accomodate all that in one Workspace - in fact probably impossible since they often have their own "includes" at site level - added .cfg etc etc etc
But I find now that a software shortcut per Client is not bad at all, I can then link that to my office management system based on job number and force a shortcut depending on job number... Reasonably user friendly - considering how user UN-friendly Bentley products generally are...