Copying a Server Configuration to Another Computer

There are many reasons for copying or migrating server configuration, such as:

Moving a Proof of Concept (PoC) in your staging environment without wanting to re-create all the settings, and configuration data.
Creating a standard configuration for installation on multiple computers.
Updating server software with a fresh install rather than patching.

Check the following before moving a configuration from the source to the target system:

Set the prototype site Administrator Home IP to All Incoming. It must not be bound to a specific IP address unless the system you are deploying to is bound to the same IP.
Verify the target system’s installation paths are the same as the installation path on the source computer. For example, if you installed the server on drive C:, then install on drive C: on the target, too. If the drive letters are different, change the drive letter on the target before installing the software.
Verify the Server root and location of the .aud file (if you are using GlobalSCAPE’s authentication manager). The drive letters on the target system must match those on the target in order for the Virtual File System (VFS) to find the Server root. (Otherwise, all permissions and groups will be lost.)
Use the same administrator username and password when installing on the source and target systems.

To set up the deployment configuration

Install and activate the product on the source system.
Configure as desired. This includes sites, users, groups, file and folder permissions, event rules, user settings, etc.
Exit the Administrator and stop the Server service in the Services dialog box (in the Windows Control Panel).
Copy the following files from the server installation directory over to the target machine:

Create the same physical folder structure on the target system as the folder structure created by the configuration of the source machine. (Simply copy the FTP folder structure from the source to the target.)

Install and activate the product on the target system.
Cancel the automatic site setup wizard that appears the first time you run the Administrator.
Exit the Administrator Interface and stop the Server service in the services dialog box.
Paste the files gathered from the source system into the server installation folder on the target system, overwriting existing files as necessary (which should only be the FTP.cfg file at this point).
Restart the server service and log in using the Administrator.
Double-check server and site configuration. The target system is now configured.