MicroStation Update 17 includes the new Manage Configuration utility. This enables MicroStation to switch between multiple configurations allowing further control and separation of standards for organizations working with serial clients or on major projects that require specific CAD/BIM standards.
This is equally beneficial for smaller organizations as this feature can support accessing, with minimal technical input, an entirely self-contained configuration supplied by a third-party.
For administrators, even when they are only managing a single configuration, it enables them to easily switch between production and development configurations.
Where a Custom Configuration is already used by Update 16, during an upgrade to Update 17 MicroStation picks up the path to this configuration from ConfigurationSetup.cfg and will list it with the Example configuration in the new Configuration panel:
If you install Update 17 and do not see your previous configuration, either nothing:
or only the Example configuration:
this will be because the previous ConfigurationSetup.cfg was not found. This can happen if a previous version is uninstalled and all remaining folders and files are deleted, whether manually or by an IT system process.
In this case simply launch Manage Configuration and click Add following the steps in this video (once the new configuration is created in the first few seconds the video goes on to show switching between configurations):
The required inputs, shown in this video, are a name and description that will appear in the UI, the choice of Custom Configuration location, the path to the Custom Configuration. This path is to the Custom Configuration root folder that contains WorkSpaceSetup.cfg. Ensure 'Visible' is ticked, if it is not the configuration will not be listed in the UI.
Clicking the Workspace Setup toggle displays the active configuration variables in the existing WorkSpaceSetup.cfg. These do not need to be changed to use an existing Custom Configuration.
Documentation is here for Update 17: Creating and Managing Configurations.
Configurations are stored in C:\Users\...\AppData\Local\Bentley\MicroStation\10.0.0\prefs\configuration.xml.
This file can be copied to any users provided that the path(s) stored in the XML for each configuration is/are valid for each user.
Each configuration is contained in a <ConfigurationModel> tag pair. The values entered in the Manage Configuration utility are stored in a similar order to the dialog:
Configuration Name: <Title>SMB Config</Title>Description: <Description>SMB Demo Config</Description>Set by application: <ConfigurationVariable>_USTN_CONFIG_SMB_Config</ConfigurationVariable>Type: <Type>Local</Type>Visible: <IsActive>true</IsActive>Configuration Folder: <Path>D:\_SMB\SMB_Resources\</Path> <IsSelected>true</IsSelected> <IsEditable>true</IsEditable>
Additional values set by the application are IsSelected, which identifies the user selected configuration and ConfigurationVariable, which is is an an identifier used by the application.
IsEditable is set by default to true for new configurations but set to false for the Example configuration to ensure new users have access to the examples for learning purposes.
The example configuration can be hidden by editing the XML, set the IsActive statement to false:
In MicroStation 17.1 we can use _USTN_USER_CONFIGURATION to hide the Configuration Manager and all configurations listed in configuration.xml. This is an interim step. The ability to hide Configuration Manager while making pre-selected configurations available for use is being worked on for MicroStation 17.2.
When _USTN_USER_CONFIGURATION is directed to a configuration path that configuration is the only one that will be visible in the UI, similar to its previous behaviour.
it gets even better....it's different depending on the number of versions as well. For instance, if you have multiple ORD versions, then you may have 10.0.0, 10.0.0_1, and 10.0.0_2.
I am attempting to disable this in MicroStation so I adjusted the MicroStation ConfigurationSetup.cfg to be:
_USTN_CUSTOM_CONFIGURATION = (networked configuration path)
_USTN_USER_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION)
When I restart MicroStation, I am still getting the Manage Configuration options. Where should I put this so that it disables this?
Yes, it appears to be placed per Product. I haven't checked OpenRail or OpenBuildings yet.
does everyone realize where this file gets placed ? as Marc says you can use windows or manually control this.
but - there is another twist to this. This file seems to be per product. So if I have MicroStation and ORD (for example) - I have two separate folders for the preferences. So there will be two separate XML files.
Has anyone else encountered this ?
I must say this is a REALLY bad way of implementing this level of configuration.
I understand the reason that the Examples Configuration is locked is to ensure that MicroStation based applications are always installed with at least one operational WorkSpace.
There is a note on how to change this in the "Manage Configuration XML Syntax" section above:
The example configuration can be hidden by editing the XML, set the IsActive statement to false: <IsActive>false</IsActive>
As discussed above and in the comments, the modified configuration.xml file needs to be distributed to all users. This can be done using Windows Account Policies or by a manually initiated batch file similar to the one described in CONNECT Edition - Deploying or Updating ConfigurationSetup.cfg.
Why is the examples configuration locked and cannot be hidden or deleted? I already have problems with my users using the MetroStation workset in Opencities MAP PowerView but at least we can "remove from list". Costs us money in wage loss every time a user plays around with something like this rather than getting to the real work.
While not used to open the software it still seems to be used when running the Configuration Explorer. At least in my experience. I was trying to use the CE to track down an issue causing dgnlibs to crash when opened with a workspace and found the CE doesn't know where to look unless the local ConfigurationSetup.cfg is pointed to the correct location on the network.
I eagerly await more documentation on this topic. Has anyone considered either a coffee corner or even Learn Server Training Session(s)?
And how does a Nov. 2022 Blog post have questions from 5 months ago? I was pleased to see the answer to Jon Summers question about the file "ConfigurationSetup.cfg" - I had come to that conclusion on my own but was a bit surprised about the lack of any detailed explanation (warning?) when this was implemented. Granted, it was introduced to me via Open Roads Designer, which also made it seem even more obscure as it was not addressed in the Open Roads help, but only in the MicroStation help.
I can only support the request, that this should be configureable and centralised.Having this file in the localappdata is difficult to manage in a company.
Is there a seed file for the xml-file: C:\Users\...\AppData\Local\Bentley\MicroStation\10.0.0\prefs\configuration.xml.
Where are the defaults stored?
What was updated for Manage Configuration Utility in MicroStation CONNECT - Update 17.1?
I upgraded to Update 17.1, and cleaned out user preference files (prefs folder)
Now user only has options to select example workspaces/worksets delivered with the product... and no "Manage Configurations"
This does not allow users to access our workspaces/wporksets on the network....
If I restore the user prefs (from previous version), "User Configuration" will show up and user can access our networked workspaces/worsets
I guess I could go back and manually edit the configuration.xml file (local) - to get the "user" configuration back, but this seems counter intuitive...
Could this feature be set as a Technology preview for the next builds while Bentley fine tunes the implementation of it?
Hi MarcAs per the others feedback, this needs to be added to a configuration variable, so CAD Admin's can select the location. Having this file located within the user C drive profile is a pain
I agree this is yet another layer of choice that the user at the coal face has to decide on, and that is not ideal - especially when users generally don't/can't keep up to date on every new feature.
However as a background admin tool I would love to see configuration more generally turned into an organised "database" structure that allows an admin to control configuration in one place rather than chasing several CFG files. It is undeniably tedious to track down what a variable is doing when having to hunt through several CFG files that usually follow their own internal order.
If Bentley is listening -I can see a future Config Editor that is able to take several XML based config files and mash them together in one editor interface. Much like the way OpenBuildings Designer mashes together several XML files to form a dataset, and presenting a single structure to the admin.In this single editor interface it would be far easier to visualise and juggle what order/level(s)/values variables are organised in. The interface would then save out to the separate files for Organization / Workspace / Workset / etc to maintain that flexibility & power we have now with the mixing and matching of CFG files.
XML is still human readable (like CFG), but can come with a schema that would help keep the structure true. Tags could include - <Variable Name/> - <Variable Value> - <Variable Type/> (is the variable a path, path list, file name, filename list, boolean, text, integer, etc.) - <Processing Priority> (%level) - <Description/>
However I admit I am not sure how logical conditions could be handled with this format (%if etc.) so perhaps this editor interface would only be able to evaluate things from the perspective a specific workset... much like the Configuration Explorer currently does.
But I just don't understand the logic behind this xml file. It breaks everything a CAD admin wishes for. We have data segregation at Organization / Workspace / Workset. We were told that's the CONNECT way. Now this xml adds another layer "CONFIGURATION?" into the mix.
I understand the appeal for the ease of switching workspace/workset in situ, but if you have hundreds of CAD operators in the building, "ease of switching workspace/workset" is deffinitely not what a cad admin wants.