In CE17 there seems to be another layer of messy configuration options bar in already confusing config jungle. How can I get rid of them? Our Microstaton users no need to access any example configs as we use our company workspace only. Therefore I would like to turn obsolete items off so that only our own config options would be visible. What's the point making the GUI more complicated? Who needs this?
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.
I managed to get rid of the example configurations by following your orders. This shoud definately be the default setting for the configuration selector bar! Now we need to do the same trick for another 18 workstations.....
so if you have 200 users, you will need to touch all their configuration.xml files and make this change ?
Don't you think their should be an easier way to control this from an admin perspective ?
CADD Manager | CADD Department
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
If the 200 users configurations are silimiar, just copy this configuration.xml to their prefs folder.
I get that and of course I can do this, but I will need to touch 200 users prefs folders (just seems very inefficient) .
It would be nice if it could be controlled by a configuration (IE: capability setting perhaps).
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/worksetWas 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