RdpGuard Silent Installation and Deployment

Add the appropriate argument to your installation command:

• Custom installation directory: use /DIR="C:\Apps\RdpGuard" for EXE, or TARGETDIR="C:\Apps\RdpGuard" for MSI.
• EXE installer language: use /LANG=en, /LANG=de, /LANG=es, /LANG=fr, or /LANG=ru. The MSI wizard is in English.
• No desktop shortcut from EXE: use /TASKS="" to deselect optional tasks. Start Menu shortcuts are separate from these tasks.

EXE switches start with /. MSI properties such as TARGETDIR are uppercase NAME=value arguments without a slash.

Activate during deployment: supply a protected text file containing your license key. Add the matching argument to the EXE or MSI installation command above:

EXE:

/RDPGUARD_LICENSE_KEY_FILE="C:\Deploy\RdpGuard\license-key.txt"

MSI:

RDPGUARD_LICENSE_KEY_FILE="C:\Deploy\RdpGuard\license-key.txt"

Pass the file path, not the key itself. Activation requires access to the RdpGuard licensing service. Prepare the file using your deployment system's secure secret-file mechanism and meet these requirements:

• Use an absolute path on a local fixed drive. Network paths, mapped network drives, symbolic links, junctions in the path, and alternate data streams are not accepted.
• Use a UTF-8 text file containing one key. The file must be no larger than 4,096 bytes; the trimmed key must be no longer than 1,024 characters.
• The file owner must be SYSTEM or the built-in Administrators group. Its permission entries must grant access only to those identities, including inherited permissions. Ensure the installer can read it; for MSI, the activation action runs as SYSTEM. A file in an ordinary user profile may fail these checks even when setup is elevated.
• Remove the key file after the installer has finished, including after a failure. The installer does not delete a caller-supplied key file.

Activate later: use /DEFERACTIVATION=1 for EXE or DEFERACTIVATION=1 for MSI. Do not combine this with a license-key file. This skips the installer's online activation check; it does not activate a license, start a new trial, or extend maintenance. An existing local paid-license certificate is retained, but it must still be valid for the installed build.

A fresh installation without a key file also leaves activation to the installed product. Installation success alone does not mean protection is active. Confirm the license or trial and protection status before treating deployment as complete. During an update, a failed activation check stops silent setup instead of asking for a key.

EXE installation: run the uninstaller from the actual installation directory. This example uses the default path; use the registered uninstall path if it differs.

start /wait "" "C:\Program Files\RdpGuard\unins000.exe" ^
  /VERYSILENT /SUPPRESSMSGBOXES /NORESTART ^
  /LOG="%TEMP%\rdpguard-uninstall.log"
echo Exit code: %ERRORLEVEL%

MSI installation: use the original MSI for the installed version, or its registered ProductCode. Do not substitute the MSI for a different release.

start /wait "" msiexec.exe ^
  /x "rdpguard-setup.msi" /qn /norestart ^
  /L*v "%TEMP%\rdpguard-uninstall.log"
echo Exit code: %ERRORLEVEL%

Both formats keep settings, data, and logs by default. To explicitly remove them, add /REMOVEDATA=1 for EXE or REMOVEDATA=1 for MSI. Back up anything you need before using this option.

Cleanup targets %ProgramData%\RdpGuard but preserves its Licensing subdirectory. It does not reset a trial or bypass normal license deactivation. Linked directories are not followed, and locked or inaccessible files may remain. This is a cleanup option, not a guaranteed secure wipe.