Network Floating Options
Network Floating Options control the behavior of Cloud-Controlled Network Floating Licensing through the XmlNetworkFloatingService web service. If you are interested in implementing Cloud-Controlled Network Floating Licensing into your product, please contact us.
The fields on this page are as follows:
- Display Name
- Display name for the set of options.
- Poll Frequency
- The frequency the application will poll the server in seconds. Must be greater than 0.
- Poll Retry Frequency
- The frequency the application will retry polling the server if polling fails in seconds. Must be greater than 0.
- Poll Retry Count
- The number of times the application will retry polling the server if polling fails. Must be 0 or greater.
- Allow Temporary Overages
- If enabled, this will allow temporary overages to occur within the set maximum overage period. An example scenario of where this could be useful could include a user shutting the lid on a laptop before heading out to lunch, which causes the computer to suspend or hibernate. In this state, the computer is unable to perform any polls to keep the session active. When the user lifts the lid on the laptop and returns to its normal, running state, the session would no longer be active, and this could result in the user being locked out of the application if other users have since consumed all available seats. By allowing temporary overages, this will allow the user to resume a session which has since expired within the allowed overage period; however, this would result in the possibility of more seats being used than licensed temporarily. No new sessions may be open until enough active sessions have closed or expired to fall back under the seats allowed.
- Maximum Overage Period
- Please refer to the description of Allow Temporary Overages above. This is the time, in seconds, in which a session is allowed to be expired before polling again to resume its session, even if it means an overage will occur.
- Checkout Duration Minimum
- The minimum number of hours allowed when checking out a network seat.
- Checkout Duration Maximum
- The maximum number of hours allowed when checking out a network seat. Must be equal or greater than the Minimum Checkout Duration.
- Allow Checkout Extension
- Whether to allow extending the checkout period for a checked out session. Important: Enabling this feature means multiple checkout requests may be used to extend a checkout period. Checked-out sessions cannot be manually closed from within SOLO Server, so they may only be checked-in or closed from the application. If a computer should orphan/abandon a checked-out session, it's seat will not be recovered until that session’s check-out period is over. In other words, the ability to self-heal and recover orphaned seats is eliminated when using checkouts, and the risk of this being problematic is higher with “Allow Checkout Extension” enabled.
- Allow Expired Licenses
- Whether to allow expired licenses (with a Download Until in the past) to open sessions.