<%NOJS_WARNING%>

KISTERS Logo KISTERS logo

The VS License Manager's usage privileges can be configured by editing and saving the ServerConfig.json file. This includes allowing, denying, restricting, and reserving checkout and borrowing of features for specific users. Restart the VS License Manager for the changes to take effect.

When to use which privilege rule?

If you want most of your users to be able to use all features and only a few to be restricted, use Deny Rules.

If you want to allow a few privileged users to use certain features and restrict most of your users, use Allow Rules.

If you want to control the number of features available to different user groups, use Limit Rules and Reserve Rules.

How to specify users?

In each rule, users can be specified as usernames, host names, or IP addresses (IPv4 or IPv6, see setting IP_VERSION) and must be separated by a semicolon:

"USERS": "UserOne;UserTwo;UserThree;..."

If the list becomes large, or if the same list is used in multiple privilege rules, it is useful to define GROUPS at the end of the configuration file. The format for MEMBERS is the same as for USERS. Curly braces {...} define a group within the group list [...], separated by commas.

"GROUPS": [

   {

       "NAME": "Group 1",

       "MEMBERS": "UserOne;UserTwo;UserThree;...;UserN"

   },

   {

       "NAME": "Group 2",

       "MEMBERS": "Host01;Host02;Host03;...;HostX"

   }

]

You can now specify users as follows:

"USERS": "Group 1;Group 2"

Linking a group within a group is supported.

Note:

When restricting many host names or IP addresses, you can use wildcards like "4.3.2.*" or "PC*" or IP ranges such as "4.3.2.10-50". Usage examples can be found below.

On Windows, you can use your local groups. If you have a local group "My Users" that contains a list of domain users or a domain user group, you can use it like a user or group name in the configuration file by simply prefixing it with '&': "USERS" : "&My Users". Usage examples can be found below.

The default ServerConfig.json contains two empty presets per rule, which can be edited or removed and are ignored by the VS License Manager.

Important syntax rules:

The server configuration file uses standard JSON syntax.

Square brackets [...] define the list of privilege rules for a privilege setting, separated by commas.

Curly braces {...} define a single privilege rule, separated by commas.

Multiple key-value pairs within a privilege rule must also be separated by commas.

All users, features, and serial numbers must be separated by a semicolon.

You can use the following examples as templates.

hmtoggle_arrow0  Allow Rules

hmtoggle_arrow0  Deny Rules

hmtoggle_arrow0  Limit Rules

hmtoggle_arrow0  Reserve Rules

English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version German Version English Version Japanese Version Italian Version French Version Spanish Version Chinese Version German Version English Version Japanese Version Italian Version French Version Spanish Version Chinese Version German Version English Version Japanese Version Italian Version French Version Spanish Version Chinese Version Tutorial File Format list-PDF Admin-PDF Release Notes-PDF Sys requ-PDF Function list-PDF