In this article I am going to explain the common scenarios where redeploying MS Dynamics CRM is required. Of course there could be others. But these are the most common of them. So what exactly happening when you redeploy a MS Dynamics CRM instance? Actually it copies the organization database to another. Following are the most common reasons to redeploy.
- Maintain a test environment with production data. This gives the opportunity to test newly implemented business logic with actual data and assess the impact of the new change. It also helps the support teams to trouble shoot bugs and recreate them without damaging live data.
- Also these test environments are heavily used before applying hardware upgrades and software upgrades. Again gives you the opportunity to assess the impact on new changes on the production data without harming the data.
- Creating a development environment with production data makes it easy for the developers to implement the change. They can test their changes with production data and fine tune the new changes. Also very hand when there are external consultants. They can be given a redeployment to do the changes separately and test it.
- There could be scenarios where you have to adopt to Active Directory Reorganizations. In such scenarios, redeployment options are very handy.
- When there are multiple deployments of MS CRM and during an organizational acquisition, the parent organization might want to consolidate everything into one deployment.
You need to keep in mind that, Dynamics CRM uses Active Directory for user authentication. And a link exists between Active Directory users accounts and Dynamics CRM user accounts. This bridge is maintained via GUIDs. That is every AD user has a GUID and the GUID for Dynamics CRM users are stored on MS CRM. When you move MS Dynamics CRM from one domain to another, the MS CRM users in the database must be linked with the appropriate GUIDs in the AD of the new domain. This process is known as mapping users.