Configuring the SMART Client with config.json – SMART DPK Support

Authentication File

Some SMART Client deployments also use an authentication text file, such as auth.txt.

This file is used only for authentication. It contains the encrypted token the SMART Client uses to identify the correct company and facility when it starts.

auth.txt is not a product-key list. Do not add Windows product keys to a text file for SMART to inject. Windows licences are managed through the SMART Dashboard and injected by the SMART Client during the normal workflow.

The config.json file allows you to customise the behaviour of the SMART Client on a per-installation basis without changing the global Client Settings in the SMART Dashboard.

This is useful where different production lines, facilities, Wi-Fi networks or deployment environments need different SMART Client behaviour.

Important

The file must be named exactly config.json and must be placed in the same folder as SMART.exe.

If the filename is changed, or the file is placed somewhere else, SMART will ignore it and the settings will not be applied.

Basic config.json structure

A valid configuration file uses the following structure:

{
  "Client": {
    "AuthFileName": "auth.txt",
    "NetworkConfiguration": {
      "SSID": "",
      "PassPhrase": ""
    },
    "Overrides": []
  }
}

AuthFileName

"AuthFileName": "auth.txt"

This tells SMART which authentication file to load when starting.

The default value is auth.txt.

In most environments this should not be changed unless instructed by SMART Support.

NetworkConfiguration

The SMART Client can temporarily connect to a wireless network while it is running.

Example:

"NetworkConfiguration": {
  "SSID": "Warehouse WiFi",
  "PassPhrase": "password-here"
}

Property	Description
`SSID`	The wireless network name.
`PassPhrase`	The Wi-Fi password.

When SMART launches, it will:

Create a temporary wireless profile.
Connect to the specified network.
Complete any online operations.
Remove the wireless profile before the process finishes.

This helps ensure Wi-Fi credentials are not left behind on the customer’s device.

Overrides

Overrides allow you to force selected SMART Client settings locally using config.json.

Example:

"Overrides": [
  "DriverCheckEnabled",
  "AuditModeEnabled"
]

Each entry is the name of the setting you want to enable.

Dashboard setting to override mapping

SMART Dashboard setting	config.json override	Availability
Enable Driver Check	`DriverCheckEnabled`	All facilities
Enable Audit Mode	`AuditModeEnabled`	All facilities
Enable Reverse Lookup	`ReverseLookupEnabled`	All facilities
Close CMD Prompt	`CloseCmdAtStartup`	All facilities
Exit when Shipping to Customer	`ShipToCustomerExitsSmart`	All facilities
Force Citizen Key Injection	`ForceCitizenKeyInjection`	All facilities where Citizenship licences are available
Low Battery Check	`CheckBatteryStatus`	All facilities
Enable Automated Driver Install	`AutomatedDriverInstall`	Essentials/Pro only
Auto Inject Key At Launch	`AutoInjectOnLaunch`	Essentials/Pro only
Wait On Results Screen	`WaitOnResultsScreen`	Essentials/Pro only
Skip Driver Install	`SkipDriverInstall`	Essentials/Pro only

Available overrides

DriverCheckEnabled

Requires all required Windows drivers to be installed before SMART can continue to licence injection.

If this is not enabled, SMART still checks for missing drivers, but the technician may be allowed to continue depending on the facility settings.

AuditModeEnabled

Requires SMART to be run from Windows Audit Mode.

This is recommended for most deployment workflows.

ReverseLookupEnabled

Warns the technician if the detected Windows edition differs from a licence previously assigned to the device.

For example, if a device was previously licensed with Windows 11 Pro but has now been installed with Windows 11 Home, SMART will warn the technician before continuing.

CloseCmdAtStartup

Attempts to close Command Prompt and other open applications when SMART starts.

This helps prevent external applications interfering with the licensing process.

ShipToCustomerExitsSmart

Normally, SMART runs Sysprep after licensing to return Windows to OOBE.

When this override is enabled, SMART exits instead. This allows the technician to continue working before manually running Sysprep.

ForceCitizenKeyInjection

Forces SMART to inject Citizenship licences instead of standard Home or Pro licences.

Requirements:

Windows Pro must be installed.
Citizenship licences must be available.

CheckBatteryStatus

Warns the technician when a laptop battery is low before starting the licensing process.

This is recommended for portable devices.

Essentials/Pro only automation overrides

The following overrides are only available for Essentials and Pro facilities.

They are not available on Pay As You Go facilities. If these values are added to config.json for a Pay As You Go facility, the SMART Client will automatically disable or ignore them.

AutomatedDriverInstall

Automatically downloads and installs missing drivers before continuing.

This is intended for automated deployment environments using Essentials or Pro facilities.

AutoInjectOnLaunch

Automatically begins the licence injection process when SMART starts.

This is designed for highly automated production lines using Essentials or Pro facilities.

WaitOnResultsScreen

Keeps SMART open after processing has completed until the result is acknowledged by the technician.

This is useful where operators need to review the result before continuing.

SkipDriverInstall

Skips the automated driver installation stage.

This is useful where drivers are installed by another deployment solution.

Example config.json file

{
  "Client": {
    "AuthFileName": "auth.txt",
    "NetworkConfiguration": {
      "SSID": "Warehouse WiFi",
      "PassPhrase": "password-here"
    },
    "Overrides": [
      "ForceCitizenKeyInjection",
      "AutomatedDriverInstall",
      "AutoInjectOnLaunch"
    ]
  }
}

Notes

config.json must be in the same folder as SMART.exe.
The filename must be exactly config.json.
The SMART Dashboard currently generates a standard config.json automatically.
Additional override entries can be added manually if required.
Unknown or unsupported override names are ignored by the SMART Client.
Pay As You Go facilities cannot use the Essentials/Pro only automation overrides.