my question is as the subject described! Is it possible to lock one product to only be used by one connection user at the time.
we have for an example one licens of microstation but fibe users, is it possible to manage that the one microstation license is locked to the first user who activated the license an the rest of the user gets for example an message ”no license aviable” the license is used by user firstname.lastname@example.org
if it is possible how do I manage that setting?
Hi Tom,What product & version are you using? With the latest CE products, you can get a notification of "opening this may cause an overage", but I don't think there is a way of preventing someone from overriding the notification and causing an overage.
What version we are using:
The latest connect versions. but the handling of user license connections is also via the "new" connection client workflow, where every user connects to the Bentley site (license) with there own personal login "usernamne/password) so it is straight forward who logs in in person not as in old days when the computer was the "ID" from someone wanted an license.
So when we now are using this "personal" login procedure via connection client so in my mind there also be an possibility to get granted ok to to one license or not ( if the site license usage is limited to X sum users)
I can be totally wrong in my ideas but I Know that in old days before Connection Client this was not possible because you didn´t know who " person" requeried the license, all you sended was computer name "ID"
So now when you have to login via connection client to get the license the user who want´s is aviable an the computer wherefrom the user accesses license is not relevant anymore.
So I hope you understand my bad English and get an idea what I am after
So instead of node_lock options there would be an user ID Lock instead in connection versions, the only thing what I have found to manage what users can or not can do in settings is:
And this is not what my question is about.
And it would be great that somewhere there was an setting that could avoid running more that one Microstation at once, most relevant place would be on installed microstation computer in microstation settings/preferences.