Problem

How to migrate transfer sites configuration between SecureClient running 6.1 or 6.3 on Windows OS to an instance running SecureClient 6.4 SP2 (or later) on Windows OS?

Resolution

IMPORTANT NOTE: When migrating transfer sites configuration between SecureClient version 6.3 onto SecureClient 6.4, transfer sites' passwords are NOT preserved. You will be prompted to enter transfer site's password on initial run. When migrating from SecureClient version 6.1 to version 6.4, passwords for the transfer sites are successfully transferred to the new SecureClient instance.

IMPORTANT NOTE: When migrating transfer sites configuration between SecureClient version 6.1 onto version 6.4, transfer sites' passwords are successfully transferred to the new SecureClient instance.

In order to sucessfully migrate transfer sites configuration between SecureClient running 6.1 or 6.3 on Windows OS to an instance running SecureClient 6.4 SP2 (or later) on Windows OS, you must execute the following steps in the exact order as they are listed:

Login into the Windows console of the source computer/server which SecureClient configuration will be migrated from. Make sure to login as user with administrative permissions.

As you are logged in, turn off SecureClient and the SecureClient Scheduler while you are still logged in. Make sure no SecureClient processes are running.

Navigate to SecureClient installation subfolder. It should look like: C:\Users\<username_folder>\AppData\Roaming\axway\SecureClient\data\site. For example: if SecureClient was installed by the "Administrator" user, the path would look like C:\Users\Administrator\AppData\Roaming\axway\SecureClient\data\site. If the installation was performed by a different user, replace <username_folder> in the path with the name of the said user.

Example: C:\Users\User1\AppData\Roaming\axway\SecureClient\data\site ("User1" would be the user that installed the SecureClient)

All files in this folder correspond to the specific transfer sites settings used in SecureClient. Select the files (as seen on the screenshot above) that you want to migrate. Select all files if your goal is to migrate them all.

Use whatever method you prefer to copy the selected files (transfer sites configuration files) from the source computer (the one you are logged into) to the destination computer (the one you are migrating to).

Login into the Windows console of the destination computer/server which SecureClient configuration will be migrated to. Make sure to login as user with administrative permissions.

As you are logged in, turn off SecureClient and the SecureClient Scheduler. Make sure no SecureClient processes are running.

(While still logged in the destination computer) Navigate to the installation subfolder of the SecureClient: C:\Users\<username_folder>\AppData\Roaming\axway\SecureClient\data\site

The files (transfer sites' configuration) from the source computer must be copied into this folder, overwritting any existing files should there are any. For example: if SecureClient was installed by the "Administrator" user, the path would look like C:\Users\Administrator\AppData\Roaming\axway\SecureClient\data\site. If the installation was performed by a different user, replace <username_folder> in the path with the name of the said user.

While still logged in the destination computer, navigate to the C:\Users\<username_folder>\AppData\Roaming\axway\SecureClient\data folder.

Open the site.db with a Notepad (or other prefered text editor) in order to edit the file. In order to do so:
Right-clilck on the site.db file; select the option Open with and choose "Notepad" from the appearing list of programs.

Once you opened site.db file in Notepad, add the names of the migrated transfer sites (the files migrated with the previous steps), each of the names on its own line.

Save the site.db file with the newly added transfer sites.

While still logged in the destination computer, start the SecureClient and the SecureClient Scheduler. The transfer sites' configuration that was just migrated will now appear.