Identify the cause before changing the system

SmartScreen or self-signed warnings

1. Confirm the file came from the official Release.
2. Compare SHA-256 and run the package verifier.
3. Check Authenticode, signer, and timestamp.
4. If every check passes, a personal user may intentionally select More info → Run anyway.
5. On managed systems, contact IT when AppLocker/WDAC blocks execution.

The Agent has not submitted a report

1. Confirm the endpoint is awake and connected to the LAN.
2. Wait for boot/logon/resume triggers or the hourly schedule.
3. Check last-seen time and the latest error in the enterprise interface.
4. Confirm the server is listening on the configured IP/port and allowed by Firewall.
5. Pair again only when the stored configuration or key was removed or changed.

An already paired endpoint does not need a new code after reboot.

The LAN server did not start after reboot

1. Open Enterprise features and check server status.
2. Confirm the VietLicenSure Enterprise Server startup task still exists.
3. Recheck URL ACL, port, and Firewall through the application controls.
4. If you intentionally stopped the server or disabled LAN, the auto-start task is removed; configure/start it again.

The Central Dashboard returns 401 or the session expired

1. Open the Dashboard again from the application to obtain a fresh URL/session.
2. Do not edit the token, change the bound IP, or share the URL outside the authorized LAN scope.
3. Short-lived sessions expire and are revoked when the server stops or resets; this is expected security behavior.

The pairing code expired

The code is only for enrolling a new endpoint and has a limited lifetime. Generate a new code for an unregistered endpoint. Existing clients continue using their stored ClientId/secret and do not rotate the code after reboot.

Online, catalog, or version checks fail

1. VietLicenSure always starts Offline.
2. Enable Online only with explicit user intent.
3. The application downloads/validates the signed catalog first, then checks application-version availability; it never auto-downloads/installs a version or starts a scan, report, or privacy prompt.
4. A signer/hash/schema mismatch blocks the affected step fail-closed.

Online mode does not upload inventory or product keys; runtime telemetry is disabled.

“Licensed” appears but entitlement is unclear

Licensed/Activated is a technical state. Also verify invoices, agreements, accounts, or portals. MAK does not require a KMS host; an empty KMS value for MAK is not an error.

Still unresolved?

Export a redacted support bundle and include Build ID, reproduction steps, and screenshots. Do not share full keys, pairing secrets, or personal data.