Hi @abhayparashar ! For a "dead" system, the License Server can be Returned (if enabled - configuration option)  by the admin in the Customer Portal.  This will return all licenses mapped to the server back to the entitlement and take the existing License Server HostID out of commission permanently (it will no longer be able to activate with FNO in the future).  The admin can then Activate a new License Server using the same online/offline method used to Activate the original license server. Thanks, Jim ... View more

Hi @Ravikiran , To answer your first question secure anchoring is not enabled by default.  You need to run a utilility (secureprofileutil) on your client identity in order to create a new client identity with secure anchoring enabled.   Thanks, Jim ... View more

Hi @MicheleF , No, there are no restrictions on file types.  They can be executables, iso/zip files, videos, documentation, data files, etc. Thx, Jim ... View more

Hi @paltvi , The renew interval provides the recommended time the client should wait between license renewal attempts with the server.  It is specified as a percentage of the borrow interval.  For example, the default borrow interval is 1 week and the default renew interval is 15 .  This results in a renewal of 15% of 1 week, or ~1 day.  This renewal interval is calculated and returned to the client in the capability response from the server.  Note it us up to you to read this value and renew the licenses with the server, it does not happen automatically.   Borrow/Renew intervals specified in the license model take precedence.   If set to "Not Used", FNO default values set in System/Configure/Embedded Devices/License Generation will be used. Thx, Jim   ... View more

Hi  @paltvi  Yes after requesting the change, the expiration date of features returned by the CLS will be equal to the expiration date on the entitlement when the Maximum Borrow Interval is set to "0" in the license model. If you release a license back to trusted storage, it is then available locally for acquisition granted the license has not expired.  When the license expires it will be reclaimed by the server. Returning a license back to server is a valid option.  This removes the license from trusted storage on the client and makes it immediately available for other clients.  Note that the purpose of the borrow interval is to make floating licensing tolerant.  Let's say a client checks out a license and then the application crashes, or the system has a hardware failure, or it goes offline for an extended period of time?  In these cases the system cannot return the license back to the server and you have to take other actions.  With a reasonable borrow interval you only need to wait a period of time and the server will automatically get the licenses back. Thanks, Jim         ... View more

Hi @paltvi , If you specify a maximum borrow interval in the license model, that value will be used by the server when providing licenses to served clients.   If you do not specify a value in the license model, the default FNO value will be used.  This is configurable and is set via System/Configure/Embedded Devices/License Generation.  In the example below the default borrow interval is 604800 seconds or 7 days. Served clients check out licenses from a license server.  These licenses are stored locally on the clients and will expire at the end of the borrow interval if they are not refreshed (re-requested from the server) periodically.    In your application it is best practice to periodically re-acquire the licenses locally from trusted storage to make sure that they have not expired.  If the licenses expire locally on the clients they will be automatically reclaimed by the server for use by other clients. Thanks, Jim   ... View more

Hi @paltvi , There is a known issue where Revenera will need to globally set the CLS licensing.borrowInterval to 0 in your instance if you want a borrow interval = entitlement expiration when setting the Maximum Borrow Interval to 0 in the license model.   Please submit a support ticket to have this configured. Thanks, Jim ... View more

Hi @paltvi , Please refer to the /features endpoint which is documented in the FlexNet Embedded License Server Producer Guide   Thanks, Jim ... View more

Hi @paltvi , You could obtain the desired information using the license server REST API /features endpoint. Thanks, Jim ... View more

Hi @Ravikiran , You referenced a custom (non-Revenera provided) license server.  Revenera does not provide APIs for creating your own license server.  The recommendation for implementing a floating license model would be to use either Revenera Cloud or Local license servers. Thx, Jim      ... View more

Hi Ken, FlexNet Operations provides default Roles with each Role having a default set of associated permissions.    Based on the desired permissions your technicians would need to be assigned a System Administrator role in order to create entitlements, updates, products, etc.   You can add a new "Technician" Role and tailor the desired permissions for that Role so they do not have the full set of permissions assigned to a System Administrator.   Thanks, Jim   ... View more

Hello @beethika_pandey , It is possible that the license return policy has been exceeded.  Please submit a support ticket so someone can get access to your account & entitlements to verify.  Thanks, Jim ... View more

Hi @Ravikiran , Yes the C-SDK has all the necessary APIs to implement floating/concurrent licensing.  There are a few differences between licensing a client directly with FlexNet Operations vs using a License Server.   Direct activation with FlexNet Operations (FNO): - The capability request from the client to FNO contains an Activation ID and Quantity using FlxCapabilityRequestAddRightsId or FlxCapabilityRequestAddRightsIdWithSettings.   - FNO returns all of the features associated with entitled Product.  Features expire on the entitlement expiration date. License requests from a Server (Local Server or Cloud Server):  - The License Server is activated and contains a pool of license features.  -  Capability requests from the client to License Server contain the desire license features and quantities using FlxCapabilityRequestAddDesiredFeature. - Features are "borrowed" from the server for a designated borrow interval specified in the license model or default FNO settings (default is 1 week). - Features need to be re-requested (renewed) periodically to extend the expiration date. Thanks, Jim   ... View more