locked
Migrating CRM 2011 Organization to a new domain and Active Directory RRS feed

  • Question

  • Hi.

    Should I migrate CRM 2011 that I have implemented in SQL Sever 2008R2 Enterp to some new servers that are in a new domain and therefore a new active directory, where users were created manually (not imported), for what concerns me the following:
    How I can map the users of the group of new active directory, with the users of CRM organization that was in the other domain?
    What problems can occur and how could mitigate?

    I appreciate all your suggestions.
    Thank you very much.


    • Edited by MazingerJ Thursday, November 29, 2012 7:33 PM Incomplete
    Thursday, November 29, 2012 3:19 PM

Answers

  • Based on my experiences these are the two most common places to experience problems when migrating to a new domain.

    1. Backup the organization database(s) and restore it/them to a SQL Server in the new domain.
        Dynamics CRM requires you to use a SQL Server in the same domain so you will need to move the databases. If you move to a non-enterprise edition of SQL Server you should make a copy of the database on the existing SQL Server to run a script from the following KB article: http://support.microsoft.com/kb/2567984

    2. If Dynamics CRM has not been installed in the new domain beforehand then do a fresh installation with a dummy organization, then import the organization from the restored databases.
        During the import Dynamics CRM wants to map all the users (both enabled and disabled) from the existing organization to users in your new domain. To make this transition as easy as possible you should export separate lists of enabled and disabled users from the existing environment, then make sure that all the users are created in the new domain. Any disabled CRM users that also have been disabled/deleted in the old domain can be created and then set to expired after the organization import.

    - Marius


    Thursday, November 29, 2012 11:04 PM

All replies

  • I think you want to move your CRM 2011 database to a new domain, is that right?

    Part of the process would be to backup the CRM database and restore it to the new SQL Server. On the new CRM server in the new domain run the Deployment Manager and then under Organizations right-click and select Import Organization. Follow the wizard and you will be asked to map users in the CRM database to users in the new Active Directory.

    Do post again if you need more information.

    Thursday, November 29, 2012 9:49 PM
    Moderator
  • Based on my experiences these are the two most common places to experience problems when migrating to a new domain.

    1. Backup the organization database(s) and restore it/them to a SQL Server in the new domain.
        Dynamics CRM requires you to use a SQL Server in the same domain so you will need to move the databases. If you move to a non-enterprise edition of SQL Server you should make a copy of the database on the existing SQL Server to run a script from the following KB article: http://support.microsoft.com/kb/2567984

    2. If Dynamics CRM has not been installed in the new domain beforehand then do a fresh installation with a dummy organization, then import the organization from the restored databases.
        During the import Dynamics CRM wants to map all the users (both enabled and disabled) from the existing organization to users in your new domain. To make this transition as easy as possible you should export separate lists of enabled and disabled users from the existing environment, then make sure that all the users are created in the new domain. Any disabled CRM users that also have been disabled/deleted in the old domain can be created and then set to expired after the organization import.

    - Marius


    Thursday, November 29, 2012 11:04 PM
  • I have followed these steps and was able to import the organization on the new server. However, none of my accounts or entities are in the new organization.

    Any idea on what may be causing this?

    Thanks.

    Wednesday, October 16, 2013 3:29 PM
  • That sounds like you created a new organization rather than importing an organization. Is there any data in the new organization?

    Wednesday, October 16, 2013 4:48 PM
    Moderator
  • I found the problem. The documentation that the guy who created the organization left had some wrong information. It listed the wrong database on the wrong instance of SQL. After some snooping around I was able to find the correct database and it imported correctly. Thanks
    Thursday, October 17, 2013 1:59 PM