Microsoft Dynamics 365 multiple-server deployment
Updated: November 1, 2016
Applies To: Dynamics 365 (on-premises), Dynamics CRM 2016
[This topic is pre-release documentation and is subject to change.]
Microsoft Dynamics 365 Server deployments can include multiple servers, which provide additional performance and scaling benefits. However, with Microsoft Dynamics 365 Workgroup Server, server roles can’t be installed on separate computers. Therefore, all server roles are installed on every computer where you install Microsoft Dynamics 365 Server.
During Microsoft Dynamics 365 Server Setup, you can select to install a server role:
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 Microsoft Dynamics 365 deployment. Note that all server roles must be running and available on the network to provide a fully functioning Microsoft Dynamics 365 system.
You can install Microsoft 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 Server 2016.
For improved application performance, the computer or computers that run the Microsoft 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 Microsoft Dynamics 365 Server and the Active Directory domain controller are running should be on the same LAN to guarantee efficient Active Directory access to Microsoft Dynamics 365.
For each organization, Microsoft Dynamics 365 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 Microsoft Dynamics 365 databases is located near the Microsoft Dynamics 365 Server. This means there should be a high-speed, permanent network connection between the Microsoft 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 Microsoft Dynamics 365 depends on it for security information. If communication with Active Directory is lost, Microsoft Dynamics 365 will not function correctly. If communication with Active Directory is inefficient, Microsoft Dynamics 365 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 Microsoft Dynamics 365 and SQL Server computers.
© 2016 Microsoft. All rights reserved. Copyright