cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Clock-Windback detection with an FlexNet Embedded client

Clock-Windback detection with an FlexNet Embedded client

Summary

Do you need to separately resolve clock-windback once you've corrected a client system clock?

Question

If a client system activates a capability request and then realizes their system clock isn?t correct, after they fix the system clock, the clock-windback detection gives an error. The question is, do they need to reload the license from the server with the new client time settings to avoid this error? Or is windback detection evaluated each time a client attempts to acquire a license? And if the former (which I assume means there?s a flag or something set in the Anchor file?), what?s the process on FNE to fix a clock-windback flag? Or am I completely misunderstanding how this works?

Answer

If they set the clock back and then restore the correct time, then the wind back error should clear itself.

If they set the clock forward, performed licensing operation, and then restore the correct time, the error persists until the real time catches up with the time of the last licensing operation performed while the clock was wrong. The way to clear up this error is by applying a new capability response, which resets the clock wind-back anchor even if it is set in the future.

In general, we mostly worrying about moving clock backward to extend the expiration time. Setting clock forward might let someone to access the license before its start date, but does not extend the length of license availability.


Additional Information

Clock wind-back detection will be triggered if the system time appears to have been set to an earlier date than has been recorded by the licensing infrastructure (see our documentation). Setting the system time back to the correct time should allow the licensing system to continue functioning. Having set the time forward and used licensing such that it updates the wind-back time the predicament is that there is no easy way to reset the wind-back time to the present. To accomplish this, a new capability response should be created which when processed will reset the wind-back time to the time of the capability response.
Was this article helpful? Yes No
No ratings
Comments

"a new capability response should be created which when processed will reset the wind-back time to the time of the capability response" how do you do this in the code?

@xiaoming_tu  the capability response is typically generated by either FlexNet Operations or a License Server.

Version history
Last update:
‎Nov 12, 2018 07:51 PM
Updated by: