locked
Install CRM 2011 reusing CRM 4.0 Organization Unit RRS feed

  • Question

  • I am working  on a CRM 2011 for an upgrade and I was wondering if I could use the same Organizatio Unit I have used for the CRM 4.0 installation.

    What I can see on other Organization Units is that the installers(2011 and 4.0) adds some groups but they have an GIU identifier on the name wich make them different between differents deployments so there is not going to be a problem when the CRM 2011 tries to add his own grups.

    As far as I can see there is no any problem, has anybody tried this before?

    Sebas!

    Wednesday, May 23, 2012 8:13 PM

Answers

  • Hi Sebas,

    You are correct. Microsoft Dynamics CRM will create four group in the Organizational Unit: 

    PrivUserGroup
    ReportingGroup
    SQLAccessGroup
    PrivReportingGroup

    The group name will includes the GUID of your Organization, or "OrganisationID".

    Yes, Microsoft recommends that you use different OUs: 

    Multiple Microsoft Dynamics CRM Server 2011 versions in the same domain:
    Microsoft CRM 1.2, Microsoft Dynamics CRM 3.0, and Microsoft Dynamics CRM 4.0 can coexist in the same Active Directory domain. However, each version must be installed on a separate server. We recommend that you associate each version of Microsoft Dynamics CRM with a separate Active Directory organizational unit. This can prevent confusion if you have to add users or troubleshoot Active Directory issues. Page 93 or Planning Guide. 


    Here's what Microsoft says in the Implementation Guide regarding the configuration of Organizational Units: 

    Frequently, you may find it convenient to create a separate organizational unit (OU) for Microsoft Dynamics CRM users, and give Microsoft Dynamics CRM administrators limited administrative rights over that OU. They can make the change for any user in that OU, but not for any user outside it. Page 62 of Planning Guide

    The Microsoft Dynamics CRM security groups (PrivUserGroup, SQLAccessGroup, ReportingGroup, and PrivReportingGroup) must be in the same domain as the computer that is running Microsoft Dynamics CRM. These security groups can be located in the same organizational unit (OU) or in different OUs. To use security groups that are located in different OUs, you must install Microsoft Dynamics CRM Server 2011 by using an XML configuration file and specify the correct distinguished name for each pre-existing security group within the <Groups> element. For more information see Sample server XML configuration file for installing with pre-created groups in the Installing Guide. Page 77 of Planning Guide

    As far as I know, I see no problem reusing the same Organizational Unit. It will work. But it's not recommended from a management standpoint.  It's a matter of managing your Active Directory Objects as per your likings/corporate policies. 

    Hope this helps,

    Maxime

    • Proposed as answer by MaximeFortier Wednesday, May 30, 2012 12:46 PM
    • Marked as answer by Sebas2012 Wednesday, May 30, 2012 1:14 PM
    Wednesday, May 30, 2012 12:45 PM

All replies

  • If you do not want to do an inplace upgrade (Upgrade your CRM 4.0 Server), just setup a new CRM 2011 Server with a default Organisation. Don´t use the name of your CRM 4.0 Organisation. Just use "sample", "MicrosoftCRM" or something like this. After setup the system, import your CRM 4.0 Organisation. After sucessfully import your 4.0 Org you can deactivate your temp Org and delete it.

    Doing so, you´ll also have the chance to manually map the users (don´t use automatic) - this way you can correct deactivated users or users you actually have deleted in your AD.


    Carsten Groth http://carstengroth.wordpress.com Microsoft Dynamics Certified Technology Specialist

    Thursday, May 24, 2012 12:38 PM
  • Thak you Carsten, but reading the post againg I can see that I made a huge mistake.

    I was talking about Organizational Unit instead of Organization Unit. I am trying to reuse the Organizational Unit, the one we set before the installation.

    Sebastian.

    Thursday, May 24, 2012 12:45 PM
  • You could use same OU but it is not best practice

    Carsten Groth http://carstengroth.wordpress.com Microsoft Dynamics Certified Technology Specialist

    Thursday, May 24, 2012 12:49 PM
  • Hi Sebas,

    You are correct. Microsoft Dynamics CRM will create four group in the Organizational Unit: 

    PrivUserGroup
    ReportingGroup
    SQLAccessGroup
    PrivReportingGroup

    The group name will includes the GUID of your Organization, or "OrganisationID".

    Yes, Microsoft recommends that you use different OUs: 

    Multiple Microsoft Dynamics CRM Server 2011 versions in the same domain:
    Microsoft CRM 1.2, Microsoft Dynamics CRM 3.0, and Microsoft Dynamics CRM 4.0 can coexist in the same Active Directory domain. However, each version must be installed on a separate server. We recommend that you associate each version of Microsoft Dynamics CRM with a separate Active Directory organizational unit. This can prevent confusion if you have to add users or troubleshoot Active Directory issues. Page 93 or Planning Guide. 


    Here's what Microsoft says in the Implementation Guide regarding the configuration of Organizational Units: 

    Frequently, you may find it convenient to create a separate organizational unit (OU) for Microsoft Dynamics CRM users, and give Microsoft Dynamics CRM administrators limited administrative rights over that OU. They can make the change for any user in that OU, but not for any user outside it. Page 62 of Planning Guide

    The Microsoft Dynamics CRM security groups (PrivUserGroup, SQLAccessGroup, ReportingGroup, and PrivReportingGroup) must be in the same domain as the computer that is running Microsoft Dynamics CRM. These security groups can be located in the same organizational unit (OU) or in different OUs. To use security groups that are located in different OUs, you must install Microsoft Dynamics CRM Server 2011 by using an XML configuration file and specify the correct distinguished name for each pre-existing security group within the <Groups> element. For more information see Sample server XML configuration file for installing with pre-created groups in the Installing Guide. Page 77 of Planning Guide

    As far as I know, I see no problem reusing the same Organizational Unit. It will work. But it's not recommended from a management standpoint.  It's a matter of managing your Active Directory Objects as per your likings/corporate policies. 

    Hope this helps,

    Maxime

    • Proposed as answer by MaximeFortier Wednesday, May 30, 2012 12:46 PM
    • Marked as answer by Sebas2012 Wednesday, May 30, 2012 1:14 PM
    Wednesday, May 30, 2012 12:45 PM