System requirements for on-premises for Microsoft Dynamics 365 Finance and Operations
Rahul Mohta
21,032
Like
Share
ReportSystem requirements for on-premises for Microsoft Dynamics 365 Finance and Operations
Network requirements
|
Value |
Web browser to AOS |
AOS to database |
|
Bandwidth |
50 kilobytes per second (KBps) per user |
100 megabytes per second (MBps) |
|
Latency |
Less than 250–300 milliseconds (ms) |
Less than 1 ms (local area network [LAN] only). AOS and the database must be co-located. |
Domain requirements
- VMs that host Finance + Operations components must belong to an Active Directory domain. Active Directory Domain Services (AD DS) must be configured in native mode.
- VMs that run Finance + Operations components must have access to each other. This access is configured in AD DS.
- The domain controller must be Microsoft Windows Server 2012 R2 or later, and the domain functional level must be 2012 R2 or more.
Minimum infrastructure requirements
|
Topology |
Role (node type) |
Recommended processor cores |
Recommended memory (GB) |
|
Production |
AOS, Data management, Batch |
8 |
24 |
|
Management Reporter |
4 |
16 |
|
|
SQL Server Reporting Services |
4 |
16 |
|
|
Orchestrator |
4 |
16 |
|
|
SQL Server |
8 |
32 |
|
|
Sandbox |
AOS, Data management, Batch |
4 |
24 |
|
Management Reporter |
4 |
16 |
|
|
SQL Server Reporting Services |
4 |
16 |
|
|
Orchestrator |
4 |
16 |
|
|
SQL Server |
8 |
32 |
Minimum sizing estimates for production and sandbox deployments
|
Topology |
Role |
Number of instances |
|
Production |
AOS (Data management, Batch) |
3 |
|
Management Reporter |
2 |
|
|
SQL Server Reporting Services |
1 |
|
|
Orchestrator** |
3 |
|
|
SQL Server |
2 |
|
|
Sandbox |
AOS, Data management, Batch |
2 |
|
Management Reporter |
1 |
|
|
SQL Server Reporting Services |
1 |
|
|
Orchestrator |
3 |
|
|
SQL Server |
1 |
|
|
Summary for production and sandbox topologies |
19 |
Initial estimates for the back-end SQL Server and AD DS
|
Role |
VMs/instances |
Cores |
Total cores |
Memory per instance (GB) |
Total memory (GB) |
|
|
Shared infrastructure |
SQL Server* (* SQL Server sizes are highly dependent on workloads.) |
2 |
8 |
16 |
32 |
64 |
|
File server/Storage area network/Highly available storage |
The back-end storage must be based on solid-state drives (SSDs) on a runtime storage area network (SAN). Size and input/output operations per second (IOPS) throughput is based on the size of the workload. |
|||||
|
Active Directory |
3 |
4 |
12 |
16 |
48 |
|
|
Summary for shared infrastructure |
5 |
28 |
112 |
|||
Storage requirements
- AOS– Finance + Operations uses a Server Message Block (SMB) 3.0 share to store unstructured data.
- SQL– The following options are viable:
- A highly available SSD setup
- A SAN that is optimized for online transaction processing (OLTP) throughputs
- High-performance direct-attached storage (DAS)
- SQL Server and data management IOPS– The storage for both data management and SQL Server should have at least 2,000 IOPS. Production IOPS depends on many factors.
- VM IOPS– Each VM should have at least 100 write IOPS
Virtual host requirements
Each virtual host should have enough cores for the infrastructure that is being sized. Multiple advanced configurations are possible, where SQL Server resides on physical hardware but everything else is virtualized. If SQL Server is virtualized, the disk subsystem should be a fast SAN or the equivalent.
Software requirements
- The Microsoft .NET Framework
- Service Fabric
Operating systems requirements
|
Microsoft Windows Server 2016 Datacenter or Standard |
These requirements are for the database and the Service Fabric cluster that hosts AOS. Only en-US OS installations are supported. |
SQL requirements
- Only 64-bit versions of SQL Server 2016 are supported.
- Only SQL_Latin1_General_CP1_CI_ASis valid for the server and database collation
- Microsoft SQL Server 2016 Standard Edition or Enterprise Edition
*This post is locked for comments