locked
Setting up an environment for development on CRM RRS feed

  • General discussion

  • Hi to all,

    We are looking at setting up an environment for development on CRM.  This environment would consist of four areas: test, development, user acceptance, and production.  Our first thoughts were to create 4 separate domains, four exchange servers and 4 CRM servers.  A simple design that logical separates all 4 environments so no interaction or bleeding over of any kind occurs.  SQL would be the only service shared and only in the Test and Dev environments.  AD, exchange and CRM would all be virtualized in Test, Dev, and UA.  Of course Production would not share anything and would be unto it’s self.

    Now for the question.  Is there a better way?  Could AD and or Exchange be consolidated, in Test , Dev, and UA, without stepping on CRM in some way?  I’m not sure about running one connector in one exchange server for 3 CRM instances.   My gut is telling me to stay with the silo design, but I would like to get some feedback from some experts.

    Friday, November 6, 2009 8:07 PM

All replies

  • I have currently in my client 5 environments and all based on the same AD ( I have 5 OU - one per env.) and it work fine. It is easier to redeploy which is very often. The problem I have only with Exchange because we not have test one only production. Every environment have a own SSRS server and we are using 4 SQL clusters (we are merging one SQL cluster for 2 CRM env.)
    My Dynamics CRM Blog: http://bovoweb.blogspot.com
    Friday, November 6, 2009 11:11 PM
  • Hi,

    How to move the customizations that are developed using .Net and C$ coding?

    Regards,

    Vj

    Tuesday, July 31, 2012 5:47 PM