Setting Up Microsoft Dynamics 365 FInance and Operations ...

Purpose

The purpose of this document is to highlight the minimum and the recommended infrastructure configuration

required for Deploying a Microsoft Dynamics 365 Finance and Operations based IT solution On-Premise.

About Microsoft Dynamics 365 Finance and Operations

Microsoft Dynamics 365 for Finance and Operations is a Microsoft Enterprise Resource Planning (ERP) System for medium

to large organisations. The software, part of the Dynamics 365 product line, was first on general release in November 2016,

initially branded as Dynamics 365 for Operations. In July 2017, it was rebranded to Dynamics 365 for Finance and

Operations. At the same time, Microsoft rebranded their business software suite for small businesses (Business Edition,

Financials) to Finance and Operations, Business Edition, however, the two applications are based on completely different

platforms.

This solution can be deployed in the following three layouts:

1. Cloud: fully managed by Microsoft cloud service.

2. Cloud + Edge - a central cloud node with local application services and business data that is stored locally.

3. Local Business Data - business processes and data storage are on-premises.

In this document, we will discuss on the third (On-Premise \ Local Business Data) layout.

Requirements

For deploying Microsoft Dynamics 365 for Finance and Operations, the following artefacts are required:

Infrastructure

? Network:

? LAN ? If it is to be used in closed circuit environment (like from within office only, etc.)

? WAN ? If it is to be used externally (over internet)

? Peripherals:

? Firewall Server

? Defender \ Anti-Virus Server

? Domain:

? Domain Controller using Microsoft Active Directory

? ADFS ? If it is to be used externally (over internet)

? Storage:

? Microsoft SQL Server {SSMS, SSAS & SSRS with SSIS (if required)}

? Application:

? Application Object Server

Key Considerations

? All Servers hosting Application and Storage Services should be members of the same domain

? End-User computers\devices can by members of any domain or isolated workgroups

? Operating System for Servers hosting Application and Storage Services should use Microsoft Windows Server 2016

Datacentre or Standard Edition (x64 only)

? Database Services (SSMS, SSIS, SSRS) should be based on Microsoft SQL Server 2016 Standard Edition or Enterprise

Edition (x64 only)

? For using Microsoft Excel and Microsoft Word add-ins, Microsoft Office 2016 for Windows is required (on end-user¡¯s

computer device)

Page | 1

Layout Model

Microsoft Recommendations

Hardware Configuration (for hosting servers)

Role (node type)

Processor Cores

Memory (GB)

Application Object Server

8

24

Data Management

8

24

Batch

8

24

Management Reporter

4

16

SQL Server Reporting Services

4

16

Orchestrator

4

16

SQL Server

8

32

Minimum sizing estimates for Production Deployments

Role (node type)

Memory (GB)

AOS (Data management, Batch)

3

Management Reporter

2

SQL Server Reporting Services

1

Orchestrator (with Service Fabric services)

3

SQL Server

2

Page | 2

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download