SERVER SPECIFICATIONS
As such all specifications below are defined as virtual resources and do not necessarily map one to one to the actual
physical resources that the servers ultimately run on. Physical resources are dedicated to a virtual server only where
noted below.
Additionally, due to the virtual nature of the servers, it is relatively easy to increase (and in some cases decrease) the
allocated resources.
Version
Author
April 2011
Microsoft Corporation
Microsoft Corporation
Microsoft Corporation
David Reinhold
Microsoft Dynamics Ax Performance and
Scalability Engineer - Database
David Reinhold
Microsoft Dynamics Ax Performance and
Scalability Engineer - Database
Microsoft Corporation
Mike Ruthruff
Applies to: SQL Server 2005
Microsoft
March 2010
Microsoft
Namely, the bare bones option of a consolidated server hosting all services for the solution SQL AX,
SharePoint, SSRS, SSAS
Hardware and licensing costs could be reduced by consolidation of services, however application
component complexities and supportability issues could outweigh and cost benefit saved up front.
The consolidation of services onto one server may also introduce issues with the strategic direction
addition of any services to this one platform in the future would cause compatibility, scalability, testability,
supportability and performance issues.
Client to AOS: 100mb LAN connection with less than 5 milliseconds latency
AOS to Database: 1000mb LAN connection with less than 5 milliseconds latency
Integration Server to AOS: 1000mb LAN connection with less than 5 milliseconds latency
SharePoint to AOS: 1000mb LAN connection with less than 5 milliseconds latency
Microsoft Dynamics AX can operate on networks that use Internet Protocol Version 4 (IPv4) or Internet Protocol
Version 6 (IPv6)
Computers running Microsoft Dynamics AX components must have access to other computers in the same
Active Directory service domain, with Active Directory configured in native mode.
To support e-mail alerts in Microsoft Dynamics AX, an SMTP (Simple Mail Transfer Protocol) server must be
present in the environment.
During the implementation phase of this project, this server will be used to host two AOS instances, namely the
Config AOS Instance and the UAT/Pre-Production AOS Instance.
At go-live the Config AOS will be decommissioned and the Pre-Production Instance will be converted into the
Production AOS instance.
All Dynamics AX transaction processing will be performed by the AOS, so it is pertinent that this server is sized
adequately to handle the following user load:
65 Functional User CALs have been allocated to users that will access information via Enterprise Portal
CPU Count:
Memory:
OS:
LAN:
Disk:
Software:
CPU Count:
Memory:
OS:
LAN:
Disk:
Software:
CPU Count:
Memory:
OS:
SQL:
LAN:
Disk:
Note
When running on a virtualized environment it is pertinent to ensure that the virtual hard drives are deployed on the
underlying physical drives as to reduce/eliminate any contention on the physical drives IO capabilities.
2+
8GB
Windows Server 2008 R2 Enterprise Edition (x64)
SQL Server 2008 R2 Standard Edition CU3 or later required (x64)
LAN:
Disk:
2+
8GB
Windows Server 2008 R2 Standard Edition (x64)
SQL Server 2008 R2 Standard Edition (x64)
D and E (SQL drives) to be formatted with 64KB data chunks with 1024 offset (http://msdn.microsoft.com/enus/library/dd758814%28v=sql.100%29.aspx). All remaining drives formatted as 4KB data chunks (default).
2+
16384+ MB
Windows Server 2008 R2 Enterprise Edition (x64)
Microsoft SharePoint 2010 Enterprise SP1
Microsoft SharePoint Office Web Applications 2010
Dynamics AX 2012 R2
Disk:
Enterprise Search
Microsoft .NET Framework 3.5 SP1 (Certain AX components require .NET 4.0. These are highlighted in the AX
2012 R2 System Requirements document)
General
The AX Client delivered as a Published Application via Citrix Session off the existing server farm.
Note The Dynamics AX Remote Desktop Services Integration feature isnt supported on Citrix.