Installing CRM

 

Preparing Your Environment

Microsoft Dynamics CRM requires several steps of preparation and execution. Below are the necessary components that should comprise your preparation checklist.

Documentation and Planning
Throughout this chapter we have prepared for a robust, secure, and scalable architecture. To ensure a successful implementation it is extremely important to document the design.

Pre-requisites Gathering
Each server and component of the installation includes a list of pre-requisites in the Microsoft Dynamics CRM Implementation Guide. Take this opportunity to completely document, verify, and consolidate server data, infrastructure, and user information. Ensure licensing is in place to not preclude progress as deployment proceeds.

Domain Considerations.

Part of the deployment requirements documentation should be a checklist of authorization accounts and permissions for installation. Best practice is to configure a new OU for the CRM AD groups for each new CRM deployment.

Online customers may choose to federate with Microsoft Online Services and benefit by synchronizing their local Active Directory and the Microsoft Online Services Portal.

Server Configuration
As part of the documentation and diagram of the entire deployment consider any potential upgrades, in particular Server and Client OS and SQL Server. This should include careful evaluation of SQL Server 2012, highlighting the potential costs and benefits especially related to

A full feature list of SQL Server 2012 is available here.

 

Evaluating the Installation
In preparation for deployment, it’s important to review the following components to be installed.  Document all of the various components that will be needed during the installation.  Those include:

 

  • CRM Application Server
  • SQL Server 20012/2008 R2
  • SQL Reporting Services
  • CRM Reporting Extensions
  • Email Router – later in this chapter
  • Language Packs
  • ADFS
  • SharePoint Server

Prior to installation a best practice is to create an Organization Unit in Active Directory to contain the CRM Security group that will be created during the installation.  Consider naming the OU with a nomenclature that you can easily identify, such as CRM or CRM Security groups.

It is also a best practice to add another Deployment Administrator in case the installer account is removed at some point in the future. These Deployment Administrators will just need rights to the CRM OU(s)

 

The following CRM Security groups are created in Active Directory during the installation:

PrivReportingGroup

PrivUserGroup

SQLAccessGroup

ReportingGroup

UserGroup

 

Accounts

  • Installer – Active Directory account that installs the application and creates databases
  • Deployment Administrator(s) – the installer account will be added as a Deployment Administrator
  • Sandbox Service Account – used for code execution in an isolated environment
  • Email Router Account – provides Email Router access to the CRM organization

Services

  • Async Processing Service
    • The Asynchronous service is installed with Microsoft CRM and runs outside the main Microsoft Dynamics CRM system process, resulting in an overall improvement in performance.  It is a managed queue for workflows, asynchronous registered plug-ins, and bulk operations such as quick campaign and campaign activity distribution, bulk emails and data imports.
    • Note: may need an SPN associated with it
  • Deployment Web Service – manages CRM web services
  • CRM IIS Application Pool Identity – CRM services and app pool

NOTE: This should be a service account and not be a CRM user

  • SQL Server Reporting Services – must be configured prior to CRM installation
  • Email Router Service – can be local system or domain account


Return to Top ▲Return to Top ▲