Create fingerprint

To use acron with license file key (FLK) you have  two options to create the necessary fingerprint for your acron license.

Option 1 with the acron Admin:
Install acron (using the supplied DVD) to a new directory. Then in acron Admin open  the 'Local license' area in the acron Explorer'. Click"Fingerprint..."to create a one-off file and send it to lizenz[at],quoting the purchase order number and where appropriate the license  number. The manufacturer requires the information from this file to create a custom license file, which will be promptly mailed to you with further instructions.

Option 2 with the "RUS_DaFo" program:
Install the hardlock driver (acron DVD\ Hardlock\ HASPUserSetup.exe). Then  run the  program  (acron DVD\ Hardlock\ RUS_DaFo…exe) and  follow its instructions. Please create a fingerprint and e-mail it to lizenz[at]

When  you submit the fingerprint by e-mail, if received Monday through  Friday by 2 p.m. we will return the file license key to the sender the same day. If e-mails are received after 2 p.m., we will return the file license key the next working day (again only Monday through Friday).

When using a file license key (FLK), the following points must be observed depending on whether acron is used on a virtual machine (VM) or a physical machine.

Virtual Machine (VM)
The FLK is bound to the fully qualified domain name (FQDN) of the VM. The  FQDN is composed of machine name and domain suffix, which means changes to the VM's machine name and domain affilia- tion are not allowed after the fingerprint is created. Subsequent modification of the above parameters will result in FLK inactivation.

Physical machine
The FLK is bound to hardware features of the computer. Extensive hardware changes (e.g. processor, mainboard,  hard  disk) are no longer permitted after the  fingerprint has been created. If hardware or software changes before license activation or if the fingerprint was created for the wrong computer, a new fingerprint must be created for a fee. Therefore, we recommend to use a hardlock or promo license for configurations that do not take place on the customer's 'end device'.