Examples: Lease Renewals and Entitlement Updates
The following examples illustrate how different settings affect lease renewal and entitlement update distribution. (Relevant for Sentinel RMS 10.1 and later.)
| Flexible License Model Settings | Administration Console Settings | ||||||
|---|---|---|---|---|---|---|---|
| Scenario | Lease Duration | Lease Renewal Frequency | Detect Entitlement Updates (Includes License Model Attributes) | Entitlement Update Detection Interval—Back End (mins) | Entitlement Update Detection Interval—Client (mins) | Outcome | Notes |
| 1 |
Default (Full license) |
Default (No lease renewals, only updates) |
Default On |
Default (1440 minutes, meaning 24 hours) |
Default (60 minutes) |
When license-related attributes are changed, entitlement updates are delivered in the next 1 hour (approximately). To immediately obtain updates, clients can sync manually. |
Recommended setting |
| 2 |
90 days |
24 hours |
Default On |
Default (1440 minutes, meaning 24 hours) |
Default (60 minutes) |
Lease is renewed on daily basis.
Entitlement updates are delivered as per the settings. |
Not recommended.
Such frequent lease renewal generates a very high volume of activation records. This can lead to degraded performance. |
| 3 |
90 days |
24 hours |
Off |
Not applicable |
Not applicable |
Lease is renewed on daily basis.
Entitlement updates are delivered along with the next lease renewal. |
Not recommended.
Such frequent lease renewal generates a very high volume of activation records. This can lead to degraded performance. |
| 4 |
Default (Full license) |
Default (No lease renewals, only updates) |
Default On |
1 minute |
10 minutes |
When license-related attributes are changed, entitlement updates are delivered in 10 minutes (approximately). | Useful when no manual synchronizations are possible and updates are to be received quickly and automatically. |