We have produced a small licence activation bolt on for a our software, which allows the user to activate their copy of the software. After confirming activation with us it logs the activation date on the local machine. This is then used to calculate when the software should expire.
We will know when the time is up and our central system will reinvoice the client. However, we can't stop the client cancelling the subscription and adjusting the Windows time to keep the software running.
We have considered using the BIOS date rather than the Windows date, however we came accross problems coding this (nasty code), besides the BIOS time is not always correct!!
I have some ideas for how to at least detect if the client has changed the time, but wondered if there was an excepted solution to this problem. I can't find anything out there, and am sure that we are not the first people to want to do this!!
Any ideas would be gratefully received...
We will know when the time is up and our central system will reinvoice the client. However, we can't stop the client cancelling the subscription and adjusting the Windows time to keep the software running.
We have considered using the BIOS date rather than the Windows date, however we came accross problems coding this (nasty code), besides the BIOS time is not always correct!!
I have some ideas for how to at least detect if the client has changed the time, but wondered if there was an excepted solution to this problem. I can't find anything out there, and am sure that we are not the first people to want to do this!!
Any ideas would be gratefully received...