[U17] Missing Manage Configuration

We are actually using Open Roads, but this is not specific to Open Roads. On my PC, my initial screen offers the Manage Configuration button/menu. But on a few other users, there is no option to manage configurations. I looked at the variable MS_CONFIGURATIONOPTS and found it in the list twice.

One shows it as a User Level, defined as [Null] but the second one appears as Level Undefined. And only the Undefined version contains a Detailed Description.

These seemed to be identical on all PC's. But one has the ability to use the Manage Configuration tool and the others do not.

I also noticed that by default, the Training and Example workspaces are no longer available in the list. on any of the PC's.

Finally, the Manage Configurations appear to be very volatile. I have been testing a number of configuration file edits and have had my Configurations suddenly disappear from the list. They are reasonably easy to add back in, but this is not something I want to need my users to become skilled at.

I should point out that we generally use ProjectWise and Managed Workspaces, but we also have some users using local or network-based files and workspaces.

  • Are you talking about the Managed Configuration my screenshot shows at arrow 1, or Create WorkSpace (and Create WorkSet) shown at arrow 2?

    If it's position 1, then that is version dependent. ORD 10.10 does not have it, but  it is there in 10.11 and 10.12. The configurations shown here are controlled by the configuration.xml file in the user's preference directory (one of the numbered folders under C:\Users\USERNAME\AppData\Local\Bentley\OpenRoadsDesigner)

    MS_CONFIGURTIONOPTS only controls the Create WorkSpace/WorkSet options under the WorkSpace & WorkSet dropdowns (arrow 2)

     

  • In addition to Kevin's post, it could be related to _USTN_RESTRICT_MANAGE_CONFIGURATION = 1 mentioned in this thread



  • Thanks Carl, 

    The next question is where to set _USTN_RESTRICT_MANAGE_CONFIGURATION = 1?

    One candidate is setting it as a Windows Environment Variable which can be implemented by Windows policies.

    Otherwise it would need to be added to "C:\ProgramData\Bentley\<applicationName>\Configuration\ConfigurationSetup.cfg"  but this file can be edited by the knowledgeable user.

    From MicroStation 2023 this can be combined with MS_CONFIGURATIONXML_PATH to redirect MicroStation to a shared configuration.xml, e.g.:

    MS_CONFIGURATIONXML_PATH = D:/_CONFIG_XML/M23/
    _USTN_RESTRICT_MANAGE_CONFIGURATION = 1

    Regards

    Marc