SMART shows “Invalid config.json” or “auth.txt not found” when running from a network share
SMART needs the executable, config.json, and auth.txt to be in the same folder and it must be launched from that folder.
If you run the EXE from a script without changing directory first, Windows keeps the working directory somewhere else (often C:\Windows\System32). SMART then can’t see the JSON or TXT files and shows an error.
Before launching SMART, set the working directory:
Batch
pushd z:\client smartclient.exe popd
PowerShell
Start-Process "z:\client\smartclient.exe" -WorkingDirectory "z:\client"