Install Microsoft Dynamics CRM 2013 Front End Server and Back End Server roles

 

Applies To: Dynamics CRM 2013

The following procedure installs Microsoft Dynamics CRM 2013 Front End Server and Back End Server roles on two separate servers that do not already have Microsoft Dynamics CRM Server installed. We recommend this configuration instead of a single Full Server deployment because it helps improve security and performance by isolating specific Microsoft Dynamics CRM Server services on each computer. As part of this procedure, the Microsoft Dynamics CRM Reporting Extensions are installed on the server where the Back End Server roles are installed, and the Deployment Tools are installed on the server where the Front End Server roles are installed. More information: Microsoft Dynamics CRM server roles

A backend and frontend deployment configuration requires two separate computers running Windows Server. This example uses two computers that are named CRMbackend and CRMfrontend.

Important

After Setup is completed, you must either import or create at least one organization to be able to connect a client to the Microsoft Dynamics CRM deployment.

In this example, the Back End Server role will be installed before the Front End Server role.

In This Topic

Install Back End Server role

Install Front End Server role

Create the Microsoft Dynamics CRM organization

Install Back End Server role

On the computer named CRMbackend complete the following procedure.

1. Meet all requirements specified in Microsoft Dynamics CRM system requirements and required technologies in the Planning Guide.

2. Log on to the domain as a user who has administrator-level privileges where Microsoft Dynamics CRM will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain.

3. Locate the Microsoft Dynamics CRM installation files. You can find the Microsoft Dynamics CRM Server 2013 download packages on the Microsoft Download Center.

4. In the folder where the Microsoft Dynamics CRM files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe.

5. On the Welcome to Microsoft Dynamics CRM Server 2013 Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next.

6. On the Product Key Information page, type your product key in the Product key boxes, and then click Next.

7. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept.

8. If Setup detects that components are missing, the Install Required Components page appears.

   • If you have already installed the required components, this page will not appear.

   • If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue.

   Note

   If you are prompted to restart the computer, do so, and then start Setup again.

9. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next.

10. On the Specify Server roles page, select all the Back End Server roles. Leave the rest blank.

    

11. On the Specify Deployment Options page, in the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of Microsoft SQL Server that will be used to store the Microsoft Dynamics CRM database (MSCRM_CONFIG).

12. On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed into, click OK, and then click Next. Microsoft Dynamics CRM security groups are created in this organizational unit.

13. On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next.

    The services are described below. For more information about the service accounts required to run these services, see Minimum permissions required for Microsoft Dynamics CRM Setup and services in the Planning Guide.

    • Sandbox Processing Service. Enables an isolated environment to allow for the execution of custom code, such as plug-ins. This isolated environment reduces the possibility of custom code affecting the operation of the organizations in the Microsoft Dynamics CRM deployment.

    • Asynchronous Processing Service. Processes queued asynchronous events, such as bulk email or data import.

    • Monitoring Service. This service will be installed with any Microsoft Dynamics CRM Server 2013 role installation to monitor Microsoft Dynamics CRM server roles that are running on the local computer. More information: Available individual server roles

    For each service, we recommend that you select a low-privilege domain user account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. The domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must be a member of the Performance Log Users security group.

    If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Microsoft Dynamics CRM Server 2013 for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. More information: How to use the ASP.NET utility to encrypt credentials and session state connection strings.

14. On the Select Microsoft Update Preference page, you must select either of the following options, and then click Next. For more information about the legal terms and privacy with Microsoft Update licensing, see Windows Update FAQ.

    • Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server will use the Microsoft Update settings on the computer.

    • I don’t want to use Microsoft update. You should only select this option if the computer uses another method to install updates such as by using Windows Server Update Services (WSUS).

15. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next.

16. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup.

17. Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install.

18. When the Setup program is finished, click Finish.

19. Run Microsoft Dynamics CRM Reporting Extensions Setup. More information: Install Microsoft Dynamics CRM 2013 Reporting Extensions

    Important

    Microsoft Dynamics CRM Reporting Extensions for SQL Server Reporting Services are required to complete the Front End Server and Back End Server deployment of Microsoft Dynamics CRM Server 2013.

20. When the Microsoft Dynamics CRM Reporting Extensions Setup has finished, complete the next procedure to install the Front End Server role.

Install Front End Server role

On the computer named CRMfrontend, follow these steps.

1. Log on to the domain as a user who has administrator-level privileges where Microsoft Dynamics CRM will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain.

