locked
Moving CRM 4.0 DB to new domain RRS feed

  • Question

  • Hi folks,

    Customer wants us to explore moving the DB over to new domain prior to moving CRM application server. MSCRM application server will remain in the old domain until the next phase. MSCRM is only one of the many applications they're migrating. It's a tightly coupled environment with multiple systems interfacing with one another. And they want to do it in phases.

    The production environment setup.

    2x MSCRM application servers (Load balance. apps01 and apps02)

    2x SQL Server (clustered. db01 and db02)

    I worked out the followings in the test environment with reference to Implementation Guide.

    1. Restore/Attach ORGANIZATION_MSCRM and MSCRM_CONFIG DB to SQL Server in new domain.

    2. On CRM Application server, edit registry settings (HKLM\Software\Microsoft\MSCRM) . Change the datasource.

    •  Configdb
    •  Database
    •  Metabase

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

    •  Update DeploymentProperties set NVarCharColumn = 'crm.enterprise.com' where ColumnName = 'ADWebApplicationRootDomain'
    • Update DeploymentProperties set NVarCharColumn = 'crm.enterprise.com' where ColumnName = 'ADsdkRootDomainUpdate'
    • Update Organization set ConnectionString = 'Provider=SQLOLEDB;Data Source=<FQDN of SQL Server in new domain>;Initial Catalog=Organization_MSCRM;Integrated Security=SSPI' where DatabaseName = 'Organization_MSCRM'

    4. Update connection string in app config and web.config for custom solutions.

    5. Reboot MSCRM server.

    Yes. I read the warning. 

    "Incorrectly modifying the configuration database (MSCRM_CONFIG) can cause unexpected behavior in the Microsoft Dynamics CRM system or cause the system to stop working. We recommend that you back up the Microsoft Dynamics CRM system before you complete these steps."

    I am also aware both SQL Server and CRM server must be in the same AD domain. http://technet.microsoft.com/en-us/library/dd979201.aspx

    I had made an effort to advise customer to accept Microsoft recommended solution in the following KB article to no avail.  http://support.microsoft.com/kb/952934

    Had anyone done similiar? Did I miss anything? Any inputs is appreciated.

     

    Regards,
    Daniel 

    • Edited by Daniel.Tan Monday, September 26, 2011 4:15 AM
    Monday, September 26, 2011 4:05 AM

Answers

  • Hi,

    If they ar emoving the CRM deployment into the new Active Directory then make sure to have the trust with old domain, in case of making direct changes the User windows SID will not updated into the tables and users would be unable to login. I believe you are only changing the server domains and not changing the server hardware. The above method t you have mentioned is unsupported (risky) and have not mentioned in any of Microsoft documentation, another alternate supported way could be:

    Manually perform these steps:

    1. Back up the [OrganizationName]_MSCRM database.
    2. Uninstall CRM 4.0 from the CRM Server.
    3. Remove the MSCRM_CONFIG Database if it still exists in the SQL Server Instance.
    4. Reinstall CRM 4.0 to a clean set of databases.
    5. Restore the original [OrganizationName]_MSCRM database in SQL Server.
    6. Navigate to the CRM Deployment Manager
    7. Import the new Organization Database. During the import, the wizard will allow to remap the user from the old ones to the new ones in new domain and also to the new ones with a different domain suffix.

    Additional configurations may be required according to which solution has been adopted for authenticating the services/Web Application pools, in terms of creating the necessary Service Principal Names (SPNs) but these operations are those normally carried out during the CRM 4.0 installation process.

    Please also refer this: http://blogs.msdn.com/b/emeadcrmsupport/archive/2010/02/26/domain-renaming-in-a-crm-4-0-environment.aspx


    Jehanzeb Javeed

    http://worldofdynamics.blogspot.com
    Linked-In Profile |CodePlex Profile

    If you find this post helpful then please "Vote as Helpful" and "Mark As Answer".
    • Proposed as answer by Khaja Mohiddin Monday, September 26, 2011 1:14 PM
    • Marked as answer by Daniel.Tan Wednesday, September 28, 2011 4:11 AM
    Monday, September 26, 2011 12:41 PM

All replies

  • Hi,

    If they ar emoving the CRM deployment into the new Active Directory then make sure to have the trust with old domain, in case of making direct changes the User windows SID will not updated into the tables and users would be unable to login. I believe you are only changing the server domains and not changing the server hardware. The above method t you have mentioned is unsupported (risky) and have not mentioned in any of Microsoft documentation, another alternate supported way could be:

    Manually perform these steps:

    1. Back up the [OrganizationName]_MSCRM database.
    2. Uninstall CRM 4.0 from the CRM Server.
    3. Remove the MSCRM_CONFIG Database if it still exists in the SQL Server Instance.
    4. Reinstall CRM 4.0 to a clean set of databases.
    5. Restore the original [OrganizationName]_MSCRM database in SQL Server.
    6. Navigate to the CRM Deployment Manager
    7. Import the new Organization Database. During the import, the wizard will allow to remap the user from the old ones to the new ones in new domain and also to the new ones with a different domain suffix.

    Additional configurations may be required according to which solution has been adopted for authenticating the services/Web Application pools, in terms of creating the necessary Service Principal Names (SPNs) but these operations are those normally carried out during the CRM 4.0 installation process.

    Please also refer this: http://blogs.msdn.com/b/emeadcrmsupport/archive/2010/02/26/domain-renaming-in-a-crm-4-0-environment.aspx


    Jehanzeb Javeed

    http://worldofdynamics.blogspot.com
    Linked-In Profile |CodePlex Profile

    If you find this post helpful then please "Vote as Helpful" and "Mark As Answer".
    • Proposed as answer by Khaja Mohiddin Monday, September 26, 2011 1:14 PM
    • Marked as answer by Daniel.Tan Wednesday, September 28, 2011 4:11 AM
    Monday, September 26, 2011 12:41 PM
  • Hi,

    Please follow this steps:

    1. Take backup for Org_MSCRM DB

    2. Delete the MSCRM_CONFIG DB

    3. Uninstall the CRM and Install again in new server.

    4. While installing CRM give new DC

    5. Restore the Org_DB.

    6. Imports all customization.

     

     


    Thanks & Regards, MS CRM Consultant, V.Surya.
    Tuesday, September 27, 2011 6:48 AM
    Answerer
  • Thank you for your valuable input, Javeed. We had proposed to the customer to procure a new server in the new domain to setup a new CRM installation. Frankly, I had never thought of reusing or keeping the current servers.

    Unfortunately, against our advice, customer insists to move the DB to the SQL server in new domain before moving CRM server.  

    • Edited by Daniel.Tan Wednesday, September 28, 2011 4:49 AM
    Wednesday, September 28, 2011 4:25 AM