PSIsafe Server Administrator Guide: Moving or Migrating a PSIsafe Server to another Machine

Related Links:

If you are not moving your PSIsafe Server installation from one machine to another, check out the following links:

PSIsafe Client: Cloud & On-Premise: Installation Guide

PSIsafe Server Administrator Guide: On-Premise: SQL Installation

PSIsafe Server Administrator Guide: Installation Prerequisites

PSIsafe Server Administrator Guide: On-Premise: New Installation

PSIsafe Server Administrator Guide: Registration


This article was created to help maintain your PSIsafe configuration across Servers. Normally these instructions are sent for those looking to update to a new Windows Server or leaving physical machines in favor of virtual environments. This article is not meant for PSIsafe Cloud users and is meant for system administrators of PSIsafe On Premise installations. 

Prepare New Server:

  1.  Ensure your Server meets the minimum requirements System Requirements

    1. Microsoft SQL Express 2017 (x86 or x64):

      1. There are different versions of SQL Server based on your business needs. SQL Server Express is free, but has limitations. We recommend that you only use SQL Server Express for an organization of 10 or less users.
    2. Microsoft SQL 2017 Management Studio Express 17.9:

    3. PSIsafe Server installer v11.1.0.4500 and beyond.

      1. Please email for current installers.
    4. PSIsafe Client installer v11.1.0.4500 and beyond.

      1. Please email for current installers.
  2. Unblock Installers and run as Administrator
    1. Ensure you unblock all installers downloaded by right clicking, selecting properties, and choosing the Unblock feature.
    2. When the above is complete right click the installer again and select Run as Administrator.
  3. Create Inbound and Outbound Port exceptions within Windows Defender Firewall with Advanced Security.
    1. TCP exceptions
      1. 8993-8994 (Service Ports)
      2. 11000 (.NET Remoting)
      3. 1433 (SQL Service)
    2. UDP exceptions
      1. 1434 (SQL Browser Service)


Backup and Restore Repositories and SQL Databases:

  1. Ensure that CNG-ServerService is stopped on both the original server and the new server locations.
    1. Locate service by opening Services.msc and selecting the CNG-ServerService.
      1. Right click on CNG-ServerService and select Stop.
      2. Right click on CNG-WorkflowService and select Stop.
      3. Right click on CNG-FullTextService and select Stop.
  2. Repositories
    1. Repositories are stored in the following location
      1. Open Management.
      2. Log in with a user that has PSIsafe Administrator credentials.
      3. Click on Filing Structure.
      4. Repositories.
        1. Here you will find the physical locations of your repositories.
    2. Transfer Methods:
      1. Standard file transfer of the entire directory to the new server.
        1. Copy and paste into new location
          1. You will need to ensure these are properly linked and a best practice would be to duplicate the exact file structure on the new server.
        2. Choose any method of transfer that best suits your organization.
    3. SQL Database Backup and Restore.
      1. Before beginning review Backup and Restore article.
        1. On the original Server open SQL Server Management Studio.
        2. Log in as SQL SA account or custom SQL admin account you have created.
        3. Backup your CNG_Main and CNG_Forms databases.
        4. Move The database backups to the new server location.


Condensed SQL Server Express 2017 Installation:

  1. Run the downloaded executable after being sure to unblock and “Run as Administrator”.
  2. Most of the default selections for the installation will be appropriate, allowing you to select “Next”,with the exception of the following screens:
  3. Check the box for “Use Microsoft Updates to check for updates (recommended)”.

  4. Name your SQL Server Instance to PSIsafe or similar on the “Instance Configuration” page.

  5. Set the SQL Server Browser to “Automatic” startup type on the “Server Configuration” page.

  6. Set the Authentication mode to “Mixed Mode (SQL Server authentication and Windows Authentication)”.

  7. Set the “sa” user password to “Admin-01” or something you will remember for later in the installation and registration process.

  8. Finish the installation process (may take sometime) until you arrive at the “Complete” screen.

  9. Ensure SQL Server Management Studio(SSMS) is installed in mixed mode authentication.
    1. We require this for all installs of PSIsafe.


Final Server Installation:

  1. SQL Restore Steps
    1. Open SSMS and login as the the sa SQL Administrator account, or custom SQL Admin account that you have created.
    2. Open the SQL Server Instance, Right-click on “Databases” and click “Restore Database”.
    3. Select the “Device” radio button and then browse to the location of the backup file with the “...” ellipses.
      1. Select “Verify Backup Media”.
      2. Once verification completes, hit “OK”
    4. This completes the SQL DB restoration process.
  2. Set TCP/IP to Enabled within SQL Server Configuration Manager.
    1. Open the SQL Server 2017 Configuration Manager.

    2. Select the Database we just created during the SQL Server Express installation process under “SQL Server Network Configuration”.

    3. Highlight “Protocols for [Instance Name]”.

    4. Right-click on “TCP/IP” and click “Enable”.

      1. In some environments and installations, you may need to enable “Named Pipes” as well.

    5. If the process was missed during installation, set the logon type for “SQL Server Browser” under the SQL Server Services tab to “Automatic”.

    6. This completes the SQL Server Installation, Restoration, and Configuration process.

  3. PSIsafe Server Installation
    1. Run the downloaded executable after being sure to unblock and “Run as Administrator”.
    2. Complete the initial installation with the default settings (unless you have an alternate default storage

      location for the program files).

    3. When the “PSIsafe Server Setup” window appears, make sure to “Skip SQL Database creation, and then input the information accordingly.

    4. This completes the PSIsafe Server installation.


Final Registration and Repository Validation:

  1. Registration in System Settings
    1. Open PSIsafe Client or Management.
    2. Click the Gear icon in the bottom-right and select “System Settings”.
    3. Type in the default system password "sysman” and the Server IP address.
    4. After hitting “List”, select “Add”.
    5. Type in the relevant information to each field, including the SQL Server,
      Database, sysadmin credentials, and Company Name.
    6. Click “Generate Code”, copy this code to your clipboard, and then email for your Key.
    7. Enter the Key from your response email and click “Register” to complete.
  2. Associate Repositories through Management
    1. PSIsafe creates files called “CNG_DO_NOT_DELETE” when creating and associating a Repository with an active PSIsafe installation. This is the one and only occasion in which we will remove these files so that PSIsafe can re-associate the active installation with the new server.

        1. Identify the actual restored location of the repository path(s). This should be the parent level “CNG” path containing the numbered folders.

        2. Delete the “CNG_DO_NOT_DELETE” file present in the folder. (This is the only time it is appropriate to delete this file.)

        3. Open the Management console and ensure that each repository location is intact.

        4. You can manually browse to the migrated Repository location, or if the repositories have been moved to a new network location, the UNC path can be updated here.

        5. This completes the PSIsafe Server Migration.

Having Problems:

Any errors encountered while trying to complete this task? Don't worry we have dedicated Technical Support Engineers available to assist.


Phone: (949) 916 7700 ext 2

Hours of Operation: Monday - Friday (5:00 am - 5:00 pm pacific time | 8:00 am - 8:00 pm eastern time)


Keywords: PSIsafe Server Transfer, PSIsafe Server Migration, PSIsafe Migrate Server, Migrate PSIsafe Server, Migrate Safe Server

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.