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.

Currently 15 out of our 18 Microstation users work out of office so this approach doesn't sound practical. Could you kindly make <IsEditable>true</IsEditable> as a default setting in the future relases so that we can hide the example configurations from GUI without tweaking XML-files in every single user folder.

MS CE UD 17 is ignoring "MS_CONFIGURATIONOPTS" variable I have set at the Organization level

I was checking to see if this variable changed in UD 17 - as this new interface allows users to create workspaces/workset
Was also checking here to see if this could control (or ignore) the new UD 17 interface being discussed here

Our workspaces/worksets are "Read Only" on a server

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.

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.