The supported methods to bulk configure product activation is either utilize Microsoft’s Group Policy, GPO or the utility, Licensetoolcmd.exe. Sometimes it is tempting to configure systems with a scrip or to push a registry settings to a accomplish this. Do to the complexity of the registry, and where we store settings based on the users rights (admin or not) and the user access control level, UAC and what operating system your running on and whether or not that OS is 32 bit or 64 bit makes this impractical to support. Group policies are the industry standard for this type of thing, mass deployments is the reason why Microsoft created them and is why we chose to implement support for them. Delivered with SELECTServer is a Group Policy template ADM called BentleyLicensing.adm. This will give administrators the ability to apply the SELECTServer settings to the desired objects. Attached to this article are the BentleyLicensing.adm and BentleyLicensing.admx GPO templates.
The following is a video on how to use GPO to configure your applications for Activation against a SELECTserver.
Using Active Directory GPO To Configure Licensing For Users Centrally
For those that can take advantage of Microsoft’s group policies, we developed the LicenseToolCmd.exe which is a command line executable that allows for the scripting of the SELECTserver settings. The script can either be a part of the user’s login script that is executed every time they login or run once when the machine is configured.
To populate the server name and activation key for the SELECTserver license, you can run a script to set this. After the installation, there will be a file called Licensetoolcmd.exe in the program's installation folder. Your script should use the following syntax:
...\Licensetoolcmd.exe configure /setting:selectserver /value:selectserver.bentley.com
…\Licensetoolcmd.exe configure /setting:activationkey /value:ABCDEFGHIJKL1234567890
For those using LicenseToolCmd, the following example batch file provides a good starting point:
Just to verify, LicenseToolCmd was developed for those who CANNOT take advantage of Microsoft's group policies, correct?
Very useful information!