How do I deploy license keys to the Windows clients automatically (/KEY parameter, registry, terminal server/Citrix)?

When rolling out software across an organization, the Password Depot Windows client is supposed to be unlocked without user interaction – only the Windows client requires a license key; the macOS, Linux, and mobile clients are free of charge. Three methods are available; they work with both the Standard and the Corporate Edition setup (pdepot19.exe or pdepot19CE.exe). The paths given apply to version 19.

1. Setup parameter /KEY= (as of version 16)
   Pass the license key directly during the – usually silent – setup:
   pdepot19.exe /VERYSILENT /KEY=<license key>
   The setup writes the key machine-wide to the registry (HKEY_LOCAL_MACHINE\Software\AceBIT\Password Depot 19, string value Key). It therefore applies to all users of the computer.

2. Deploying the registry value (without reinstalling)
   At startup, the client searches for the key in this order: first under HKEY_CURRENT_USER, then under HKEY_LOCAL_MACHINE (key Software\AceBIT\Password Depot 19, string value key in each case), and finally in a license file (see 3.). The license delivery for business customers contains the key as a license file (PasswordDepot.lic) and as a ready-made registry file (PasswordDepot_19.reg) for the HKCU branch – deployable e.g. via logon script or Group Policy. For machine-wide activation, create the same value under HKEY_LOCAL_MACHINE instead.

3. License file in the program directory
   Place the license file as PasswordDepot.lic next to PasswordDepot.exe (default: C:\Program Files\AceBIT\Password Depot 19\). The client reads the key from there if no valid registry value is present. Make sure not to change the name of the license file.

Terminal servers and Citrix

• Prefer machine-wide activation here (/KEY= during setup or an HKLM value): one entry applies to all sessions and is independent of user profiles.

• If you deploy per user (HKCU) instead, then with non-persistent profiles (e.g. Citrix profile management) the registry branch HKCU\Software\AceBIT\Password Depot 19 and the folder %AppData%\AceBIT\Password Depot 19 (program configuration pwdepot.cfg, and for the Corporate Edition also the policy file) must be preserved in the profile – otherwise users are prompted for the license key again after every new logon.

• Note the search order: a key under HKCU (e.g. an outdated one) takes precedence over the machine-wide HKLM key.

Note (older versions): Up to version 17.2.4, a separate WebSocket port had to be assigned per user for the browser add-on on terminal servers. Since version 17.2.5, the add-on communicates via Native Messaging; the WebSocket port settings were removed from the client (as of 17.2.5) and from the Server Manager (as of 18.0.0). Maintaining ports per user is therefore no longer necessary at all.

Note: License keys are issued per main version – for version 19 you need a v19 key (new delivery as part of software maintenance). A key reported as "invalid" frequently does not match the installed main version.

Related topics:

• What are the installer's Command Line Parameters for client's silent installation?

• How can I create the DefSettings.ini configuration file?

• How can I set pre-defined default values for the client's program options?

• Is there an msi file of the Password Depot installation program? / How can I create the Password Depot MSI Installer myself?

• Can I use Password Depot on a terminal server and if so, is there anything to take into consideration?