Connect edition 17 - How can I remove unwanted configurations from GUI?

Same problem here.  So annoying!!!

We have deployed without example configurations so this option is pointless.  And users have to manually select custom config each time on start which is just another thing we have to explain.  

Does nobody at Bentley test this stuff in real world situations?

After I created another Configuration, there will be a file configuration.xml under folder C:\Users\<UserName>\AppData\Local\Bentley\MicroStation\10.0.0\prefs. Open this xml file and change the default configuration's tag <IsEditable>false</IsEditable> to <IsEditable>true</IsEditable>, then you can hide the default configuration. Below is my StartScreen with two configurations hidden.

Whose brilliant idea was this, and where is this significant change (and "fix") documented?

Bentley needs to understand that most of us at a company of any reasonable size use networked configurations. Adding requirements to control the user experience at the local level is inefficient at best. If there is a CAD manager, it could take them hours to go through every users' computers - IF they have physical or remote access to the users' computers at all. If the CAD is "managed" by someone of lesser authority (like just an experienced user) it gets more complicated. I love my teammates, but I don't want them making changes to application resource files.

Workspace/workset management is a huge part of deploying and enforcing standards. Options like this need to have a way to manage them at a higher level than "user".

Is there a way to "network" configuration.xml, or does that file HAVE to be local?

Stirling, the answer is "No". I don't think anyone at Bentley has used their own software in a production capacity in a decade. Surprisingly few seem to be left who have done production work at all, and the developers are definitely not talking to them.

Hi Tim,

I totally understood your pain if you are managing 200 workstations. I am searching a more convienient way to turn off this new  multiple configurations feature. It seems can be implemented by setting a token file.

Waiting me for digging into deeper.

Personal thinking, this new feature seems extend the management layers from two(Workspace/Workset) to three(Configuration/Workspace/Workset).

Yea, whatever. I've instantly figured out this is something else I need to just ignore. I can only guess this is for folks who don't want the Workspace assigned with the Workset or are confused by that behavior. Be nice if you'd just focus on getting rid of the multitude of bugs.

You did fix the odd behavior of the Power Select backwards functioning.

Yongan.Fu said:

Personal thinking, this new feature seems extend the management layers from two(Workspace/Workset) to three(Configuration/Workspace/Workset).

I like the concept of adding another configuration layer, but not managed by a user-specific file in the user LOCALAPPDATA folder and not something that is automatically on for everyone.

I have clients that use a combination of MicroStation and ORD where the MicroStation users use the same Configurations as the ORD users. For ORD you can redirect to different configurations based on the version, MicroStation you only get one. 

Using this new feature you can make ORD 10.9, 10.10, (and eventually 10.11) configurations available at the same time in MicroStation from the WorkPage.

I think you have mis-worded what the new feature is. It is not an extended management layer because management has always been able to work with this (in the background). This is an exposer to the user to now have an additional choice in the interface.

Due to some difficulties with some client DOTs I have to keep complete configurations separate from others. I have these load in various ways (desktop icons, etc...).

With this new feature it will be possible to have the user access these from one interface.

The problem with what has been created here, is that this is controlled from the user and not management.

I think you have mis-worded what the new feature is. It is not an extended management layer because management has always been able to work with this (in the background). This is an exposer to the user to now have an additional choice in the interface.

Due to some difficulties with some client DOTs I have to keep complete configurations separate from others. I have these load in various ways (desktop icons, etc...).

With this new feature it will be possible to have the user access these from one interface.

The problem with what has been created here, is that this is controlled from the user and not management.