| Posted: 28-January-2009 at 10:09am
|
|
|
Question: How does the Riva "license pool" work?
License Model
Riva licensing is "mix and match". In the same company, you could have 100 licences of Managed Signatures, 150 licences of Managed Calendars and 250 licences of Reports. The recommended best practise to implement the "mix and match" licensing, is to use an eDirectory group or a Container that contains just those accounts that you want to license for each different module.
License Pool
The user counts per module are contained in the Riva license and the Riva manages it as a "license pool".
User Counting
Riva licensing works in a similar manner as DHCP. Riva licensing engine will consume a user count against an account listed in the source or destination list of a policy. Riva will hold that license count for that user for a period of 30 days of inactivity before releasing it back to the license pool of available licenses.
If you remove a user from the destination list of a policy, Riva will return the license count after a 30 day period, provided the user account is not included in a different policy of the same type.
For example, if you have three Riva Managed Calendar Policies and "Bob" is listed in two of the policies, Riva consumes one license count for Riva Managed Calendar Policies. If "Bob" is removed from both policies, Riva will return that license count back to the "license pool" after 30 days. If "Bob" is removed from one policy but is retained in the other policy, his license count is still being consumed by one of the Riva Managed Calendar policies and is not released back ti the "license pool".
Multiple Licence Files
Riva supports using multiple license files. In that instance, the license counts are cumulative (added together). One must be careful though to ensure that licenses with support expirary dates are removed, otherwise the "Check for Updates" feature may not work as expected.
|