Sometimes it can be extremely useful to be able to automatically import an activation key into a CompleteFTP configuration file (config.db).
For example, this may be required in a failover scenario. If CompleteFTP is set up on a primary machine, and a secondary machine maintains a backup, administrators may choose to regularly copy config.db across to the failover machine.
However the primary machine's config.db file will contain the activation key for the primary machine. The activation key for the failover machine must be inserted in config.db for CompleteFTP to operate with this configuration file on the failover machine.
This is easily accomplised by entering the activation key via Enter Activation Key in the Licensing panel. However this is a manual process, and it may be desirable for the process to be automated.
Updating the activation key automatically can be accomplised with the license utility that can be found in the Server directory of the installation (typically C:\Program Files\Complete FTP\Server). This utility permits importing or exporting of the activation key to or from config.db:
license -c config.db [-i infile|-e outfile|-d] [-h] -c config.db : CompleteFTP configuration file -i infile : file to import activation key from -e outfile : file to dump activation key to -d : delete the activation key from the database -h : show this help
For example, to import an activation key saved in a text file:
license -c C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\config.db -i license.txt
Note that this tool will not work with CompleteFTP clustered servers (as replicating the configuration is the task of the cluster). Enterprise MFT is required for cluster support. You can contact us to upgrade to Enterprise MFT from the Standard or Professional Editions if you wish to access this functionality.