Share via

Option 3: Rehome or configure an existing Microsoft Dynamics CRM Server 2013 deployment that connects to a SQL Server cluster that stores both the configuration and organization databases

  • Article

 

Applies To: Dynamics CRM 2013

Configure your existing Microsoft Dynamics CRM Server 2013 server to use the SQL Server cluster that contains both the configuration and organization databases.

Configure an existing CRM server to use the SQL Server cluster that contains both databases

  1. Follow the procedure in the previous section to create the SQL Server cluster. Option 1: Install a new Microsoft Dynamics CRM Server 2013 deployment

    Important

    Before you complete the following steps, make sure that users are not connected to, or accessing, the Microsoft Dynamics CRM system. You can do this by disabling the organization. To do this, right-click the organization and then click Disable.

  2. Back up the MSCRM_CONFIG and OrganizationName_MSCRM databases that are on the existing SQL Server.

  3. Restore the MSCRM_CONFIG and OrganizationName_MSCRM databases to the SQL Server cluster shared disk. More information:Backing Up and Restoring Databases in the SQL Server

  4. On all nodes in the cluster, modify Windows registry subkeys.

    Warning

    Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system and Microsoft Dynamics CRM. We can’t guarantee that these problems can be resolved. Modify the registry at your own risk.

  5. Update the configdb registry subkey on the computer that is running Microsoft Dynamics CRM Server 2013. To do this, follow these steps:

    1. On the computer that is running the Microsoft Dynamics CRM web application, click Start, click Run, type regedit in the Open box, and then click OK.

    2. Locate the following registry subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM

    3. Right-click configdb, and then click Modify.

    4. In the Value data box, change the data source to the name of the new virtual SQL Server, and then click OK. For example, the string value in the Value data box should resemble the following:

      Data Source=NewSQLServer;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI

    Note

    • If multiple Microsoft Dynamics CRM Server 2013 roles are in your deployment, you must update the registry keys for all the server roles.

    • If you use the Microsoft Dynamics CRM Reporting Extensions and if you are not moving the Microsoft SQL Server Reporting Services server, you must update the configdb subkey on the computer on which the Microsoft Dynamics CRM Reporting Extensions is installed.

  6. Configure Microsoft Dynamics CRM Server 2013 to connect with the new instance of SQL Server where the organization database is now located. To do this, follow these steps:

    1. On the computer that is running the Microsoft Dynamics CRM Server 2013 web application, start Deployment Manager. To do this, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager.

    2. Expand the Deployment Manager node, and then click Organizations.

    3. If the organization is not already disabled, right-click the organization, and then click Disable.

      Warning

      When you disable an organization, users will no longer be able to access Microsoft Dynamics CRM for that organization.

    4. Click Yes to disable the organization.

    5. In the list of organizations, right-click the organization, and then click Edit Organization.

    6. In the Edit Organization Wizard, in the SQL Server box, type the virtual SQL Server name for the SQL Server cluster that you created earlier, and then click Next.

    7. On the System Requirements page, after a successful diagnostics check, click Next, and then click Apply.

    8. Click Finish.

    9. Enable the organization. To do this, right-click the organization, and then click Enable.

  7. Reset the IIS services on the computer that is running IIS where the Microsoft Dynamics CRM Server 2013 web application is installed. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

See Also

Microsoft Dynamics CRM Server 2013 installation
Option 2: Rehome or configure an existing Microsoft Dynamics CRM Server 2013 deployment that connects to a SQL Server cluster that stores only the organization database