Step 4: Update the configuration database to address the NLB cluster

[Applies to: Microsoft Dynamics CRM 4.0]

You must manually update the configuration database by adding the fully qualified domain name (FQDN) cluster name. To do this, follow these steps.

Warning

Incorrectly modifying the configuration database can cause unexpected behavior in the Microsoft Dynamics CRM system, or cause it to stop working. We recommend that you back up the Microsoft Dynamics CRM system before you start these steps. For information about how to back up the Microsoft Dynamics CRM system, see the Operating and Maintaining Guide that is part of this document set.

Run the following update statements against the configuration (MSCRM_CONFIG) database:

  • Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'ADWebApplicationRootDomain'
  • Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'ADsdkRootDomain'

For an Internet-facing deployment of Microsoft Dynamics CRM, run the following update statements in addition to the statements specified above:

  • Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'IFDWebApplicationRootDomain'

  • Update DeploymentProperties set NVarCharColumn = 'crmcluster.contoso.com' where ColumnName = 'IFDsdkRootDomain'

    Important

    Depending on how you deployed the Microsoft Dynamics CRM Server role group or separate server role installation, and the configuration of each server in the NLB cluster, the ADWebApplicationRootDomain and ADsdkRootDomain values may be different. For example, if you installed the application-server role group on a server in an NLB cluster that is named crmcluster1 in the contoso domain but installed the platform-server role group on a different server in a different NLB cluster such as crmcluster2 in the same domain, the FQDN will be different for each of the ADWebApplicationRootDomain and ADSdkRootDomain values.

    For a full server role deployment, replace crmcluster.contoso.com with the FQDN of the cluster. If you are using a TCP port other then 80 (non-secure HTTP) or 443 (secure HTTP or SSL), you must specify the port number by appending the FQDN name with :5555, where 5555 is the port number, such as crmcluster.contoso.com:5555.

© 2011 Microsoft Corporation. All rights reserved.