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?
Probably I misunderstood. As you are trying to have different workspaces, our approach might not work. We do have different project setups, which do use different datasets.
But a dataset is not the same as a workspace, as datasets still have a common "standards" folder, for example.
In this case I would propose to make copies of the shortcuts of the programs, and change them accordingly. If I am not mistaken you have to add -wrPATH\TO\WORKSPACE to the shortcut.
P.S.: A windows system variable in windows control panel - system.
All my workspaces read the same standards
My users then read different datasets
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
Actually what I finally find works well is to have different mslocal.cfg -one for each Client's workspace - and then add
-wc"PathTo mslocal_XYorZ.cfg" straight after (almost, needs a space) the -ws BB_DISCIPLINE statement...
in the shortcut target for each shortcut. Can't think of another way to launch the software with a choice of Workspace.
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...
Chris, hope this screenshot makes it clear, even if it is from a norwegian Windows 7 system.
Edit Control Panel - System - Advanced - Environmental Variables - System Variable - New - USTN_WORKSPACEROOT
Thanks for the screenshot Andreas, understand. Interesting way to do, first time I come across that one.
I added the _USTN_WORKSPACE variable as mentioned above, and added my adjusted .cfg file
But i still get this message. is there any other varibales to change to get my network workspace configured?!
Thanks in advance
It seems that you have defined the variable not correctly. I assume that you didn't add a slash at the end of the definition.
_USTN_WORKSPACEROOT=D:\Microstation\Workspace\
I solved all problems except the below msg appear whenever I select a new project UPF