locked
Refresh Development Environment from Production RRS feed

  • Question

  • What is the best way to refresh a development CRM 2011 environment from production?  I have taken a backup of the production database and restored it to a new development database successfully, but when I try to import the organization in the deployment manager, I run into AD permission errors.  I have never run into this before, but this is the first time I have tried to copy a production database in one OU to create a dev environment in a different OU.  The error I am getting is:

    The current user does
    not have required permissions (read/write) for the following Active Directory
    group: CN=ReportingGroup {c7cd7146-a921-4298-a66e-24368aaee26d},OU=CRM
    DEV,DC=awc,DC=corp

    The ReportingGroup in the restored database has a different guid (the guid from production).  I believe this is the cause of the problem, but I don't have a solution.  Can I change the Reporting Group in the new database to the one in the dev OU?

    Friday, May 18, 2012 2:58 PM

Answers

  • The whole point of importing an Organisation from one environment into another is to re-map things like CRM Users to the new environment's AD account equivalents; the process will also add those mapped Users to the target deployments CRM AD Groups, such as 'ReportingGroup {deployment GUID}'.

    The error message is complaining that you as the Deployment Administrator, do not have sufficient permissions on the target deployment's ReportingGroup AD Group to complete the import - this has nothing to do with the source deployment.

    Is the user under which you are performing the Organisation import an AD Admin?  You will, at the very least read/write permissions on each of the CRM AD Groups and the requisite permissions to add whichever Users you map during the Organisation import to the necessary CRM AD Groups.


    --pogo (pat) @ pogo69.wordpress.com

    Friday, May 18, 2012 8:25 PM

All replies

  • Moving the database may blow away your development customizations so you will have to back them up and then re-import them after the refresh if you are replacing the CRM database.  Otherwise Scribe or some other data migration tool might better suit your needs.

    Jamie Miley
    Check out my about.me profile!
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!

    Friday, May 18, 2012 4:22 PM
    Moderator
  • The whole point of importing an Organisation from one environment into another is to re-map things like CRM Users to the new environment's AD account equivalents; the process will also add those mapped Users to the target deployments CRM AD Groups, such as 'ReportingGroup {deployment GUID}'.

    The error message is complaining that you as the Deployment Administrator, do not have sufficient permissions on the target deployment's ReportingGroup AD Group to complete the import - this has nothing to do with the source deployment.

    Is the user under which you are performing the Organisation import an AD Admin?  You will, at the very least read/write permissions on each of the CRM AD Groups and the requisite permissions to add whichever Users you map during the Organisation import to the necessary CRM AD Groups.


    --pogo (pat) @ pogo69.wordpress.com

    Friday, May 18, 2012 8:25 PM