Using the provided installer

1.Use the Policy Manager to prepare the policy file. Please see the instructions about using the Policy Manager.

2.Install the software using the provided installer.

3.Deploy the policy.ini and/or local.ini files. There are two ways to install the policy for the end user:

Local policy

- Install the policy.ini file to the main FastKeys folder on each user's computer. The advantage of a local policy that it is available also when user is not connected to the network.

Shared policy

- Install the policy.ini file on a network location accessible to all users. Install "local.ini" text file to each user's computer with the path to the policy file. For example, if your policy.ini file is located on a W:\Shared folder, the content of the local.ini file would be:


The advantage of the shared policy file is that the administrator can change any policy setting without a need to deploy the settings to users again. You can also use a /POLICYFILE command line parameter to deploy the policy.

Command line parameters

The following optional command line parameters can be used with the provided installer:

/SHAREDFILE=file path - Installs FastKeys with the link to the shared settings.

/POLICYFILE=file path - Installs FastKeys with the link to the policy file. Only available in the Enterprise Edition.

/SP - Disables the This will install... Do you wish to continue? prompt at the beginning of Setup.

/SILENT - Instructs Setup to be silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is.

/VERYSILENT - Instructs Setup to be very silent. When a setup is very silent the installation progress window is not displayed.

Using custom installer

Many companies prefer to use their own deployment tools and procedures to install software to the production environment and create their own installation packages. Installation is very simple and only requires to copy FastKeys files and folders to local users.

The following principles should be considered:

- Custom installer need to include all FastKeys folders and files,

- Policy.ini and/or local.ini files need to be located in the main FastKeys folder,

- Make sure you do NOT include Policy Manager to ensure users cannot change the settings.

- Ensure proper user access rights for the folders containing user data.

Please let us know if you need any additional support.