System requirements for Microsoft Dynamics GP 10.0
Updated: May 17, 2007
Microsoft supports the following minimum client hardware requirements, server recommendations, and Terminal Services minimum hardware requirements for Microsoft Dynamics GP 10.0. (Note that the server recommendations are not the minimum server requirements.) The specific hardware that you will need for your configurations depends on environmental factors. To achieve individual performance expectations, you may need to increase these recommendations.
On This Page
note
Customers currently using Microsoft Dynamics GP 10.0 can refer to the Knowledge Base documents linked to below for more detailed information. Knowledge Base (KB) is part of CustomerSource and is a secure site available to customers on a service plan.
Client requirements
Operating system1 | One of the following: | • | Windows Vista Business, Ultimate, or Enterprise (32-bit and 64-bit) | | • | Windows XP Professional SP2 (32-bit only) |
|
Processor | Intel Pentium IV 2.4 gigahertz (GHz) or higher |
Available hard disk space | 800 megabytes (MB) or more on the system root |
Minimum available RAM | 512 MB (1 gigabyte (GB) recommended) |
Network card | 100-MB Ethernet Full Duplex or 1-GB Ethernet |
Microsoft Office2 | One of the following: | • | 2007 Microsoft Office system3 | | • | Office 2003 | | • | Office XP |
|
Microsoft Internet Explorer | Internet Explorer 7 or 6 SP1 |
Adobe | Adobe 8.0, 7.0, or 6.0 |
1See the 64-bit support tables in #4 in the Additional notes section to verify that all products you're using are compatible.
2Microsoft Office Outlook is required for the Outlook area to display on the Microsoft Dynamics GP home page.
3 The Microsoft Office Web Components are required for home page metrics. If you are using Office 2007, you must install the Office 2003 Web Components. Use the links below to install the components:
Server recommendations
Review the following customer profiles to determine which profile best reflects your environment based on user count, modules used, and transaction volume. Use that customer profile as a recommendation for your server hardware implementation.
Customer profile 1
The following profile applies if you:
| • | Use only Financial Series modules |
| • | Have 0-20 concurrent users for Microsoft SQL Server or 0-10 concurrent users for Microsoft SQL Server Desktop Engine (MSDE) 2000 or SQL Server 2005 Express Edition |
| • | Use Report Writer, Crystal Reports |
| • | Process fewer than 1,000 transactions a day |
| • | Import very little data |
| • | Have a dedicated server with SQL Server only |
| • | Recommend a dedicated server with MSDE 2000/SQL Server 2005 Express Edition only |
Database | One of the following: | • | SQL Server 2005 SP2 Standard Edition 32-bit, Workgroup Edition, or Express Edition | | • | SQL Server 2000 SP4 Standard Edition or Workgroup Edition | | • | MSDE 2000 SP4 |
|
Operating system1 | One of the following: | • | Microsoft Windows Server 2003 Standard Edition SP2, R2 Standard Edition SP2, x64 Standard Edition SP2, or R2 x64 Standard Edition SP22 | | • | Windows Small Business Server 2003 Premium Edition SP2 or R2 Premium Edition SP2 | | • | Windows Small Business Server 2003 Standard Edition SP2 or R2 Standard Edition SP23 |
|
Processor | One dual-core or two single-core4 |
Disk configuration (for SQL Server only) | | • | Minimum: RAID 5 for operating system, applications, and SQL database log and data files5 | | • | Recommended: RAID 1 for operating system and applications; RAID 5 for SQL database log and data files6 |
|
RAM | 1 GB or greater |
Network card | 100-MB Ethernet Full Duplex or 1-GB Ethernet |
1While you can install MSDE 2000 and SQL Server 2005 Express Edition on a non-server operating system, it is recommended you install those components on a server operating system. The only non-server operating system supported for MSDE 2000 is Windows XP Professional SP2. The only non-server operating systems supported for SQL Server 2005 Express Edition are Windows XP Professional SP2 or Windows Vista. (See #3 in the Additional notes section.)
2See the 64-bit support tables in #4 in the Additional notes section to verify that all products you're using are compatible.
3 MSDE 2000 and SQL Server 2005 Express Edition only.
4Ensure processors can be upgraded.
5More available disks will improve SQL Server performance.
6Recommend using a dual-channel fast and wide SCSI-2 controller.
Customer profile 2
The following profile applies if you:
| • | Use Financial Series modules |
| • | Use Distribution Series modules moderately |
| • | Use Field Service Series modules |
| • | Use Manufacturing Series or Project Series modules moderately |
| • | Have 20-60 concurrent users |
| • | Use Terminal Services |
| • | Use Report Writer, Crystal Reports |
| • | Perform some online analytical processing (OLAP) cube generation |
| • | Use an import routine/eConnect/Integration Manager |
| • | Process 1,000–4,000 transactions a day originating in Sales (Sales Order Processing and/or Receivables Management), Payables Management, or General Ledger |
| • | Have a dedicated server with SQL Server only |
Database | One of the following: | • | SQL Server 2005 SP2 Enterprise Edition or Standard Edition (32-bit and 64-bit) | | • | SQL Server 2000 SP4 Enterprise Edition or Standard Edition |
|
Operating system1 | One of the following: | • | Windows Server 2003 x64 Enterprise Edition SP2, R2 x64 Enterprise Editon SP2, x64 Standard Edition SP2, or R2 x64 Standard Edition SP2 | | • | Windows Server 2003 Enterprise Edition SP2, R2 Enterprise Edition SP2, Standard Edition SP2, or R2 Standard Edition SP2 |
|
Processor2 | One dual-core or two single-core |
Disk configuration3 | | • | RAID 1 for operating system and applications (two disks) | | • | RAID 1 for SQL database log files (two disks) | | • | RAID 5 (four disk minimum) or RAID 10 (eight disk minimum) for SQL data files | | • | RAID 1 for TempDB (two disks)—optional, but recommended | | • | RAID 0 for SQL backups (full disk volume and log) (two disks) |
|
RAM4 | 4 GB or more |
Network card5 | 100-MB Ethernet Full Duplex or 1-GB Ethernet |
1See the 64-bit support tables in #4 in the Additional notes section to verify that all products you're using are compatible.
2Ensure processors can be upgraded to four processors for Standard Edition or up to eight processors for Enterprise Edition.
3Additional disks will improve SQL Server performance. To process more than 4,000 transactions a day, you might need to increase the number of disks in your RAID 5 disk volume. Recommend use of Ultra SCSI 3 or Fiber Controller.
4If more than 2 GB of RAM is available, enable the 3 GB and/or the PAE switch in the boot.ini file if using Windows Server 2003 Enterprise Edition. Refer to Article Q283037 for more information.
5Ensure switch is capable of handling network traffic.
Customer profile 3
The following profile applies if you:
| • | Use Financial Series and Distribution Series modules extensively |
| • | Use Field Service Series, Manufacturing Series, and Project Series modules extensively |
| • | Have 60-100 concurrent users |
| • | Use Terminal Services |
| • | Use Report Writer, Crystal Reports |
| • | Use an import routine -- such as eConnect -- extensively |
| • | Process more than 4,000 transactions a day originating in Sales (Sales Order Processing and/or Receivables Management), Payables Management, or General Ledger |
| • | Perform OLAP cube generation to a different machine |
| • | Have a dedicated server with SQL Server only |
Database | One of the following: | • | SQL Server 2005 SP2 Enterprise Edition 32-bit and 64-bit, or Standard Edition 64-bit | | • | SQL Server 2000 SP4 Enterprise Edition |
|
Operating system1 | One of the following: | • | Windows Server 2003 x64 Enterprise Edition SP2, R2 x64 Enterprise Edition SP2, x64 Standard Edition SP2, or R2 x64 Standard Edition SP2 | | • | Windows Server 2003 Enterprise Edition SP2 or R2 Enterprise Edition SP2 |
|
Processor2 | Two dual-core or four single-core |
Disk configuration3 | | • | RAID 1 for operating system and applications (two disks) | | • | RAID 1 for SQL database log files (four disks) | | • | RAID 10 for data files (eight disk minimum) | | • | RAID 1 for TempDB (four disks) | | • | RAID 0 for SQL backups (full disk volume and log) (two disks) |
|
RAM4 | 8 GB or more |
Network card5 | 1-GB Ethernet |
1See the 64-bit support tables in #4 in the Additional notes section to verify that all products you're using are compatible.
2Verify processors can be upgraded to eight processors.
3Additional disks will improve SQL Server performance. To process more than 4,000 transactions a day, you might need to increase the number of disks in your RAID 5 or RAID 10 disk volume. Recommend use of Ultra SCSI 3 or Fiber Controller.
4Enable the 3 GB and/or the PAE switch in the boot.ini file if using Windows Server 2003 Enterprise Edition. (See Article Q283037).
5Ensure switch is capable of handling network traffic.
Terminal Services server requirements
Microsoft recommends using a dedicated Terminal Services server/Citrix server. There might be performance losses if SQL Server is running on the Terminal Services server/Citrix server. To help offset performance losses, it is highly recommended to have two separate servers: one server with Terminal Services and/or Citrix, and one server with SQL Server.
Operating system1 | Windows Server 2003 Enterprise Edition SP2, R2 Enterprise Edition SP2, Standard Edition SP2, or R2 Standard Edition SP2 |
Citrix (optional) 2 | Citrix Presentation Server 4.0 or 3.0 |
Processor3 | One dual-core or two single-core |
Disk configuration | RAID 1 for operating system and applications (two disks) |
RAM4 | 2 GB or more |
Network card5 | 100-MB Ethernet Full Duplex or 1-GB Ethernet |
Users6 | Based on 15-20 users for each Terminal Services server |
1See the 64-bit support tables in #4 in the Additional notes section to verify that all products you're using are compatible.
2If accessing Citrix, the hardware and software must be supported according to Citrix configuration requirements.
3Verify processors can be upgraded to four processors for Standard Edition or eight processors for Enterprise Edition.
4The amount of RAM needed depends on the number of concurrent users per Terminal Services server.
5Recommend no more then 25 users per 100 Base-T network card, unless a Fiber NIC is installed. If a Fiber NIC is installed, the SQL server also should have a Fiber NIC installed for optimal network performance. Ensure switch is capable of handling network traffic.
6Increased user count may require greater RAM and processor speed. Users Crystal Reports via Terminal Services may require increased hardware to improve performance.
Additional notes
1. | This document represents configurations tested by Microsoft and supported by Technical Support. Use of technologies not specified in this document is not recommended and will not be supported. Testing is ongoing, and as newer technologies become supported, this list will be updated. |
2. | If you will be using Workflow for Microsoft Dynamics GP 10.0, refer to the System requirements for Microsoft Dynamics GP 10.0 Web applications page for Microsoft Office SharePoint Server recommendations. |
3. | If you're running MSDE 2000 or SQL Server 2005 Express Edition on Windows XP SP2, or if you're running SQL Server on Windows Server 2003 SP1, refer to this KB article:
Some programs seem to stop working after you install Windows XP Service Pack 2. You might need to enable port 1433 for Transmission Control Protocol/Internet Protocol (TCP/IP) in Windows Firewall to ensure the incoming Open Database Connectivity (ODBC) requests are accepted. |
4. | Review the following tables to verify that the features and products you're using are supported with 64-bit operating systems. The following Release 10.0 products ARE supported on any 64-bit operating system. Microsoft Dynamics GP client or server installation note The Field Service e-mail feature will not work on a 64-bit server.
| Business Portal: Client accessing Business Portal note IIS Server must be on a 32-bit server.
| Human Resources and Payroll Suite | Integration Manager | Visual Studio Tools for Microsoft Dynamics GP SDK | Microsoft Dynamics GP SDK |
The following Release 10.0 products ARE NOT supported on any 64-bit operating system. Unless otherwise noted, testing for these products is scheduled for later this year. Business Portal: IIS Server note This will not be compatible with x64 operating systems until the next release of Microsoft Dynamics GP.
| Analysis Cubes for SQL Server 2005 (client and server) | Analysis Cubes for SQL Server 2000 (client and server) note No compatibility is planned.
| eConnect Runtime (including the SDK) | Office SharePoint Server Wizard | Personal Data Keeper | SQL Server Reporting Services Wizard | Web Services for Microsoft Dynamics GP Runtime (including the SDK and Management Tools) | Web Services for Microsoft Dynamics GP note This will not be compatible with x64 operating systems until the next release of Microsoft Dynamics GP.
| Microsoft Dexterity Development Tools |
|
Overview
System Requirements
