System requirements for Microsoft Dynamics CRM 2011 can be found at here.
We’ll install the CRM software on three different servers:
running Microsoft Windows Server 2008 R2 x64 Standard or Enterprise and Microsoft SQL Server 2008 R2 or 2012 x64 Standard or Enterprise
Dynamics CRM Server
running Microsoft Windows Server 2008 R2 x64 Standard or Enterprise
running Microsoft Windows Server 2008 R2 x64 Standard or Enterprise
Having a separate ASync server would be optimal for a production environment, but is not required. Another thing to note is that Windows Server 2008 Server Core options is not supported. Nether are Itanium based systems. Same environment works perfectly fine on VMware’s virtualization platform (ESXi) even though Microsoft obviously prefers Hyper-V.
Dynamics needs to be installed on a computer that is a member of a domain which is running in one of the following AD Directory Service domain modes:
– Windows 2000 Mixed
– Windows 2000 Native
– Windows Server 2003 Interim
– Windows Server 2003 Native
– Windows Server 2008 Interim
– Windows Server 2008 Native
Things to note:
– Server running Microsoft Dynamics CRM cannot be an Active Directory domain controller (unless it is running a supported version of Windows SBS).
– if you install Dynamics CRM software on a server that is a member of an Windows 2000 mixed-mode domain, you cannot add uses to MS Dynamics CRM that are located in a different domain
– installing MS Dynamics CRM Server 2011 in an LDAP directory that is running Active Directory Application Mode (ADAM) is not supported
We’ll start with the installation the SQL Server software on the SQL Server. Insert your installation media and start installation of Microsoft SQL Server 2008 R2.
When prompted select SQL Server Feature Installation setup role.
On the Feature Selection menu select the following:
– Database Engine Services
– Analysis Services
– Reporting Services
– Business Intelligence Development Studio
– Client Tools Connectivity
– Integration Services
– Management Tools
At the Instance Configuration menu, specify the instance name as well as the directory where you’d like it installed. My preference is to keep the data on a separate volume (or different drive/storage location altogether).
Next, at the Server Configuration menu, specify Service Accounts you want to use.
Then, specify Authentication Mode you’ll be using. If you decide to go with Mixed Mode, specify the sa account password, and add user accounts for your SQL Server Administrators.
Do the same in the Account Provisioning section.
Next, we’ll select Install native mode default configuration at the Reporting Services Configuration menu.
Finally, click on the Install button, to start the installation.
Once finished you’ll see a message notifying you that the Installation has been completed successfully.
On your newly installed SQL server, start the SQL Server Configuration Manager and navigate to SQL Server Network Configuration > Protocols for YourInstanceName, and enable TCP/IP as well as Named Pipes. In order for the changes to take effect you’ll need to restart the SQL Server Agent service.
Next thing we’ll need to do is Install Microsoft CRM Reporting Extensions. You may want to wait for the Dynamics CRM server and ASync server installation (steps 2 and 3) before you install the Reporting Extensions.
During the installation I’ve ran into a problem. See error message below.
After reviewing the install log at c:\Users\%username%\AppData\Roaming\Microsoft\MSCRM\Logs\SrsDataConnectorSetup.log it looked like the installation failed due to a newer version of Microsoft Visual C++ Redistributable already present on the system.
Issue was resolved by removing the already installed Microsoft Visual C++ 2010 x64 Redistributable.
I had to restart the Reporting Extensions installation, but was able to start the installation properly.
You’ll be prompted to install Windows Identity Foundation.
Next, you’ll need to Specify Configuration Database Server. Click on the button next to the drop down menu to find your SQL server, then select your SSRS Instance.
Once you pass the System Checks click on the Install button to start installation. Once completed click on the Finish button.
Let’s install the Update Rollups next.
If you now connect to your SQL instance using the Microsoft SQL Server Management Studio, you’ll see some new databases that were created during the installation.
I typically change the recovery model of the database to Full. You can do so by right clicking on the database in question, and selecting Properties. Then under the Options section, select the appropriate Recovery model.
Next, we’ll want to crate a Maintenance Plan. We’ll do so by expanding the Management section on the left hand side, then right click in Maintenance Plans and select New Maintenance Plan.
First off, give it a name.
Then, select Maintenance Cleanup Task and drag it to the right twice (one task for the databases, the other for the transactional logs). Then select and drag Backup Database Task.
Configure the two Cleanup tasks.
Next, configure the Backup task for the database you’ll be using.
Then specify the sequence and pick the schedule for the Maintenance Subplan.
We should also create another subplan to backup the Transactional Logs.
Once done, click on the Save icon.
Dynamics CRM Server
Insert the installation media and click on Install Microsoft Dynamics CRM Server to start.
Select Get updates for Microsoft Dynamics CRM at the next screen
Next, you will be prompted to enter in the Product Key as well as to accept the license agreement.
Click on the Install button to start installing all of the required software (.NET Framework, Application Error Reporting, Windows Identity Foundation, Windows Azure Platform App Fabric SDK, SQL Reporting Service Report Viewer, SQL Native Client).
We’ll select everything except Back End Server in the Specify Server Roles menu. Back end server functionality will be installed on a separate server.
In the Specify Deployment Options menu, enter in the name of the SQL server you will be using (in our scenario this is the SQL server we’ve installed in step 1).
Next, in Select the Organizational Unit, specify the AD OU you’ll use for your Dynamics CRM System Groups.
Then, at the Specify Service Accounts window specify which service accounts you’ll be using.
Next you’ll be prompted to create a new website in IIS. As ADFS will be using the default website, I’ve created a new Web site with a custom port number of 5555.
In the next step you’ll be prompted to provide the server name of a machine that’ll be acting as your email router. This is an optional step as it can be configured at a later time. We’ll skip it for now.
As far as Windows Updates go, I like to install the rollups later on (as reboot will be required as well as to control which updates get installed), therefore at the Select Microsoft Update Preference stage I select I don’t want to use Microsoft Update.
Update Rollup 6 for Microsoft Dynamics CRM 2011 can be downloaded here.
Update Rollup 14 for Microsoft Dynamics CRM 2011 can be downloaded here.
Once you pass all of the System Checks, click on the Next button and then click Install.
Once installation has been completed successfully you’ll be prompted to restart the server.
Next let’s install the Update Rollups.
You’ll be prompted to restart the machine once the installation has been completed.
Once updates have been installed, we’ll need to start the Deployment Manager.
First thing we’ll want to do is add Deployment Administrators. We’ll do that by clicking on the New Deployment Administrator in the right hand side window pane.
Next, we’ll add a New Organization.
Specify the Display Name and Unique Database Name.
Next, specify your SQL Server name and the Report Server URL (i.e. http://servername/ReportServer
Once you pass the System Checks, click on the Create button to create a new organization.
Click on the Finish button once done.
Insert the installation media and click on the Install Microsoft Dynamics CRM Server.
Optionally, you can get updates for the Dynamics product during the installation.
Enter in the product key and accept the license agreement.
Install all the prerequisite software.
When prompted at the Specify Server Roles, we’ll select only the Back End Server this time around.
Search for your SQL server and select it, choose Connect to, and if necessary, upgrade an existing environment, then click on the Next button.
Specify Service Accounts you’d like to use.
Once you pass the System Checks, click on the Install button to start the installation.
Click Finish to restart the machine.
Next, let’s install the Update Rollup.
Now that all the software has been installed, let’s go to to your CRM server. You can do so using your web browser to navigate to http://crmservername:5555/organizationname/main.aspx
Once logged in, click on File then Options.
Here you can tweak some CRM settings. I like to disable Show Get Started panes on all lists under the General tab. In addition, I typically change the Set the number of records shown per page in any list of records to 250, as well as switch the Default mode in Advanced find to Detailed.
Now, let’s add some users. Click on the Settings tab in the lower left hand corner, then select System>Administration. The click on Users.
Click on New or New Multiple Users in the upper right hand corner.
Select the Security Role, then Access and License Type.
Note that under the E-mail Access Configuration section, you can pick and choose whether you want to use the E-mail router for your incoming/outgoing email.
Then browse for the account to add.