PSIcapture Fusion/PSIfusion: Server Migration

Step A. Installing PSIfusion on your New Server.

  1. Backup SQL database from current production server.
  2. Restore to new SQL server location or New Server. (Step A.2)
    1. You will have the old production Database restored to the new server location; Restored Database (Previous Production Database).
    2. We will be creating a fresh empty database in Step A, and not using the Restored Database until Step B.
  3. Have PSIGEN support reset your PSIfusion license key.
  4. Install PSIfusion on new server (STOP: make sure it is the same version as the old server this is very important).
  5. Open Deployment Manager utility and create a new deployment.
    1. Ensure the deployment is named the same as the previous deployment on the old Production Server.
  6. Configure connection string and ensure the database name within Deployment Manager matches the new location for server and ensure you have a different Database.
    1. Connection String Example: Server=Enter New Server Name;Database=Enter New Database;User ID=Recommend SA account;Password=Enter Password;
    2. Ensure in your Connection string you do not use the same database name as the restored Database. 
      1. We are creating a new fresh Database instance for the new server only at this point.
        1. mceclip0.png
  7. Enter recently reset license key into Deployment Manager.
    1. Select the License option and enter the product key that has been reset by PSIGEN Support.(Refer to Step 3)
  8. Select the Save button once you have entered the license correctly.
  9. Login as administrator and confirm clean environment.
    1. Should you fail to be able to launch this may be do to an issue with the Internet Information Services site not installing correctly. 
      1. Click here to Build IIS Application Pool and Site Manually
    2. You should now have a freshly installed instance of PSIfusion on your new server.


Step B. Moving Configuration data from previous Production Server to New Server. 

  1. Ensure you have the old Production Server and the Current Production Server open. You will need both to complete the steps below.
  2. Stop Fusion Services within Services.msc application.
  3. Go to the Old Production Server and reference original file to locate the Deployment ID. [C:\ProgramData\PSIGEN\Fusion\Deployments.xml].
    1. Example: <Deployment ID="{6a88ba36-72f4-46db-9e21-52cc0c6c3017}"
      1. Bold Text is the physical Deployment ID ensure you maintain the same formatting when editing.
        1. mceclip4.png
  4. Open [C:\ProgramData\PSIGEN\Fusion\Deployments.xml] on the New Server and replace new deployment ID with old deployment ID (NOTEPAD.EXE MUST BE RUN AS ADMINISTRATOR TO SAVE FILE).
  5. Edit connection string to point to Restored Database (Previous Production Database).
    1. Ensure in the Connection string that the database name matches the Restored Database.
    2. This is the original Production database that you restored to the new server location in (Step A.2)
  6. Save Deployments.xml.
  7. Delete keys folder inside new deployment folder (C:\ProgramData\PSIGEN\Fusion\Deployments\"Deployment Name").
  8. Copy keys folder from old deployment folder and paste into new deployment folder.
  9. Copy C:\ProgramData\PSIGEN\Fusion\Organization from old server to new server.
  10. Start Fusion Services within Services.msc application. (If services fail to remain started proceed to Step C.)
  11. Run Deployment Manager as Administrator.
    1. Example: 
      1. mceclip3.png
  12. Edit Deployment and save.
  13. Have PSIGEN support reset license key again.
  14. Edit Deployment Manager again.
  15. Reapply license via the License Button.
  16. Test SQL Connection within Deployment Manager.
  17. Save Deployment Manager
  18. Restart Fusion Service.
    1. Open Services.msc and ensure the Fusion Service is stopped then started manually.
  19. Open PSIfusion and confirm it is pointing to old database with all users, teams, Document Profiles, and documents in place.
  20. You have completed your Server Migration of PSIfusion.


Step C. Fusion Services Fail to Start and require Administrator Password reset.

  1. Follow the steps below if the Fusion Service fails to start after (Step B, 10.)
    1. Verify that Fusion Services are stopped under Services.msc.
    2. Rename the follower folder.
      1. C:\ProgramData\PSIGEN\Fusion\Deployments\Fusion\Keys to
      2. C:\ProgramData\PSIGEN\Fusion\Deployments\Fusion\Keys_old
    3. Start Fusion Services
    4. New Keys folder will be created within C:\ProgramData\PSIGEN\Fusion\Deployments\Fusion\
    5. Navigate to C:\Program Files (x86)\PSIGEN\Fusion
    6. Launch PasswordGenerator.exe.
    7. Generate a new password for the Administrator account.
      1. The utility will provide a SQL statement for updating the Admin password via SQL Server Management Studio(SSMS).
      2. Ensure you login as and Administrator level account. An example of this would be the SA account.
      3. In that SQL statement, replace UserName=@Username with UserName='Administrator' (using single quotes)
        1. Example SQL Script: UPDATE dbo.Users SET PasswordSalt=Encrypted Value, PasswordSignature=Encrypted Value WHERE UserName='Administrator'
    8. After successfully resetting Administrator password, user should be able to log in as Administrator
    9. Administrator can manually reset the remaining user passwords from User Management under Administration within PSIfusion.
    10. Go back to (Step B, 11) and proceed with remainder of steps in Step B.
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.