Skip to main content

Information on ShareScan Key Resets

What is a key reset?

A license key reset is when the license activation information on the Kofax activation server is cleared to allow the activation to occur on a new machine fingerprint.

When is a key reset required?

ShareScan 5.x and 6.x: A key reset is required when the Server hosting the SQL component of ShareScan is changing or the SQL instance is changing. This is irrespective of whether the solution is for Embedded Device types or ScanStation device types.

  • Common reasons for requiring a Key reset: SQL database is migrating to a new server, SQL server is configured to Failover to a new node that causes licensing errors in ShareScan, SQL instance is renamed or changed, Windows Operating System upgrades, Full reinstallations or migrations of the software where SQL database is reinstalled or migrated. In some cases, when upgrading the software to a newer version.

ShareScan 4.x and earlier: A key reset is required when the device where the ShareScan client is installed is changed.

  • For embedded solutions, the ShareScan client is installed on the MFP. Most embedded devices activate with the serial number of the MFP. Changes to the MFP such as a HDD replacement, typically do not require a key reset as the MFP serial number does not change.
  • For ScanStations, the client is installed on the ScanStation PC. Significant Hardware changes to ScanStation PCs such as replacing the NIC, HDD, or CPU, may require a key reset as the MAC address will change.

How to request a key reset:

  1. Ensure that the license key is registered to an End user account or Dealer sub-account.
  2. Open a support ticket requesting a key reset on
  3. Provide the following information:
    1. The license key(s) to be reset. This may be provided as a license report. (See How to create a license report for  or )
    2. If a reseller is submitting on behalf of a customer, the Customer Company information must be provided
    3. The status of production on the server.
    4. Provide error messages received if applicable.
    5. If submitting a request in advance of a major change such as a migration or reinstallation, provide the approximate date and time when this is occurring.
    6. Provide details regarding recent or upcoming changes to the implementation indicating why a key reset is required.