In some situations it is necessary to limit the numbers of Users connecting to a Vault Server.
This can be achieved in a number of ways, such as using different licence servers for each Vault Server. In this blog article, I am discussing Limiting Web Site Usage by throttling the number of Concurrent Connections.
In Internet Information Services (IIS) Manager, on the Default Web Site, in the Advanced Settings, is an expandable node called "Connection Limits". there is a setting "Maximum Concurrent Connections", which in IIS 7.0, has a default setting of "4294967295". Enforcing a non-default setting requires an IISRESET.
Changing this value will limit the number of connections at anyone time to the Vault Server. When the limit is reached, a user will receive a message like this.
Each Vault Client application will consume 1 connection. (Example 1 machine with 1x Vault Thick Client and 1x Inventor, runing and logged into Vault, will consume 2 connections)
Logged in but inactive clients release connections, which is then re-acquired following any client-server communication, such as browsing.
When mulitple users are connected to a Vault, the above error message will persist until the total number of connections to the Vault server drops below the defined limit, or the user logs into another Vault Server.
Vault Professional will poll the Vault Server every 5 minutes, see "Vault Licence Release Behaviour"
Monitoring Current Connections.
You can use the Windows Performanc Monitor to see the number of users who are connected to the Vault Server using the Web Service\ Current Connections Counter.
The instance selection will depend on if there are other websites running on the same server. For default Vault Server installations, selecting either the "_Total" or "Default Web Site" should be sufficient.