How do I migrate the Engagement Admin to a new server CCH® ProSystem fx® Engagement?

Notes: Prior to starting the Migration Process, please review this important information:

  • New server must be the same Engagement version. If different versions of the Engagement Admin are installed, the migration will fail.
  • Microsoft® SQL Server® versions - If the original server is using SQL 2008 or SQL 2008 Express, then the new server will have to use SQL 2008 or SQL 2008 R2, or SQL 2012 or (if supported) SQL 2014.
    • Please note that the version of SQL or SQL Express used is dependent on the version of Engagement being migrated. 
  • The following environments are not supported:

Important: To avoid data loss, users should check-in all binders 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. Close all Engagement applications.

  1. On the new server, install the same version of the Engagement Admin that is on the original server. Do not launch the application.
    • If possible, install the program to the same installation path as the path used on the original server. This will simplify the process.
  2. Open the Admin module on the original server.
  3. Locate the CFR(s) in the lower left hand corner.
  4. Right click on the CFR and select Properties.
  5. Locate the workpaper path and document it.
  6. Repeat steps 4 and 5 for each CFR.
  7. On the original server run the Engagement Database Backup and Restore Utility and perform a full backup of Engagement. 
  8. Locate the following services on the Old Server and disable them:
    • PFXSYNPFTService
    • PfxEngDesktop
    • Pfx.Engagement.WcfServices  (v7.0 and later versions only)
    • Pfx.Engagement.SocketService  (v7.2 and later versions only)
      • To disable the services: Right-click on the service, and select Stop. Then right-click on the service again, and select Properties. Change the startup type to 'Disabled' and select Apply. Close out of the Computer Management dialogue.
  9. Copy the .bak file created with the Engagement Database Backup and Restore Utility to the New Server.
  10. On the New Server run the Engagement Database Backup and Restore Utility and restore the .bak file that you copied from the Old Server.
  11. 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 server name.
      • Select Yes to accept the name change.
  12. If the path is different on the New Server, and you are on 6.x or 7.x, the you can use the CFR Workpaper utility located in the CD image\utilities folder.
  13. Copy the Workpapers folder from the Old Server, to the New Server's Workpapers folder.

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

  1. Have the user log in to Engagement.
  2. A message will display indicating that the program could not find the old server. Select OK
  3. Either select Browse and select the new Office Server, or type in the name of the new Office Server.
  4. Click OK.


  Solution Tools
 Solution Id sw17114
 Direct Link
Did this article answer your question or resolve your issue?

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