Transferring Commit Installation from One Server to Another

From CommitCRM-Wiki

Jump to: navigation, search

Contents


Transferring CommitCRM Installation

Note: The instructions below apply to installation of CommitCRM version 3.7 and up.

  1. Backup ALL the Commit server files including ALL SUB-FOLDERS. Please make sure no one is using Commit while backing up and that CommitWebInterface and CommitServer Windows Services are stopped (if used)
  2. Copy ALL the Commit server files together with ALL subfolders from your old server (the one you are currently using) to a shared folder on your new server. All users and workstations must have full access rights to this share folder
  3. If you use the Commit Web Interface then you should uninstall it from the old server and install it on the new server using the following commands:
    1. <Old_Server>\Commit\WebInterface\CommitWebInterface.exe -uninstall
    2. <New_Server>\Commit\WebInterface\CommitWebInterface.exe -install
  4. If you use the Commit Alerts Server and/or Commit Email Connector then you should uninstall CommitServer service from the old server and install it on the new server using the following commands:
    1. <Old_Server>\Commit\Server\CommitServer.exe –uninstall
    2. <New_Server>\Commit\Server\CommitServer.exe -install
  5. If you use the Commit RMM Server then you should uninstall CommitRMMServer service from the old server and install it on the new server using the following commands:
    1. <Old_Server>\Commit\RMM\CommitRMMServer.exe –uninstall
    2. <New_Server>\Commit\RMM\CommitRMMServer.exe -install
  6. If you use any any third-party service or program that accesses CommitCRM database, stop the service or program.
  7. On the old server rename the "Commit" main folder to "Commit-Old". If the path to the Commit server folder on the new server is the same as it was on the old server (i.e. you assign the same drive letter to the Commit shared folder on the new server as it was used on the old server) then the transfer is complete. Otherwise, if the path to the new server is different than the original path used with the old server:
  8. Run the Commit client installation file on ALL network workstations:
    1. <New Server>\Commit\Utils\Install\InstallClient.exe


General Note: Documents files are not stored in Commit database but are rather stored on your hard disk like any other file. In addition to transferring Commit, as explained above, you should also transfer your documents files. Make sure that you keep the old path so the files referenced from Commit will keep pointing to the correct path.



  • If you experience any problems installing Commit™ , please contactour support department.

Transferring your installation when using CSD

These instructions are intended for Commit SQL Database users who need to migrate their CommitCRM servers to another computer. CommitCRM systems which do not use the CSD do not need to read this section.

  • Install the CSD on the new server (use the instruction email provided to you during purchase), when it is standalone (you cannot run two CSDs at the same time on the same network, so the server must be disconnected from your network when you install CSD). You should use the same installation instructions and trial codes you received with your purchase. In case you plan to purchase the CSD, you may consider purchasing first, and installing the final CSD version on the new server first.
  • Check that the service starts successfully. Make sure you have followed the CSD installation steps carefully, including setting up DEP. You should follow the instructions provided in the initial CSD email. If you do not have such an email (with the DEP instructions), please contact us at this email address, and a support rep will provide the necessary information.
  • Stop the CSD service on the old server.
  • Connect the new server to the network.
  • Make sure to re-install the clients shortcuts, so they will point to the new path (use <server>\Utils\Install\InstallClient.exe).
  • Having any problems running the clients after the transfer? Check out these helpful CSD Troubleshooting steps.

See Also

Personal tools