If you have ever read the installation guide for CRM, you know that it’s not an easy task. The problem isn’t the actual installation, but rather the setup of all the fields and preparing the information so that CRM can be used correctly. While those steps are defiantly needed, there are times when a developer may need to install CRM just to connect and verify how data is sent to CRM. The following documentation details how to install CRM on a single Virtual PC. Please note that some of the items listed below I had not installed the first time through and had to go back and install them, so if they do not look exactly the same or I am missing a screen shot, that is the reason why.
Background information:
I created a Virtual PC running on Windows 7. The operating system is Windows Server 2008 x86.
Server Manager Roles/Features Installation
Make your Virtual PC a domain controller. For more information on how to create a domain controller in Windows Server 2009 look here: Installing Active Directory on Windows Server 2008. I used Method 3 (dcpromo).
Install IIS 7 from the Server Manager. You must install II6 Management Compatibility and Application Development (ASP.NET) and Security (Windows Authentication):
Install File Services Role from Server Manager, after several tries I discovered that you must install the Windows Server 2003 File Services:
SQL Server Installation
- Install SQL Server 2005 or 2008. I installed SQL Server 2008 and used a named instance of CRM, no real need that I am aware of to install on a named instance; BizTalk has just made me wary.
- Install SQL Reporting Services
- Be sure to open SQL Server and start the SQL Server Agent.
Office 2007 Installation
Install Office 2007. I installed Enterprise Edition.
CRM Installation
Install Microsoft Dynamics CRM Server from the CRM Installation options.
Choose Custom Installation and select both Server Roles:
If you get the following error, you are not connected to a network and need to install the domain controller (step 1).
Enter the name of the server, if you installed using a named instance you will have to use the named instance. I had to type the SQL Server name into the box. It was not in the drop down list.
Enter a Organization name.
Select a web site, a reporting server site and continue.
In the Active Directory Users and Computers, add a new Organizational Unit to store the CRM System groups. Go back to the CRM installation and select the group.
Select the security account for CRM. I kept the defaults:
I did not install the Email Router, but will install the CRM Outlook client:
By following the directions above, there should not be any red x’s on the following screen. If there are, you will have to fix the issues before continuing.
Restart your virtual PC
Outlook Configuration
Open Outlook and configure your email. Since this is a all-in-one box, you will need to create a POP3 account. I used hMailServer for the first time, and so far so good. Up until this point I had always used Windows Server 2003’s POP3 service, so I am not an SMTP/Exchange person and it took me some time to get hMailServer configured correctly, but once I did everything went smoothly.
CRM Outlook Client
Next, bring up the CRM installation screen and select Install Microsoft Dynamics Client for Outlook
Be sure to change the installation location as it cannot be installed in the same location as the server.
After the installation , the configuration wizard will appear:
Again, this is an all-in-one box, so select My Company as the option.
Internet Address is localhost:
Everything should be green on the Requirements screen:
I also installed the CRM Data Migration Manager, but the installation was straight forward.
Sample Data
There is sample data located at http://www.microsoft.com/downloads/details.aspx?familyid=D5F77EE7-3D01-4944-B5DC-C8CDC8123DF4&displaylang=en
My next steps was to start loading the sample data and to start understanding how everything works in CRM.
Posts
No comments:
Post a Comment