How do I migrate CCH® ProSystem fx® Engagement or Workpaper Manager Administrator module to a new server?

Prior to starting the migration process, please review this important information:

  • It is best practice to have the new server be the same CCH ProSystem fx Engagement or Workpaper Manager version. If different versions of the Administrator module are installed on the new server, the migration may fail depending on the version installed.
    • See step 11 for more details. 
  • Microsoft SQL Server versions - The new server will need to have the same version of SQL installed that was installed on the original server or a newer version of SQL that is supported. Review the article below for supported technologies. 
  • The following environments are not supported:

To avoid data loss, all binders should be synchronized and checked in prior to the migration process.

Warning! The steps below only involved migrating the Admin module. If you have other modules on your server such as the Terminal Services Database, all binders from Engagement Terminal Services Client sessions must be checked into the Central File Room (CFR) prior to migration. The Terminal Services Database is not included with the backup of the CFR SQL databases. The Terminal Server Database cannot be migrated.

The following steps must be followed to avoid data loss.

  1. Close all Engagement applications.
  2. On the new server, install SQL & the same version of the Engagement or Workpaper Manager Administrator that is on the original server. Do not open Administrator Module on the new server. 
  • You can install Engagement 2018 on the new server if you are migrating and upgrading at the same time from Engagement 7.5 or Engagement 2017. See step 11 for further details.
  • You can install Engagement 2017 on the new server if you are migrating and upgrading at the same time from Engagement 7.2 or Engagement 7.5. See step 11 for further details.
    1. Install and configure a Microsoft® SQL Server® instance for Engagement.
    2. Install Engagement Administrator.
      • Warning! Do not open and configure the Administrator Module on the new server! This will cause the following message on the workstations once they go to log into Engagement:
        • "The firm for the office server you have specified is different from the firm for the other CCH ProSystem fx Engagement profiles on this computer."
      • If possible, install the program to the same installation path as the path used on the original server. This will simplify the process.
  1. Open the Admin module on the original server.
  2. Locate the Central File Room(s) in the lower-left corner.
  3. Right-click the Central File Room and select Properties.
  4. Locate the workpaper path and document it.
  5. Repeat steps 3 through 6 for each Central File Room.
  6. On the original server, run the Database Backup and Restore Utility and perform a full backup. 
  7. Locate the following services on the old server and disable them:
    • SQL Server (PROFXENGAGEMENT)
    • PFXSYNPFTService
    • PfxEngDesktop
    • Pfx.Engagement.WcfServices  (v7.0 and later versions only)
    • Pfx.Engagement.SocketService  (v7.2 and later versions only)
      • To disable the services, review the following steps.
      1. Click on the Windows Start Menu and type in: Services.exe. Click on Services.exe to open the Services window.
      2. Right-click on the each service listed above and select Stop.
      3. Right-click on the services again and select Properties. Change the startup type to "Disabled," and select Apply.
      4. Close out of the Services window.
  8. Copy the .bak file created with the Database Backup and Restore Utility to the new server.
  9. On the new server, run the Database Backup and Restore Utility and restore the .bak file that you copied from the old server.
    • If the version of Engagement or Workpaper Manager installed on the new server is a 2017 or 2018 release, you will receive a prompt stating there is a database version mismatch. If the backup file is compatible to restore onto the new version of Engagement or Workpaper Manager, you will be allowed to proceed. 
      • If you are restoring an older version of Engagement or Workpaper Manager database onto a newer version of Engagement or Workpaper Manager, then run the Pfx Database Utility to upgrade the databases to the correct version after the Backup and Restore Utility completes the restore.
        • The Pfx Database Utility is a version specific utility and can be found in the ?:\Pfx Engagement\Admin\Engagement CD Image\Utilities folder, where "?" is the drive Engagement or Workpaper Manager is installed on.
  10. Open the Administrator module on the new server for the first time.
    • Note: If the server name has been changed, you will be prompted to change the Engagement or Workpaper Manager server name. Select Yes to accept the name change.
  11. Copy the Workpaper folder from the old server to the new server. The default location of the Workpaper folder is located at ?:\Pfx Engagement\WM\Workpapers, where "?" represents the drive where Engagement or Workpaper Manager is installed. If you find that the Workpaper folder is empty or does not exist in ?:\Pfx Engagement\WM\Workpapers, then you can check the location of the Central File Room workpapers folder by right-clicking on the Central File Room in the Administrator module and choosing Properties. 
    • If you choose to place the Workpaper folder to a different path on the new server compared to the old server, then you must use the CFR Workpaper utility located in the CD image\utilities folder to configure the new Administrator Module Workpaper path. 
  12. If any of the following folders contain files, copy the content to the corresponding folder on the new server:
  • ?:\Pfx Engagement\Admin\Admin Packages\
  • ?:\Pfx Engagement\Admin\Archive\
  • ?:\Pfx Engagement\Admin\Transition Binder Packages\
    • "?" represents the drive where Engagement or Workpaper Manager is installed.
  1. If your Engagement configuration uses one or more secondary office servers, create an admin package on the migrated server and receive it on all other main and secondary office servers.

If the server name changed, each workstation that has Engagement installed will need to do the following:

  1. log into Engagement or Workpaper Manager.
  2. A message will display indicating that the program could not find the old server. Click OK. 
  3. Either click Browse and select the new Office Server, or type in the name of the new Office Server. Do not add "\\" to the beginning of the server name when typing in the server name. 
  4. Click OK.

Notes:

  Solution Tools
  Attachments
 Solution Id 000030920/sw17114
 Direct Link
To provide feedback on this solution, please login.

Your feedback about this article will help us make it better. Thank you!