CRM 2013 Deployment with seperate roles RRS feed

  • Question

  • Hi,

    I was exploring the part of CRM 2013 installation, where it says the server roles can be separated thus making it highly scalable. I have a question for some one who has knowledge about this or has actually done this.

    I have gone through the topic which shows how to install Dynamics CRM 2013 using command line and a xml which contains the configuration. This topic lists out the complete XML; where all the roles are installed in the same server. Now my question is for the part where we can split up the roles.

    This and this post gives the XML for installing roles; but it seems that some things are missing. I mean if I were to separate the roles into two parts for my deployment, one XML containing the front end roles and the other the backend and deployment administration roles, will XMLs similar to the ones above work? Because things like the following tags are missing from the two sample XMLs:



    Where do I need to put these tags? Would these go in the front end roles or back end roles XML? Also, if I split up roles and do the CRM installation by XML, will it automatically create the AD Groups (SQLReportingGroup, UseProvGroup, etc.) and add the required users to them? Or does that need to be done manually?

    I am new to CRM administration, which explains this long question. :) Please could anyone assist me with this? Thanks.

    Admin QuikView Solution for CRM 2013

    Thursday, March 13, 2014 4:23 PM

All replies

  • Hi,

    Sorry to bump this thread, but please can someone assist me with this?

    Admin QuikView Solution for CRM 2013

    Friday, March 14, 2014 2:50 PM
  • The main article shows all the elements needed for an installation.

    The others show XML for servers with only one or more roles.

    The point is that whichever one you install first will need the details for the OU for the security groups, and other related settings. The second and subsequent servers you would not need these settings, it is not about which roles they have. You might install one front end server and then a second front end server, these would need different config files.

    You should also make sure that the <Database create="false" update="true" /> element is used for the additional servers. (the first would use <Database create="true" />).

    If you specify the OU, the groups are created for you and maintained, just as they are if you install using the wizard (unless you tell it not to maintain group memberships, but it sounds like you want them to be automatic). You don't specify the groups if you use the <OU> element.

    Hope this helps.
    Adam Vero, Microsoft Certified Trainer | Microsoft Community Contributor 2011
    UK CRM Guru Blog

    Sunday, March 16, 2014 11:04 AM