Freigeben über

Domain renaming in a CRM 4.0 environment

  • Artikel

The renaming of a domain is an uncommon yet possible operation that might be required in an organization where CRM 4.0 is used. CRM 4.0 heavily relies on Active Directory (the database that supports the domain security enforcement) and changes in it can have a nasty impact on CRM. Following are the steps required to have CRM 4.0 still running after a domain rename operation. Please note that the process for renaming a domain can be different according to the version of the operating system used for the Domain Controllers.

 

Windows Server 2003 family provides tools with which can safely be used to rename domains to restructure a Windows 2003 forest. To download the Windows Server 2003 Domain Rename tool please go to: https://download.microsoft.com/download/5/6/d/56df978b-9a76-487e-80b7-0250289f2579/domainrename.exe

 

You can use the Windows Server 2008 domain rename process to change the names of your Active Directory domains, and you can also use it to change the structure of the domain trees in your Active Directory forest. This process involves updating the Domain Name System (DNS) and trust infrastructures as well as Group Policy and Service Principal Names (SPNs). Detailed information available on TechNet: https://technet.microsoft.com/en-us/library/cc816848(WS.10).aspx

 

Once the domain rename has been completed proceed with the following 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. Create a blank database in SQL and restore the original [OrganizationName]_MSCRM database to it.
  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 user principal names  (UPNs – the domain user accounts that have access to CRM 4.0) 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.

 

Greetings,
EMEA Dynamics CRM Team