Share via

Support for Microsoft Dynamics 365 multiple-server topologies

  • Article

 

Applies To: Dynamics 365 (on-premises), Dynamics CRM 2016

This section provides examples of various multiple-server topologies.

In This Topic

Five-server topology

Multi-forest and multi-domain with Internet access Active Directory topology

Five-server topology

The five-server topology is for small to midsize user bases, typically 25 or fewer users concurrently using Microsoft Dynamics 365. The following example depicts a possible configuration running a supported version of Windows Server and the required and optional software technologies. It also includes a Full Server deployment of Microsoft Dynamics 365 Server that is configured for an Internet-facing deployment (IFD). For a complete list of the supported versions of the required and optional technologies, see Software requirements for Microsoft Dynamics 365 Server.

A five server topology can consist of the following configuration:

  • Server 1: Running on Microsoft Windows Server as a functioning domain controller.

  • Server 2: Running on Windows Server as a secondary domain controller and Active Directory Federation Services (AD FS) server.

  • Server 3: Running on Windows Server with IIS and an Active Directory Federation Services (AD FS) proxy.

  • Server 4: Running on Windows Server with an instance of Microsoft SQL Server the includes the database engine, Microsoft SQL Server Reporting Services, and Microsoft Dynamics 365 Reporting Extensions.

  • Server 5: Running on Windows Server, IIS, and a Full Server deployment of Microsoft Dynamics 365 Server configured for Internet-facing deployment (IFD).

  • CRMWebClient, CRMforOutlook, tablet, and phone devices: These computers and devices are running applications that are available, connecting from the Internet or the LAN-based network, such as Dynamics 365 for Outlook, Microsoft Dynamics 365 for tablets, and Microsoft Dynamics 365 for phones.

Diagram shows five-server topology in Dynamics CRM

Basic Microsoft Dynamics 365 five-server topology with Internet access example

Multi-forest and multi-domain with Internet access Active Directory topology

For very large user bases that span multiple domains and, in some cases, forests, the following configuration is supported. The following example depicts a possible configuration running a particular version of Windows Server and required software, such as SQL Server and Microsoft SharePoint.

The text and diagram show a possible deployment that lets users access Microsoft Dynamics 365 through the Internet by implementing Active Directory Federation Services (AD FS) supported by Front End Server roles that are isolated from user and resource domains on a perimeter network (also known as DMZ, demilitarized zone, and screened subnet) model.

For a complete list of the supported versions of these software technologies, see Software requirements for Microsoft Dynamics 365 Server.

Forest X: Domain A: Perimeter subnet

  • Network Load Balanced (NLB) virtual server consisting of the following two nodes:

    • Front End Server: Running Windows Server and Microsoft Dynamics 365 Server with the Front End Server role.

    • Front End Server: Another Windows Server running Microsoft Dynamics 365 Server with the Front End Server role.

    Note

    To use Microsoft Dynamics 365 Server with NLB requires manual configuration.

  • Active Directory Federation Services (AD FS) Server: Running on Windows Server as the Internet-facing claims-based authentication security token service.

Forest X: Domain A: Intranet

  • NLB virtual server consisting of the following two nodes:

    • Windows Server, Microsoft SQL Server Reporting Services, and Microsoft Dynamics 365 Reporting Extensions for SQL Server Reporting Services (Server X).

    • Windows Server, Microsoft SQL Server Reporting Services, and Microsoft Dynamics 365 Reporting Extensions for SQL Server Reporting Services (Server Y).

  • NLB virtual server consisting of the following nodes:

    • Front End Server and Deployment Administration Server: Running Windows Server and Microsoft Dynamics 365 Server with the Front End Server and Deployment Administration Server roles.

    • Front End Server and Deployment Administration Server: Another Windows Server running Microsoft Dynamics 365 Server with the Front End Server and Deployment Administration Server roles.

    Note

    To use Microsoft Dynamics 365 Server with NLB requires manual configuration.

  • Microsoft SQL Server failover cluster running the following two nodes:

    • Windows Server, SQL Server database engine (Server X).

    • Windows Server, SQL Server database engine (Server Y).

    Note

    To use Microsoft Dynamics 365 Server with SQL Server failover clustering requires manual configuration. More information: Set configuration and organization databases for SQL Server AlwaysOn failover

  • Windows Server running the Asynchronous Service server role.

  • Windows Server running the Sandbox Processing Service server role.

  • Windows Server running the Active Directory Federation Services (AD FS)Windows Server role.

  • Windows Server running Microsoft SharePoint (required for document management).

Forest Y: Domain B: Intranet

  • Exchange Server failover cluster consisting of the following two nodes:

    • Windows Server running Exchange Server (Server X).

    • Windows Server running Exchange Server (Server Y).

Diagram of conceptual enterprise deployment in CRM

Multiple forest with Internet access to Microsoft Dynamics 365 topology example

See Also

Microsoft Dynamics 365 multiple-server deployment
Upgrade a Microsoft Dynamics CRM 2015 Server

© 2016 Microsoft. All rights reserved. Copyright