To activate or renew AppProfileSafe, place the License.json file and the public key (AppProfileSafe.pem) in the configured directories. The license is validated on the next application start — no restart of the operating system is required.

Installation Steps

1. Obtain License.json from your license administrator or the license portal.
2. Copy License.json to the license folder. Default: %ProgramData%\IT-Consulting Kinner\AppProfileSafe\License\
3. Ensure the public key file AppProfileSafe.pem is present in the key folder. Default: %ProgramData%\IT-Consulting Kinner\AppProfileSafe\Key\. This file is typically included in the installation package and does not change between license renewals.
4. Start (or restart) AppProfileSafe. The license is validated automatically on startup.
5. Verify the license status on the Dashboard — the License tile should show the customer name with a green indicator.

Custom Paths

If the default locations are not suitable for your environment, both paths can be changed in settings.xml:

<Paths>
  <LicenseFilePath>D:\Config\APS\License.json</LicenseFilePath>
  <PublicKeyPemPath>D:\Config\APS\AppProfileSafe.pem</PublicKeyPemPath>
</Paths>

Both absolute and relative paths are supported. Environment variables (e.g. %ProgramData%) are expanded at runtime. The directories are created automatically if they do not exist.

Renewing a License

To renew an existing license, simply replace the License.json file with the new version and restart the application. The public key file does not change — it only needs to be deployed once. If the license was in the grace period or had expired, the new license takes effect immediately on the next start.

The License tile on the Dashboard and the "License Info" window (accessible via the tile's Details link) both display the current subscription end date. When the license is expiring within 30 days, a renewal link is shown in the warning dialog.

Verifying the Installation

After deploying the license, confirm it is working correctly:

• GUI: The Dashboard's License tile shows the customer name, "Valid until" date, and a green status indicator. Click Details to see all license fields.
• CLI: Any CLI operation (export, import) starts successfully without exit code 3. License information is written to the application log.

If the license is rejected, see License Troubleshooting for common causes and solutions.

Enterprise Deployment

For automated rollouts, the license file and public key can be deployed via Group Policy, SCCM, Intune, or any software distribution tool. Copy both files to the target paths before or during installation. The Enterprise Deployment section covers deployment strategies in detail.