2
I developed a commercial software, with system to system licensing. For licensing purpose, I'm using various parameters like CPU info, hard disk info, BIOS, and other stuff.
The problem is the license keeps expiring due to change in these properties. Clients keep calling me saying their license isn't working.
I've changed the licensing to use just:
- Processor ID
- CPU Name
- CPU NumberOfCores
- CPU NumberOfLogicalProcessors
- Architecture
Do any of these properties change after a fresh windows install?
I don't want a server side serial key validation since most of these systems don't have internet connection
not sure, but the defintely do when your computer breaks and you upgrade – None – 2019-04-03T14:04:27.517
Why is this important? Most users don't reinstall their OS on the same machine repeatedly. Most Windows users don't even install their OS by themselves, today they usually buy a machine with the OS preinstalled. When one of the above parameters has changed, it is likely the hardware was changed. If you want to stop users from calling you because they changed their machine, you need to provide a hardware license key for them they can plug into their USB port. – Doc Brown – 2019-04-03T17:47:07.123
Hi doc, basically the software is installed in factories. Their systems keep crashing frequently due to power shortages, some application malfunction, etc, and the os gets corrupted. They have proper IT teams to rectify the system, install all the softwares. The hardware dongle would work, but it would not be feasible to always send it to clients who are living abroad – mrid – 2019-04-03T18:33:06.417
1Why don't you put the above parameters (and maybe others) into a log file in case of a failed license identification? So when a client asks you about the malfunction, you ask them to send you the log first by mail? Then you can actually see what's happening there. – Doc Brown – 2019-04-03T19:40:20.280