locked
Puzzled by empty OU in Active Directory RRS feed

  • Question

  • Hi

    I have set up Dynamics CRM 2011 enterprise trial on a new VM running Windows Server 2008 R2.

    I created a new OU in AD for this install and gave the requisite permissions to the account under which I installed it. I selected this OU for Dynamics CRM when installing.

    Install has completed OK and the system works, but the OU seems to be empty. Relevant security groups such as  PrivUserGroup and PrivReportingGroup are in a different OU.

    Is this expected? Or did the install in fact use an OU other than the one I specfied?

    I don't mind too much with OU is used as this will be the only Dynamics CRM in the domain, but if something needs fixing I would like to do it now.

    Tim

    Monday, July 4, 2011 7:41 AM

Answers

  • Thanks.

    The log shows that Info.OUDistinguishedName is definitely the one I specified.

    It turns out I was jumping to conclusions. I was puzzled because when I looked at AD Users and Computers I saw that my new OU was empty and that the Dynamics groups existed in another OU. Now I find that my new OU *is* populated with four new groups. And that when I inspect the other groups I find they were created a few months back ... when my customer tried to install Dynamics CRM 4.0 but I think without success. I did not know that they had got as far as they did.

    So it seems all is well. Should I delete the old groups or leave well alone?

    Tim

     

    • Marked as answer by Tim Anderson Thursday, July 14, 2011 10:44 AM
    Monday, July 4, 2011 11:57 AM

All replies

  • That sounds weird - I've never come across the setup program using a different OU from the one specified. Was this a scripted install ?

    The CRM setup log (crm50svrsetup.log) will contain the detail of which OU the groups were added to, if you feel like investigating this further.

    My suggestion is that you're probably best leaving the groups where they are.


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Monday, July 4, 2011 10:36 AM
    Moderator
  • Thanks.

    The log shows that Info.OUDistinguishedName is definitely the one I specified.

    It turns out I was jumping to conclusions. I was puzzled because when I looked at AD Users and Computers I saw that my new OU was empty and that the Dynamics groups existed in another OU. Now I find that my new OU *is* populated with four new groups. And that when I inspect the other groups I find they were created a few months back ... when my customer tried to install Dynamics CRM 4.0 but I think without success. I did not know that they had got as far as they did.

    So it seems all is well. Should I delete the old groups or leave well alone?

    Tim

     

    • Marked as answer by Tim Anderson Thursday, July 14, 2011 10:44 AM
    Monday, July 4, 2011 11:57 AM
  • Hi Tim,

    If you are not using the old CRM then you can delete the old groups from OU.

    CRM Setup cannt use other OU's, may be you have selected the wrong OU.

     

    Regards,


    Khaja Mohiddin|||||     http://www.dynamicsexchange.com/
    • Proposed as answer by Khaja Mohiddin Thursday, July 14, 2011 10:39 AM
    Monday, July 4, 2011 4:11 PM
  • If you're sure the previous installation is not in use, I'd suggest you delete the old groups, mostly to avoid future confusion
    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    • Proposed as answer by Khaja Mohiddin Thursday, July 14, 2011 10:39 AM
    • Unproposed as answer by Tim Anderson Thursday, July 14, 2011 10:44 AM
    Monday, July 4, 2011 4:52 PM
    Moderator