locked
CRM Production Environment Infrastructure Questions... RRS feed

  • Question

  • Looking for someone to offer some guidence...

    We're trying to set up a Production environment that would offer a private hosted environment for multiple deployments of Dynamics CRM 2011, which, in any deployment, may contain multiple tenants. We are looking at (for now) around 8 application servers. On the backend, we will have at least 2 SQL servers clusters with multiple instances to support all 8 deployments. We will also need 8 SSRS instances, and possibly a dedicated integration server. Some deployments may have a little as 100 users, while some may have a few thousand. We will also have SharePoint integration for all deployments.

    Questions:

    1. At what level of usage (both users and/or number of transaction on the front-end UI) plus workflows, plus reports would warrant putting SSRS on a set of dedicated SSRS servers
    2. Ibid, but for the SharePoint server (currently, I think, there's talk of having only 1 SP Server to host all deployments, including possible multi-tenancy)
    3. When would splitting out the Application Server in to separate server roles be warranted? Some clients will make heavy use of the SDK (for on-going integrations with external systems using Scribe or some type of ETL middleware, including custom service busses). Some will not, but may make heavy use of their SharePoint integration and workflows.
    4. Finally, I'm assuming that splitting the Application server roles onto multiple servers would not require an additional server license (since this was not mentioned in the installation guide, but then, why would it be), so if I'm wrong on this assumption, let me know.

    Also, these would all be running on virtual machines, so I ned some ideas in terms of recommended RAM requirements for each server.

    I apologize for these broad, general questions, but I haven't done much work with this type of infrastructure, so any advice is appreciated. Thanks,


    --Dodd
    • Edited by MDodd73 Wednesday, July 27, 2011 5:13 PM typos
    Wednesday, July 27, 2011 5:10 PM

Answers

  • Hi,

    These are always tricky questions to answer since it is hard to know the exact usage pattern of your customers, your hardware (or VM and host configuration in your case), and your full deployment configuration. To assist with this, please take a look at the Service Provider Planning and Deployment Guide. It provides guidance on various deployment topologies for various scales.

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=14259

    Of course, your mileage may vary based on your particular users' needs, so if you expect to have heavy usage of reporting, try splitting off SSRS onto their own machines. If you expect to have a lot of workflows and data import jobs, try splitting off the async service (in back end server group) onto its own machine separately from the front end machines. For heavy SDK usage, I would recommend having multiple front end machines sitting behind a load balancer. If you are a hosting partner, we recommend having redundant servers as much as possible to ensure high availability.

    Concerning the licensing question, please consult the pricing and licensing guide posted on CustomerSource/PartnerSource and reach out to your licensing specialist as necessary. Generally for a hosting partner deployment (aka SPLA model), there is simply a per user charge in the form of a subscriber access license (SAL) and there is not a separate server license fee (to allow our hosting partners to scale out by deploying as many servers as necessary). Generally speaking, for an on-prem deployment, you need to pay a CRM server license for each installation of CRM server and purchase a perpetual client access license (CAL) for each user. In your case, if this is under the SPLA model, you shouldn't have to pay for each additional CRM server instance.

    Hope this helps,
    Michael

    Monday, October 3, 2011 11:14 PM

All replies

  • Hello,

    I've the same question, I want to deploy 10 organization and i want to know the hardware requirements for a 100 users for organization.

    Have you find any documentation?

    Thanks

    Edo


    Edoardo Molinaro Product Specialist E-Mail: edo106@gmail.com
    Monday, October 3, 2011 12:33 PM
  • Hi,

    These are always tricky questions to answer since it is hard to know the exact usage pattern of your customers, your hardware (or VM and host configuration in your case), and your full deployment configuration. To assist with this, please take a look at the Service Provider Planning and Deployment Guide. It provides guidance on various deployment topologies for various scales.

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=14259

    Of course, your mileage may vary based on your particular users' needs, so if you expect to have heavy usage of reporting, try splitting off SSRS onto their own machines. If you expect to have a lot of workflows and data import jobs, try splitting off the async service (in back end server group) onto its own machine separately from the front end machines. For heavy SDK usage, I would recommend having multiple front end machines sitting behind a load balancer. If you are a hosting partner, we recommend having redundant servers as much as possible to ensure high availability.

    Concerning the licensing question, please consult the pricing and licensing guide posted on CustomerSource/PartnerSource and reach out to your licensing specialist as necessary. Generally for a hosting partner deployment (aka SPLA model), there is simply a per user charge in the form of a subscriber access license (SAL) and there is not a separate server license fee (to allow our hosting partners to scale out by deploying as many servers as necessary). Generally speaking, for an on-prem deployment, you need to pay a CRM server license for each installation of CRM server and purchase a perpetual client access license (CAL) for each user. In your case, if this is under the SPLA model, you shouldn't have to pay for each additional CRM server instance.

    Hope this helps,
    Michael

    Monday, October 3, 2011 11:14 PM