locked
Shared Domain Controller or Seprate for Production and Developemt? RRS feed

  • Question

  • HI All,

         Please let me know, I am going to setup a new environment, what is better to share the production domain controller or keep the seprate DC for Development and why?

    Thanks

    Hassan

          


    Hassan

    Monday, January 14, 2013 12:43 AM

All replies

  • Hi Hassan,

    It should always be separate in my knowledge.

    This way you have the flexibility of having 2 active directories, one in dev and one in prod.

    The dev domain (if separate) you can create as many test users you can. Also in future if requirements change, then you can change the domain settings in dev and see the affect without touching prod environment.

    In my opinion the Development platform should be a separate domain from Prod. The UAT (user testing) environment could be in the same prod domain.

    I hope this helps. If my response answered your question, please mark the response as an answer and also vote as helpful.


    Ashish Mahajan, Microsoft Dynamics CRM Solutions Architect, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74


    Monday, January 14, 2013 1:04 AM
  • You can install multiple deployments of CRM under the same Active Directory though you must use a different OU for each. http://technet.microsoft.com/en-us/library/gg197600.aspx

    MS CRM Bing'd - http://bingsoft.wordpress.com
    Dynamics XRM Tools CRM 4 to CRM 2011 JavaScript Converter Tool
    CRM 2011 OData Query Designer
    CRM 2011 Metadata Browser
    CRM Forum Guidance

    Monday, January 14, 2013 11:35 PM
    Moderator
  • what about CRM 4.0?


    Hassan

    Tuesday, January 15, 2013 4:22 AM
  • CRM 4 and CRM 2011 use AD in a similar way, so the above can apply to either version.

    I find this choice is driven by the existing infrastructure. If there's already a separate test AD domain, then I'd use that, but I'd rarely ask for a new AD domain to be created for testing


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Tuesday, January 15, 2013 11:48 AM
    Moderator
  • Hi Hassanz,

    Is not common practice keeping separate AD infrastructure for DEV and PROD, unless you have reasons at development side to consider a DEV AD (e.g. custom AD schema) otherwise I would not recommend it.

    However if you have the extra servers and the extra time to admin a second AD infrastructure and feel more comfortable having it that way, you should go for it, just bear in mind the extra time it will take you to consider all the infrastructure differences in DEV and in PROD and the effort keeping it near like-to-like.


    Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com

    Wednesday, January 16, 2013 9:33 AM
    Answerer
  • @Rhett - I agree different OUs per Org (and certainly per deployment) is a good practice, but there is no "must". All the groups can co-exist in one OU without issues, in my experience.

    Hope this helps.
    Adam Vero, Microsoft Certified Trainer | Microsoft Community Contributor 2011
    Blog: Getting IT Right

    • Proposed as answer by Adam Vero Wednesday, June 12, 2013 8:16 PM
    Wednesday, January 16, 2013 2:42 PM
  • ok I may have been a bit forceful in my sentence but it is good practice to to help keep track of your deployment groups. J


    MS CRM Bing'd - http://bingsoft.wordpress.com
    Dynamics XRM Tools CRM 4 to CRM 2011 JavaScript Converter Tool
    CRM 2011 OData Query Designer
    CRM 2011 Metadata Browser
    CRM Forum Guidance

    Wednesday, January 16, 2013 4:25 PM
    Moderator