You can download the SMART Client files from the SMART App:
https://app.smartdpk.com/client
You must sign in before downloading the files.
Files You May See
-
SMART.exe— the SMART Client application that runs on the device you want to licence. -
auth.txt— the authentication file that tells SMART which company and facility to authenticate against. -
config.json— an optional configuration file used for custom settings, overrides, Wi-Fi profiles, or specific workflows such as Citizenship key injection.
Normal Licence Injection
For a normal first-time licence injection, you usually only need:
SMART.exeauth.txt
Put both files in the same folder, for example on a USB drive, then run SMART.exe on the device you want to licence.
When You Need config.json
config.json is only needed for advanced setups, when you want to change how the SMART Client behaves for that folder.
It can override global SMART Client settings for that specific folder, or help the device automatically connect to your Wi-Fi network when SMART launches.
Examples include:
- forcing Citizenship key injection using
ForceCitizenKeyInjection - adding Wi-Fi details for startup connection
- using client overrides for a specific production workflow
If you are not using a custom workflow, you do not normally need config.json.
Important
-
auth.txtis not a product-key list. -
config.jsonis not a product-key list. - Do not manually type or paste Windows product keys into either file.
- SMART injects licences from your available SMART licence inventory.
If You Cannot See the Files
- Make sure you are signed in to the correct SMART account.
- Make sure you are using the account/facility that owns or has access to the licences.
- If another user in your company purchased the licences, sign in with that user or ask your administrator to give your user access.