This support solution explains how to configure SELECTserver to prevent activation of a product unless a license is checked out using the Product Activation Wizard or License Management Tool. This article does not explain how to restrict your usage to avoid Quarterly Term Licenses. For more information regarding avoiding Quarterly Term Licensing this article.
By default SELECTserver is configured to accept usage collected and transmitted by client workstations. Workstations typically transmit usage once a day if communication is possible. This system provides access without checking for license availability since real-time communication with SELECTserver is not a requirement. Consequently, license overuse can become a concern. To help limit license overuse, SELECTserver can be configured to require the "checkout" or assignment of a product license to a client workstation for a specified period of time.
Important: For users of SELECTserver OnLine, Bentley's licensing solution over the Internet, a Bentley login with the Site Administrator role is required to complete the steps below.
When usage is restricted to checked out licenses only, products will not activate unless a license is checked out first. However, most Bentley products will still function in disconnected mode for up to 30 days without a license. Consequently, this setting alone is not sufficient for limiting usage. A change in workflow is needed to address this. What the setting does address is the simultaneous usage of licenses in excess of those owned if the following suggested workflow is used.
As mentioned above, simultaneous (i.e. concurrent) usage of licenses in excess of those owned is prevented if engineers use the suggested workflow.
For users of Bentley's hosted SELECTserver, selectserver.bentley.com, a round-up rule introduced in Q2 2016 eliminates usage overlaps that could occur when checking in a license from one machine and immediately checking it out on a different machine. The "How is usage calculated" section in the following FAQ provides further details. Users of a deployed SELECTserver should still exercise extreme caution since usage is calculated by the number of machines that used a license in a calendar hour, for example 11:00 - 11:59. When in doubt, wait until the next hour or migrate to Bentley's hosted SELECTserver.
Bentley's SELECT Open Access program provides unlimited access to the majority of Bentley's portfolio, much like the Enterprise License Subscription often used by large organizations. Because license access is unlimited, however, all products show with a quantity of 500, breaking step 2 in the suggested workflow above. To compensate, SELECTserver's Checkout Restrictions feature can be used to specify license quantities available for checkout. Please perform the following steps:
Once the license quantities have been adjusted to owned quantities using the steps above, the suggested workflow above will work as expected.
Even easier approach would be to use licensecmd tool and create shortcuts for each product(by productid) which check-outs license for whole day. This prevents overusage at all as no excess licenses could be borrowed. If user doesn't checkout it next day then it will be free automatically.
licensetoolcmd.exe checkout -productid:1000 -productversion:08.11.09.459 -checkoutperiod:0
licensetoolcmd.cmd checkout -productid:1038 -productversion:08.11.09.459 -checkoutperiod:0
For SELECT Open Access users, Checkout Restrictions can be used to limit checkouts to the quantity of licenses owned. The support solution has been updated with these configuration steps.
This workflow no more works for OPENACCESS sites. Now the license count for OpenAccess is Unlimited so there is no way to tell how many licenses are free to use. Also reports do not show license count. Is it a bug or WAD?
We also want a mechanism to restrict use to the number of licenses we have licensed - not have to implement a "workflow" in an attempt to mitigate over use! Are we expected to pay the over use QTL's while we implement this "workflow"?! And who pays for the time spent training, policing and managing this "workflow"!
Why is it so hard to provide the restriction option for those organisations that want it! Technically, it cannot be very difficult. It was there before someone took it away!
If we do implement this "workflow", will Bentley waive the QTL invoice caused by someone in our organisation not following the "workflow"? And how do we tell who was responsible for not following the "workflow".
I am having this conversation now and have had this conversation virtually every year with Bentley when the Select renewal comes due! We have to keep our license count higher than we need to simply because the potential QTL costs work out so much more than the Annual costs. It is so frustrating! And is one reason that we are actively transitioning to other products.
If I was a conspiracy theorist, I would suggest this "flexible" licensing was a scheme dreamed up by a smart accountant as a means to increase revenue. However, I'm not and will give Bentley the benefit of the doubt when they say that a majority of their customers requested this type of licensing. We were not and remain not. I also remember that when it was introduced there were a significant number that did not want it. It would appear that there are quite a few that still don't want it.
I had to vent! Sorry everyone.
Sae_Vander, SELECTserver has been intentionally designed to stress fault-tolerance and access to products in response to years of feedback from frustrated users who could not license their products for various technical reasons ranging from Internet connectivity issues to checked out licenses that failed to return. Consequently, over the last few years, SELECTserver has become a tool for reporting usage and is not intended to be an enforcement mechanism for the reasons just described. Adjustments in workflow such as the one provided in this support solution can help, but ultimately, scheduling of program use must be incorporated to address overuse. Solutions ranging from an online calendar to sophisticated third-party reporting tools can help with this. I would encourage you to browse and participate in the various discussions on this topic in our SELECTserver and Product Activation forums at:
Note We use a Deployed Server
There is a defect number 115238 that this option ""Restrict Usage to only checked out licenses" in Hosted SELECTServer doesn't work. Until this is fixed this setting doesn't limit anything.
According to the comments, although we activate the "Restrict usage to only chequed out licenses" option, we will continue to receive notices of overusage for those computers that might not check out licenses and entered into demo mode 30 days and then were able to connect the server to report its use?
If so this makes no sense.
No access means no access. We want to have settings on a select server to avoid overuse definitely for each application.
If a user opens an application, which in turn connects to a license server that has no licenses available for this application, and the license server only allows checkuout license, then the application should display a message "no license available "and should not be allowed to enter demo mode for 30 days.
We want a more transparent solution for everyone.
I would appreciate any information that allows us to Administrators and Managers "MANAGE, CONTROL, PLAN" overuse.
One more question from users. Can you confirm that usage logs use always local time and not server time? Also what happens if doing check-in before checkout expiration, does it uses server time or local time? This is important in case computer clocks are not synchronized.
For example if real time is 12:01 but for one of computers local time is 11:55 and on other computer 12:05. If one of computer checks in at 11:55 and other checks-out license at 12:05 (simultaneously from server side) does it count as 2 usages from 12:00-13:00 or as 1 usage in 11:00 and other in 12:00?
Yes, Oto, any machine that is unable to check out a license will be thrown into the 30 day disconnected mode which will still log and record usage. As long as the machine is able to connect to the server, it will still post this "disconnected" usage to the server.
SELECTSERVER 9 help says this:
"Restrict Usage to only checked out licenses. - All users will need to checkout a license for every application they wish to use." box will force a checkout license for every use, thereby allowing SELECTserver to know instantaneously if usage is occurring. Accordingly, if a new usage request represents an overage, the user will not be able to checkout a license, thus mitigating overuse. While this method will prevent most overuse, usage is calculated by calendar hour, thus a license that is checked out and in within the same hour may be used by another user later in the hour which may cause an overage.
So will the disconnected mode report as overusage or not?