Microsoft Dynamics 365 Server roles
With Dynamics 365 Server, you can install specific server functionality, components, and services on different computers. These components and services correspond to specific server roles. For example, customers who have larger user bases can install the Front End Server role on two or more servers that run Internet Information Services (IIS) to increase throughput performance for users. Or, a Full Server role can be installed on one computer and Microsoft Dynamics 365 Reporting Extensions on another. If a server role is missing, Deployment Manager displays a message in the Messages area.
Use one of the following options to install server roles:
Run the Dynamics 365 Server Setup Wizard to select one or more server role groups or one or more individual server roles. If Dynamics 365 Server is already installed, you can use Programs and Features in Control Panel to add or remove server roles.
Configure an XML Setup configuration file and then run Setup at the command prompt to specify a server role group or one or more individual server roles. You cannot explicitly select the SQL Server "role" for installation during Dynamics 365 Server Setup. This is a logical role that SQL Server sets when you specify a particular instance of SQL Server, either local or on another computer (recommended) for use in the Dynamics 365 Customer Engagement (on-premises) deployment. For more information, see Microsoft Dynamics 365 Server XML configuration file.
Note
At any time after the initial installation of server roles, you can add or remove server roles in Programs and Features. For more information, see Uninstall, change, or repair Microsoft Dynamics 365 Server.
Important
If you have a Dynamics 365 Customer Engagement (on-premises) deployment that includes one or more Front End Server and Back End Server roles, the Language Pack must be installed on the computer that has the Front End Server role. If you have deployed individual server roles, the Language Packs must be installed on the computers that are running the Web Application Server and the Help Server roles.
Available group server roles
Although these server role groups are recommended for most deployments, any individual server role may be installed during Setup.
All server roles must be running in your organization’s network to provide a fully functioning system.
| Server Role Group | Description | Scope | Installation Method |
|---|---|---|---|
| Full Server | Contains all roles from Front End Server, Back End Server, and Deployment Administration Server. By default, Dynamics 365 Server Setup deploys the system as Full Server. In a Full Server deployment, server roles are not listed separately in Control Panel. To view the installed roles or make changes, right-click Microsoft Dynamics 365 Server , select Uninstall/Change, and then select Configure. | Deployment | Full |
| Front End Server | Enables the server roles for running client applications and applications developed with the Dynamics 365 Customer Engagement Web Services. | Deployment | Group or Full |
| Back End Server | Includes the server roles that handle processing asynchronous events, such as workflows and custom plug-ins, database maintenance, and email routing. These roles are usually not exposed to the Internet. For a list of server roles that are included in this group, see the following table. |
Deployment | Group or Full |
| Deployment Administration Server | Enables the server roles for components that are used to manage the Dynamics 365 Customer Engagement (on-premises) deployment either by using the methods described in the Dynamics 365 Customer Engagement Web Services or the deployment tools. Also includes the interface for database disaster recovery support. For a list of server roles that are included in this group, see the following table. |
Deployment | Group or Full |
Available individual server roles
| Server Role | Description | Server Group | Scope | Installation Method |
|---|---|---|---|---|
| Discovery Web Service | Finds the organization that a user belongs to in a multi-tenant deployment. | Front End Server | Deployment | Individual, Group, or Full |
| Organization Web Service | Supports running applications that use the methods described in the Dynamics 365 Customer Engagement Web Services. | Front End Server | Deployment | Individual, Group, or Full |
| Web Application Server | Runs the Web Application Server that is used to connect users to Dynamics 365 Customer Engagement (on-premises) data. The Web Application Server role requires the Organization Web Service role. | Front End Server | Deployment | Individual, Group, or Full |
| Help Server | Makes Dynamics 365 Customer Engagement (on-premises) Help available to users. | Front End Server | Deployment | Individual, Group, or Full |
| Asynchronous Service | Processes queued asynchronous events, such as workflows, bulk e-mail, or data import. | Back End Server | Deployment | Individual, Group, or Full |
| 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. | Back End Server | Deployment | Individual, Group, or Full |
| Email Integration Service | Handles sending and receiving of email messages by connecting to an external email server. | Back End Server | Deployment | Individual, Group, or Full |
| Deployment Web Service | Publishes the web service that provides the deployment interface described in the Microsoft Dynamics CRM SDK, such as those used to create an organization or manage the list of Deployment Administrators for the Dynamics 365 Customer Engagement (on-premises) deployment. | Deployment Administration Server | Deployment | Individual, Group, or Full |
| Deployment Tools | Consists of the Deployment Manager and Windows PowerShell cmdlets. Dynamics 365 Customer Engagement (on-premises) administrators can use the Windows PowerShell cmdlets to automate Deployment Manager tasks. Deployment Manager is a Microsoft Management Console (MMC) snap-in that deployment administrators can use to manage organizations, servers, and licenses for deployments of Dynamics 365 Customer Engagement (on-premises). |
Deployment Administration Server | Deployment | Individual, Group, or Full |
| Microsoft Dynamics 365 VSS Writer | The Microsoft Dynamics 365 VSS Writer service provides an interface to backup and restore Dynamics 365 data by using the Windows Server Volume Shadow Copy Service (VSS) infrastructure. | Deployment Administration Server | Deployment | Individual, Group, or Full |
| Microsoft Dynamics 365 Reporting Extensions | Provides reporting functionality by interfacing with the Dynamics 365 Customer Engagement (on-premises) system and SQL Server Reporting Services. | N/A | Deployment | Individual by using srsDataConnectorSetup.exe. |
| SQL Server | Installs the MSCRM_CONFIG database on the SQL Server. | N/A | Deployment | Individual during Dynamics 365 Server Setup or from Deployment ManagerEdit Organization Wizard. |
Scope definition
Deployment. Each instance of the server role services the entire deployment.
Organization. Each instance of the server role services an organization. Therefore, you can use a different server role instance for a given organization.
Installation method definition
Individual , Group, or Full. During Dynamics 365 Server Setup, you can install a server role individually, install one of the three predefined groups of server roles, or perform a Full Server installation that includes all roles. Or, you can select multiple individual server roles.
Microsoft Dynamics 365 Reporting Extensions . Install this role using srsDataConnectorSetup.exe on the computer where SQL Server Reporting Services is running.
Install the Microsoft Dynamics 365 Asynchronous Service to process only asynchronous events or email
The Microsoft Dynamics 365 Asynchronous Processing Service (NT style service) can be used to process asynchronous events and email, accounts, contacts, and tasks using server-side synchronization. Depending on what server roles you select during Microsoft Dynamics 365 Server Setup, you can configure the Asynchronous Service to have the following features.
Selecting both Asynchronous Service and Email Integration Service server roles installs the Asynchronous Processing Service that will be configured to process both asynchronous events and email, accounts, contacts, and tasks using server-side synchronization.
Selecting only the Asynchronous Service server role installs the Asynchronous Processing Service that will be configured to process only asynchronous events.
Selecting only the Email Integration Service server role, installs the Asynchronous Processing Service that will be configured to only process email, accounts, contacts, and tasks by using server-side synchronization.
Given these options, you can separate asynchronous events from server-side synchronization to help improve Customer Engagement system performance and simplify monitoring.
Microsoft Dynamics 365 Server role requirements
The following table describes the components necessary for each Dynamics 365 Server role. An "X" indicates the component is required for the Dynamics 365 Server role to install and function. Notice that, in most cases if a component is not already installed, Dynamics 365 Server Setup will install it.
Microsoft Dynamics 365 Server Role Prerequisites
| Component | Back End Server | Front End Server | Deployment Administration Server |
|---|---|---|---|
| SQL Server Reporting Services ReportViewer control | X | ||
| SQL Server Native Client | X | X | X |
| Microsoft Application Error Reporting Tool | X | X | X |
| Microsoft Visual C++ Runtime Library | X | X | X |
| Windows Server Web Server Role | X | X | |
| Indexing Service | X | ||
| Microsoft .NET Framework 4 | X | X | X |
| Microsoft Chart Controls for Microsoft .NET Framework | X | ||
| Azure platform SDK | X | X | X |
| Windows PowerShell | X | ||
| Microsoft URL Rewrite Module for IIS | X | ||
| File Server Resource Manager | X |
The following table describes the group membership for the Active Directory that is used by Dynamics 365 Customer Engagement (on-premises). An “X” indicates the group membership required for the service to function.
Group Membership Requirements
| Service | PrivUserGroup | SQLAccessGroup | PrivReportingGroup | ReportingGroup |
|---|---|---|---|---|
| Deployment Web Service service account | X | X | ||
| Web Application Service* | X | X | ||
| Asynchronous Service service account | X | X | ||
| Sandbox Processing Service service account** | ||||
| SQL Server service account | X | |||
| SQL Server Reporting Services server account | X | X | ||
| Email Router service account | X | |||
| Installing User/Service account | X | |||
| Individual user accounts in Dynamics 365 Customer Engagement (on-premises) | X | |||
| Unzip Service service account | X | |||
| Microsoft Dynamics 365 VSS Writer service account | X | X |
* The Web Application Service identity is applied to the CRMAppPool application pool. Subsequently, this identity is used by the Organization Service, Web Application, and Microsoft Dynamics CRM platform.
** The Sandbox Service does not need any Dynamics 365 Customer Engagement (on-premises) group membership.
Note
Email Router runs as a local system.
Important
- The Installing user should be a separate service account, but it should not be used to run any services.
- If any of the service accounts are created as users in Dynamics 365 Customer Engagement (on-premises), you may encounter various problems, some of which are potential security issues.
See Also
Microsoft Dynamics 365 multiple-server deployment
Support for Microsoft Dynamics 365 multiple-server topologies
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for