How to avoid impacts when reusing a CRM organization

resco mobile crm

In many CRM projects SAP is used as ERP system connected to Microsoft CRM. Many of our customers refresh their systems periodically. It means they deploy a backup of their productive SAP system in their consolidation environment. As result they get a database for test purposes based on current productive data.  As consequence the connected CRM system must also be refreshed.

 

The redeployment of a CRM database is quite simple.

  1. Create a backup of the MSCRM database you want to reuse.
  2. Restore the backup on your desired database server.
  3. Import the organization using the deployment manager.
  4. Adjust all connection strings used in webressources, custom reports etc.

Now we have a cloned organization we can use for test purposes or development or whatever you want. But please be aware there are some restrictions you need to know.

The organizationid is the same as in the organization you created a backup for. When you try to connect the plugin registration tool to both organizations you will get an error message like this:

Error

This is not a big issue. When you use Resco Mobile CRM you will experience a bigger problem.

Resco Mobile CRM requires one license per user. The license information is stored at the Resco servers and contains the organizationid as well as the userguid. When the user synchronizes his device with the CRM system the license is validated.

When we reuse the MSCRM database with the same organizationid the Resco server cannot differentiate both organizations. If a user is deactivated for Resco in one organization he will be also deactivated in the other one.

Another big issue will impact MS Outlook. If you are connected to both systems and after the refresh both organizations have the same organizationid you will not longer be able to open the Configuration Wizard. You can work within Outlook with the CRM because Outlooks connects to the systems using the URL und OrganizationName but in the registry the organizations are stored by ID. Deleting the registry keys would only fix this issue if both organization have different organizationid before trying to maintain the connections in the configuration wizard again.

As you can imagine this could have huge impacts on a productive environment.

As you can imagine this could have huge impacts on a productive environment.
To get rid of these behaviors we need to change the organizationid before importing the organization. Following steps are required:

  1. Create a backup of the MSCRM database you want to reuse.
  2. Restore the backup on your desired database server.
  3. Execute the sql scripts provided by Frenkie Smart on your restored database.

    http://social.microsoft.com/Forums/en-US/crmdeployment/thread/b8dfb946-bb02-4fb9-a92f-22ffb8b7071c

  4. Import the organization using the deployment manager.
  5. Adjust all connection strings used in webressources, custom reports etc.

,

No comments yet.

Leave a Reply