Dynamics 365 Customer Engagement (on-premises) multiple-server deployment

Dynamics 365 Server deployments can include multiple servers, which provide additional performance and scaling benefits.

Install server roles by running Microsoft Dynamics 365 Server Setup

During Microsoft Dynamics 365 Server Setup, you can select to install a server role:

  • Individually.

  • As one of the three predefined groups of server roles.

  • As a full server installation that includes all roles.

Server roles let you increase flexibility and scalability of the Dynamics 365 Customer Engagement (on-premises) deployment. Note that all server roles must be running and available on the network to provide a fully functioning Dynamics 365 Customer Engagement (on-premises) system.

Install server roles by running Microsoft Dynamics 365 Server Setup at the command prompt

You can install Dynamics 365 Server roles and Microsoft Dynamics 365 Reporting Extensions from their respective installation disks or file download location unattended by using the command prompt. The required setup information is provided to the Setup program both as command-line parameters and as an XML configuration file that the Setup program references. More information:Use the Command Prompt to Install Microsoft Dynamics 365.

Microsoft Dynamics 365 Server placement

For improved application performance, the computer or computers that run the Dynamics 365 Server roles and the computer that is running SQL Server should be on the same LAN. This is because of the large amount of network traffic passing between the computers. This is also recommended with Active Directory where the computer or computers on which Dynamics 365 Server and the Active Directory domain controller are running should be on the same LAN to guarantee efficient Active Directory access to Dynamics 365 Customer Engagement (on-premises).

SQL Server and Active Directory domain controller placement

For each organization, Dynamics 365 Customer Engagement (on-premises) stores all customer relationship management data in a SQL Server database. Make sure that the computer on which SQL Server is running that maintains the Dynamics 365 Customer Engagement (on-premises) databases is located near the Dynamics 365 Server. This means there should be a high-speed, permanent network connection between the Dynamics 365 Server and the computer that is running SQL Server. A network communications failure between these computers can result in data loss and service becoming unavailable.

The same is true for Active Directory because Dynamics 365 Customer Engagement (on-premises) depends on it for security information. If communication with Active Directory is lost, Dynamics 365 Customer Engagement (on-premises) will not function correctly. If communication with Active Directory is inefficient, Dynamics 365 Customer Engagement (on-premises) performance will be affected. Therefore, it is important to put an Active Directory domain controller on the same high-speed, permanent network connection as the Dynamics 365 Customer Engagement (on-premises) and SQL Server computers.

See also

Microsoft Dynamics 365 supported configurations
Microsoft Dynamics 365 Server roles
Support for Microsoft Dynamics 365 multiple-server topologies