Our firm utilizes MicroStation CE Update 17 as well as OpenRoads Designer 2021 Release 2, both of these share the same WorkSpace. I want the installation of these products to be as simple as possible for our IT folks, so I have been utilizing the options during setup to point to the Custom Configuration. Once the program is pointing to the Custom Configuration, I want all the other custom items to be handled within the workspace. In other words, I don't want to have to make further adjustments to users local machine to point to different aspects of the workspace.
Everything seems to be working for ORD, but it seems like MicroStation is no longer honoring the ConfigurationSetup.cfg settings pointing the _USTN_CUSTOM_CONFIGURATION variable to the folder that contains the WorkSpace.cfg files. I was then reading about the Manage Configuration included with MicroStation Update 17 and am wondering if it is now conflicting with the .CFG file. This may be a pretty broad question and I'm more than willing to provide additional information to get things on track.
Does MicroStation always defer to the .XML that is edited by the Manage Configuration tool? Or only after the tool is used once? I don't recall this being an issue, but it seems a couple of users are now not seeing the Workspace unless that tool is used to point back to the custom configuration folder manually. This is not something I would like users to do on their own for obvious reasons.
Any ideas?
Thanks,Ken
Here's a link to an informative post and discussion. Seems like it's still aboard the development and refinement train. {(grabs popcorn)}... Configuration Tips - Manage Configuration Utility
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
So from my understanding, starting in MS CE Update 17, the ConfigurationSetup.cfg is ignored in lieu of the .XML. Let me know if I missed something about this discussion.
Thanks!Ken
Good morning gentlemen,
Yes, you are both correct. I see that we have made at least one tweak in MicroStation 17.2 but have not checked that out yet. My blog will be updated.
Please feel free to ask further questions here.
Marc
Marc,
I added the question to the blog link above as well, but just realized you requested to ask questions here instead. So here is the question again in this post.
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?
Hi Ken, thanks.
What happens if you leave _USTN_CUSTOM_CONFIGURATION empty and hardcode _USTN_USER_CONFIGURATION?
I'll go back and check this too.
When I do that and just code _USTN_USER_CONFIGURATION directly to my networked configuration, I still get the Manage Configuration and I lose my custom workspaces.
In my ConfigurationSetupo.cfg I have:
[General]_USTN_USER_CONFIGURATION_LABEL=_USTN_CUSTOM_CONFIGURATION=_USTN_USER_CONFIGURATION = D:\_ClientFiles\<folderName>\Configuration\
[SetConfiguration]%if !defined (c)%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))_USTN_CONFIGURATION = $(_USTN_INSTALLED_CONFIGURATION)%endif%endif
Resulting in this:
The sole active configuration is listed as 'User Configuration'. (Setting a label for the configuration using the _USTN_USER_CONFIGURATION_LABEL variable does not change this. I've filed bug 808373 about this, I would expect it to show the label.)
Which U 17 version are you using?