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.
It seems this configuration.xml is new to U17, and no mention in help that I can find. It would be greatly appreciated if there's a wiki/TN for its usage. The file doesn't seem to be optional. I tried to mess around with it and ended up with no workspace/workset visible.
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).
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.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
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.
Rod WingSenior Systems Analyst
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.