MS Dynamics CRM Lab Deployment

0602.Dyn-CRM_v_rgb.pngI would like to share with you my journey installing Microsoft Dynamics CRM in my lab for testing; and later to work the steps needed to protect the CRM environment using Veeam Backup & Replication.

During my learning, I spent some time learning about the deployment process. I thought it a good idea to share with you my experience with the processes, and perhaps help you speed up your Dynamics CRM deployment.

I am going to make this post short  and to the point. Our deployment will start by preparing the CRM environment, consisting of three servers:

  • Domain Controller
  • SQL 2014 Server
  • Windows 2012R2 server

Domain Controller

Our lab is based on Windows 2012R2 Active directory. an Organisation Unit (OU) and service accounts; these are all we need to add to our AD.

The accounts will be used during the MS Dynamics CRM deployment for CRM Sandbox Processing Service and CRM VSS Writer Service.

OU.png

adusers.PNG

SQL 2014 Server

If you are deploying a new TEST or PRODUCTION environment, and the Windows Server you intend to use for the installation of the SQL Server is a new server build, then you must install a .Net Framework 3.5 before you run the SQL Server installation. Use the PowerShell command line shown below to install  .Net Framework 3.5.

Install-WindowsFeature Net-Framework-Core

The SQL Server installation  is a straight forward installation, and the features we will need for our deployment demonstration are illustrated in this following figure.

sqldep.PNG

MS Dynamics CRM requires that the SQL Server Agent be running. To ensure it is not forgotten, it is a good idea to change the startup type to Automatic. See the yellow Startup Type in the figure below.

sqlagentservice.PNG

In addition to setting the Startup Type in the previous paragraph, change the SQL Reporting Services logon account to a non-local account. This account will be needed later when we run through the CRM Reporting Extension Setup.

Microsoft Dynamics CRM Server

Prepare the environment to host the Microsoft Dynamics CRM server.  Using the intended CRM server, download the Microsoft Dynamics CRM package. The link shown below will enable you to download the package.

https://www.microsoft.com/en-au/download/details.aspx?id=50372

On the completion of the .iso file download and extraction (or Mounting),  press the splash setup to run the installation. The rolling screenshots in the figure below will take you through the steps:

This slideshow requires JavaScript.

On successfully completing the installation process, you will be able to access the CRM Server using the web browser, and can now point to the CRM server-name on default Port 80.

On completing the installation, there will be no data present on the CRM Server. Sample data for testing or learning can be loaded using the steps below.

Adding MS Dynamics CRM Sample Data

Logon to the SQL Server, and then mount or browse the CRM .iso to the following folder:

“E:\Server\amd64\SrsDataConnector”

Run the “SetupSrsDataConnector” and run through the setup process.

The SQL Server name and the Reporting Server name will be the localhost, if you have successfully followed the instructions so far.

If the “Publishing CRM reports failed” error shown below appears during the setup, and most likely will, then follow the instructions beginning in the next paragraph.

sqlreperror.PNG

Run the Reporting Services Configuration Manager, and then delete the Encrypted content as illustrated below. Continue on by pressing the Retry button in the setup procedure.

EncrDelete.PNG

On completing the CRM Reporting Extension Setup, go back to the CRM Web GUI, then browse to: Setup -> Data Management -> Sample Data.

Press “Install Sample Data” at the bottom right.

sampledata.PNG

  • Note: The Sample data will be removed from the same location you are using to begin the install of the Sample Data.

Conclusion

Following these instructions will build your first ever Microsoft Dynamics CRM Server. You can experience the great features and functionality of the product using the Sample Data.

Our next blog will show you how to protect your new CRM environment.

Leave a Reply