Updated version of this article, which was originally posted on 18 Aug 2017
In CONNECT Edition - Custom Configuration - Part 1 : Initial Creation Steps I described how the installer can be used to specify the location of your Custom Configuration by setting the value of the variable _USTN_CUSTOM_CONFIGURATION listed in "C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetup.cfg" to the chosen Network Configuration path; e.g.: \\hal\CONFIGURATIONS\MCE.
This results in the WorkSpace menu showing both the custom configuration and the delivered example configuration:
If you do not wish to expose the delivered example configuration we have a related variable, _USTN_USER_CONFIGURATION that can be used to show only one configuration. This configuration can also be given and appropriate name, in this example SMB Projects (from MicroStation Update 15 onwards):
For all users this can be enabled simply by adding two line to the [General] section of "C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetup.cfg":
Specifying the path where the custom configuration is located and applying a label, e.g.:
#----------------------------------------------------------------------# START: The section defines user selection at the time of installation.# These lines are generated by installer.[General]
_USTN_USER_CONFIGURATION_LABEL = SMB Projects_USTN_USER_CONFIGURATION = D:/_SMB/SMB_Resources/
[SetConfiguration]%if !defined (_USTN_USER_CONFIGURATION)%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))_USTN_CONFIGURATION = C:/ProgramData/Bentley/MicroStation CONNECT Edition/Configuration/%endif%endif
As the [SetConfiguration] section opens with an 'if undefined' logical statement (in the %if !defined operator the '!' is NOT), the nested statement specifying _USTN_CONFIGURATION is not processed. _USTN_USER_CONFIGURATION is then the variable that specifies the location of the Custom Configuration.
Note: the original version of this post described defective behaviour:
In early releases of CONNECT Edition that variable added a third option to the WorkSpace menu, User Configuration, as shown below, which I suggested could be useful for administrators, this is was not a designed behaviour and is no longer available.:
Translated German Wiki articles:CONNECT Edition - Was bewirkt _USTN_USER_CONFIGURATION?
Thanks for clarifying Marc, if not a little disappointing. The original behaviour was much better from an admin/testing point of view. As it stands I have to edit my cfg file each time I want to swap
Hi Duncan, the behaviour originally described was a defect, the behaviour that you have found is the intended behaviour, I have updated the article to reflect this.
Hi Duncan, you are correct. This is no longer working as I found when writing this post. Having looked at this one I think the behaviour you are seeing is the original design intention. I am discussing with colleagues and have filed Defect 1095759 to get it checked out. I've added a note at the head on the post.
If I define _USTN_USER_CONFIGURATION it overrides my custom configuration, what do I need to do to get the workspace drop down to display the 3 configurations as you show above, or evne jut custom and user?
I used to have this but seems that in recent versions if USTN_CUSTOM_CONFIGURATION is defined and exists then it overrides and hides the installed example configuration, and if USTN_USER_CONFIGURATION is defined also it overrides both.