2. In the folder where the Microsoft Dynamics CRM files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe.

3. On the Welcome to Microsoft Dynamics CRM Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next.

4. On the Product Key Information page, type your product key in the Product key boxes, and then click Next.

5. On the License Agreement page, review the information and, if you accept the license agreement, click I accept this license agreement, and then click I Accept.

6. If Setup detects that components are missing, the Install Required Components page appears.

   • If you have already installed the required components, this page will not appear.

   • If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue.

   Note

   If you are prompted to restart the computer, do so, and then start Setup again.

7. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next.

8. On the Specify Server roles page, select all the Front End Server and Deployment Administration Server roles. Leave the rest blank.

   

9. On the Specify Deployment Options page, click Connect to, and if necessary, upgrade an existing deployment, and then in the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of SQL Server that you entered previously, and then click Next.

10. On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed, click OK, and then click Next. We recommend that you select the same organization unit that you selected in the previous step.

11. On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next.

    The services are described below. For more information see Minimum permissions required for Microsoft Dynamics CRM Setup and services in the Planning Guide.

    • Application Service. This service runs the Microsoft Dynamics CRM web application that is used to connect users to CRM data.

    • Deployment Web Service. Manages the deployment by using the methods described in theMicrosoft Dynamics CRM SDK, such as create an organization or remove a Deployment Administrator role from a user.

      Important

      For each service, we recommend that you select a low-privilege domain user account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group.

      If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Microsoft Dynamics CRM Server 2013 for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. More information: How to use the ASP.NET utility to encrypt credentials and session state connection strings.

    • VSS Writer Service. The Microsoft Dynamics CRM VSS Writer service provides an interface to backup and restore Microsoft Dynamics CRM data by using the Windows Server Volume Shadow Copy Service (VSS) infrastructure.

    • Monitoring Service. This service will be installed with any Microsoft Dynamics CRM Server 2013 role installation to assist in event monitoring.

12. On the Select a Web Site page, click Create a new Web site or click Select a Web Site and select a website from the list. By default, Setup will use the default website.

    Important

    We strongly recommend that you verify the status of the existing website before you specify Setup to use an existing website. We strongly recommend that the website you select is configured for SSL. For more information see the IIS documentation. During the installation, Setup can bind the Microsoft Dynamics CRM application to the HTTPS website. If you select a network port other than a default port, ensure that the firewall does not block the port.

    When you select the Create a new Web site option, Setup creates a new website for Microsoft Dynamics CRM. You can specify the following option:

    • Port Number. Type the TCP port number that Microsoft Dynamics CRM clients will use to connect to the Microsoft Dynamics CRM Server 2013. The default port number is 5555.

13. Click Next.

14. On the Specify E-mail Router Settings page, in the E-mail Router server name box, type the name of the computer where the Email Router will be installed. This computer will route Microsoft Dynamics CRM email messages. If you will not install the Email Router you can leave this box blank. However, if you install the Email Router later you must add the computer where the Email Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroup security group. Click Next.

15. On the Select Microsoft Update Preference page, you must select either of the following options, and then click Next. For more information about the legal terms and privacy with Microsoft Update licensing, see Windows Update FAQ.

    • Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server will use the Microsoft Update settings on the computer.

    • I don’t want to use Microsoft update. You should only select this option if the computer uses another method to install updates, such as by using Windows Server Update Services (WSUS).

16. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next.

17. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup.

18. Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install.

19. When the Setup program is finished, click Finish.

Create the Microsoft Dynamics CRM organization

After Microsoft Dynamics CRM Server Setup program is finished installing the Back End Server, Front End Server, Deployment Administration Server roles, and Microsoft Dynamics CRM Reporting Extensions, you must create at least one organization to make the deployment available for users.

If you have a deployment of Microsoft Dynamics CRM 2011, you can import the Microsoft Dynamics CRM 2011 organization databases into the Microsoft Dynamics CRM 2013 deployment. For more information see the Microsoft Dynamics CRM Deployment Manager Help.

1. On the computer named CRMfrontend where the Deployment Administration Server role is installed, start Microsoft Dynamics CRM Deployment Manager.

2. Right-click Organizations, and then click New Organization. Complete the New Organization Wizard. For more information see the Deployment Manager Help.

See Also

Install Microsoft Dynamics CRM Server 2013
Install Microsoft Dynamics CRM 2013 Full Server role on a server without Microsoft Dynamics CRM installed