Microsoft supports the following hardware, server, and terminal server recommendations for Microsoft Dynamics GP 9.0 (formerly Microsoft Great Plains). The specific hardware that you'll need for your configurations will depend on which installations you're familiar with and which profile best fits your situation. To achieve individual performance expectations, you might need to increase these recommendations. On This Page Note Customers currently using Microsoft Dynamics GP 9.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 requirementsOperating system | One of the following: | • | Microsoft Windows XP Professional Service Pack (SP) 2 | | • | Microsoft Windows XP Tablet PC Edition1 | | • | Microsoft Windows 2000 Professional SP 4 | | • | Windows Vista Business Edition (refer to KB 929908 for prerequisites) | | • | Windows Vista Ultimate Edition (refer to KB 929908 for prerequisites) | | • | Windows Vista Enterprise Edition (refer to KB 929908 for prerequisites) | | • | Microsoft Windows XP x64 (refer to KB 918983 for prerequisites) |
| Processor | Pentium III 1.2 gigahertz (GHz) or equivalent | Disk space | 600 megabytes (MB) or more on the system root | RAM | 256 MB (512 recommended) | Network card | 100Base-T or 1000Base-T Ethernet |
1The Microsoft Windows XP Tablet PC Edition is only supported on a client connected to the local area network (LAN). The wireless components of Microsoft Windows XP Tablet PC Edition are not supported or recommended. Server recommendationsReview the following customer profiles to determine which profile best fits the user count, number of modules, and transaction volume for your environment. Customer profile 1 This profile applies if you: | • | Use only Financial Series module | | • | Have between 0-15 concurrent users for Microsoft SQL Server or 0-10 concurrent users for MSDE 2000 | | • | Use Report Writer in Visual FoxPro 80, Crystal Reports, or FRx | | • | Process fewer then 500 transactions a day | | • | Import very little data | | • | Have a dedicated server with Microsoft SQL Server only | | • | Recommend a dedicated server with MSDE 2000 only |
Database requirements | | • | Microsoft SQL Server 2000 Standard Edition Service Pack (SP) 4 | | • | Microsoft SQL Server 2000 Workgroup Edition SP 4 | | • | MSDE 2000 SP 41 | | • | Microsoft SQL Server 2005 Standard Edition 32-bit | | • | Microsoft SQL Server 2005 Workgroup Edition | | • | Microsoft SQL Server 2005 Express Edition | | • | Microsoft SQL Server 2005 Standard Edition 32-bit SP 1 | | • | Microsoft SQL Server 2005 Workgroup Edition SP 1 | | • | Microsoft SQL Server 2005 Express Edition SP 1 |
| Operating System | One of the following: | • | Microsoft Windows 2000 Server Service Pack (SP) 4 | | • | Microsoft Windows Server 2003 Standard Edition SP 1 | | • | Microsoft Windows 2000 Small Business Server SP 4 | | • | Microsoft Windows Small Business Server 2003 Premium Edition SP 1 | | • | Microsoft Windows Small Business Server 2003 Standard Edition SP 1 (MSDE only) | | • | Microsoft Windows Server 2003 R2 Standard Edition | | • | Microsoft Windows Server 2003 x64 (refer to KB 918983 for prerequisites) |
| Processors2 | Dual Pentium IV 2.4 GHz (or equivalent) | Disk configuration | Minimum for Microsoft SQL Server only: RAID 5 for operating system, applications, and SQL database log and data files More available disks will improve Microsoft SQL Server performance Recommend using a dual-channel fast and wide SCSI-2 controller Recommended for Microsoft SQL Server only: RAID 1 for operating system and applications RAID 5 for SQL database log and data files RAID configurations are not required for an MSDE 2000 installation; however, it can be implemented | RAM | 1 gigabyte (GB) or greater | Network card | 32-bit, 10/100 megabyte (MB) Ethernet Full Duplex |
1MSDE 2000 can be installed on a non-server operating system; however, it is recommended to install on a server operating system. The only non-server operating systems supported are Microsoft Windows XP Professional SP 2 and Microsoft Windows 2000 Professional SP 4. (See #5 in the Notes section.) 2Make sure processors can be upgraded. Customer profile 2 This profile applies if you: | • | Use Financial Series modules | | • | Use Distribution Series modules moderately | | • | Use Field Service Series modules | | • | Use Manufacturing Series modules moderately | | • | Have 10–30 concurrent users | | • | Use Terminal Server | | • | Use Report Writer, Crystal Reports, or FRx | | • | Perform some online analytical processing (OLAP) cube generation | | • | Use an import routine/eConnect/Integration Manager | | • | Process 500–2,000 transactions a day (originating in Sales (SOP and/or RM), Payables or General Ledger) | | • | Have a dedicated server with Microsoft SQL Server only |
Database requirements | | • | Microsoft SQL Server 2000 Enterprise Edition SP 4 | | • | Microsoft SQL Server 2000 Standard Edition SP 4 | | • | Microsoft SQL Server 2000 Workgroup Edition SP 4 | | • | Microsoft SQL Server 2000 (64-bit) SP 4 | | • | Microsoft SQL Server 2005 Enterprise Edition 32-bit and 64-bit | | • | Microsoft SQL Server 2005 Standard Edition 32-bit and 64-bit | | • | Microsoft SQL Server 2005 Workgroup Edition | | • | Microsoft SQL Server 2005 Enterprise Edition 32-bit SP 1 and 64-bit SP 1 | | • | Microsoft SQL Server 2005 Standard Edition 32-bit SP 1 and 64-bit SP 1 | | • | Microsoft SQL Server 2005 Workgroup Edition SP 1 |
| Operating System | One of the following: | • | Microsoft Windows 2000 Server Service Pack (SP) 4 | | • | Microsoft Windows 2000 Advanced Server SP 4 | | • | Microsoft Windows Server 2003 Standard Edition SP 1 | | • | Microsoft Windows Server 2003 Enterprise Edition SP 1 | | • | Microsoft Windows Server 2003 R2 Standard Edition | | • | Microsoft Windows Server 2003 R2 Enterprise Edition | | • | Microsoft Windows Server 2003 x64 (refer to KB 918983 for prerequisites) |
| Processors1 | Dual Xeon 2.4 gigahertz (GHz) or equivalent | Disk configuration2 | RAID 1 for operating system and applications (2 disks) RAID 1 for SQL database log files (2 disks) RAID 5 (4 disk minimum) or RAID 10 (8 disk minimum) for SQL data files RAID 1 for TempDB (2 disks)—optional, but recommended RAID 0 for SQL Server backups (full and log) (2 disks) | RAM3 | 2 GB or more | Network card4 | Dual 100-bit 10/100 MB Ethernet or Fiber PCI NIC |
1Processors must be able to upgrade to Quad processors. 2Having more disks available will improve Microsoft SQL Server performance. To attain 2,000 transactions a day, you might need to increase the number of disks in your RAID 5 disk volume. Recommend separate disks for database backups and transaction log dumps. Recommend use of Ultra SCSI 3 or Fiber Controller. 3If more than 2 gigabytes (GB) of RAM is available, enable the 3 GB or the PAE switch in the boot.ini file if any of the following have been installed: Windows 2000 Advanced Server, Windows Server 2003 Standard Edition or Windows Server 2003 Enterprise Edition and SQL Server Enterprise Edition. Refer to Article Q283037 for more information. Be sure to expand to 4 GB if necessary. 4Ensure switch is capable of handling network traffic. Customer profile 3 This profile applies if you: | • | Use Financials Series and Distribution Series modules extensively | | • | Use Field Service Series and Manufacturing Series modules extensively | | • | Have 25 or more concurrent users | | • | Use Terminal Server running Citrix MetaFrame | | • | Use Report Writer, Crystal Reports or FRx extensively | | • | Use an import routine extensively—such as eConnect | | • | Process 2,000-5,000 transactions a day (originating in Sales (SOP and/or RM), Payables or General Ledger) | | • | Perform OLAP cube generation to a different machine | | • | Have a dedicated server with Microsoft SQL Server only |
Database requirements | | • | Microsoft SQL Server 2000 Enterprise Edition SP 4 | | • | Microsoft SQL Server 2000 (64-bit) SP 4 | | • | Microsoft SQL Server 2005 Enterprise Edition 32-bit and 64-bit | | • | Microsoft SQL Server 2005 Enterprise Edition 32-bit SP 1 and 64-bit SP 1 |
| Operating System | One of the following: | • | Microsoft Windows 2000 Advanced Server Service Pack (SP) 4 | | • | Microsoft Windows Server 2003 Standard Edition SP 1 | | • | Microsoft Windows Server 2003 Enterprise Edition SP 1 | | • | Microsoft Windows Server 2003 R2 Enterprise Edition | | • | Microsoft Windows Server 2003 x64 (refer to KB 918983 for prerequisites) |
| Processors1 | Quad Xeon 2.4 gigahertz (GHz) or equivalent | Disk configuration2 | RAID 1 for operating system and applications (2 disks) RAID 1 for SQL database log files (4 disks) RAID 1 for TempDB (4 disks) RAID 0 for SQL backups (full and log) (2 disks) RAID 10 for data files (8 disks or more) | RAM3 | 4 GB or more | Network card4 | Single 1000Base-T Ethernet or Fiber PCI NIC |
1Processors must be able to be upgraded to 8 GB processors or higher. 2Having more disks available will improve Microsoft SQL Server performance. To attain 5,000 transactions a day, you might need to increase the number of disks in your RAID 5 or RAID 10 disk volume. Recommend separate disks for database backups and transaction log dumps. 3Enable the 3 gigabytes (GB) or the PAE switch in the boot.ini if any of the following have been installed: Windows 2000 Advanced Server, Windows Server 2003 Standard Edition or Windows Server 2003 Enterprise Edition and SQL Server Enterprise Edition. (See Article Q283037). Be sure to expand to 8 GB if necessary. 4Ensure switch is capable of handling network traffic. Terminal server requirementsMicrosoft recommends using a dedicated Terminal Server/Citrix Server when running Microsoft Dynamics GP 9.0. There might be performance losses if Microsoft SQL Server is running on the Terminal Server/Citrix Server. To avoid performance losses, it is highly recommended to have two separate servers: one server with Terminal Server and/or Citrix, and one server with Microsoft SQL Server. Database requirements | Required: | • | Microsoft SQL Server 2000 Enterprise Edition SP 4 | | • | Microsoft SQL Server 2000 Standard Edition SP 4 | | • | Microsoft SQL Server 2000 Workgroup Edition SP 4 | | • | Microsoft SQL Server 2000 (64-bit) SP 4 | | • | MSDE 2000 SP 4 | | • | Microsoft SQL Server 2005 Enterprise Edition 32-bit and 64-bit | | • | Microsoft SQL Server 2005 Standard Edition 32-bit and 64-bit | | • | Microsoft SQL Server 2005 Workgroup Edition | | • | Microsoft SQL Server 2005 Express Edition |
Recommended1: | • | Citrix MetaFrame XP SP 2 | | • | Citrix Presentation Server 3.0 | | • | Citrix Presentation Server 4.0 |
| Operating System | One of the following: | • | Microsoft Windows 2000 Server Service Pack (SP) 4 | | • | Microsoft Windows 2000 Advanced Server SP 4, Microsoft Windows Server 2003 Standard Edition SP 1 | | • | Microsoft Windows Server 2003 Enterprise Edition SP 1 | | • | Microsoft Windows Server 2003 R2 Standard Edition | | • | Microsoft Windows Server 2003 R2 Enterprise Edition | | • | Microsoft Windows Server 2003 x64 (refer to KB 918983 for prerequisites) |
| Processors2 | Dual Pentium IV 2.4 gigahertz (GHz) or equivalent | Disk configuration | RAID 1 for operating system and applications (2 disks) | RAM3 | 1 GB or more | Network card4 | Single/Dual 100Base-T or 1000Base-T Ethernet or Single Fiber PCI NIC | Users5 | Based on 15-20 users for each Terminal Server |
1Recommendation is based on 15-20 users for each Terminal Server. 2Processors must be able to be upgraded to 8-gigabyte (GB) processors or higher. 3The amount of RAM needed depends on the number of concurrent users per Terminal Server. 4Recommend no more then 25 users per 100Base-T network card, unless a Fiber NIC is installed. If a Fiber NIC is installed, the SQL Server should also have a Fiber NIC installed for optimal network performance. Ensure switch is capable of handling network traffic. 5Increased user count might require greater RAM and processor speed. Users of FRx or Crystal Reports via Terminal Services might require increased hardware to boost performance. Notes1. | 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, they will be added to this document. | 2. | Microsoft Office 2000, Office XP, Office 2003 and the 2007 Microsoft Office system have been tested and are supported with Microsoft Dynamics GP 9.0. The Office XP Web Components need to be installed if you are using Office XP or Office 2000 and the Office 2003 Web Components need to be installed if you are using Office 2003 or the 2007 Microsoft Office system. You can find the downloads below: Microsoft Office XP and Office 2000 Microsoft Office 2003 and the 2007 Microsoft Office system Microsoft Dynamics GP is supported on a 64-bit operating system, however, please refer to KB 918983 for prerequisites for installing the Microsoft Dynamics GP client application on a 64-bit machine. Analysis Cubes for Microsoft Office Excel is not compatible with 64-bit systems. | 3. | The Microsoft SQL Server databases can be housed on a 64-bit operating system. | 4. | Intel Pentium processors are used in platform testing; however, the compatibility is based on the speed of the processor, not on the type of processor. | 5. | If running MSDE 2000 on Windows XP with SP 2, or on Microsoft SQL Server on Windows Server 2003 with SP 1, refer to the following knowledge-base article: http://support.microsoft.com/default.aspx?scid=kb;en-us;842242&Product=winxp. You might need to enable port 1433 for Transmission Control Protocol/Internet Protocol (TCP/IP) in the Windows firewall to ensure the incoming Open Database Connectivity (ODBC) requests will be accepted. | 6. | Adobe 6.0 and Adobe 7.0 have been tested and are supported with Microsoft Dynamics GP 9.0. | 7. | Microsoft Dynamics GP is supported on a Windows Vista operating system, however, please refer to KB 929908 for prerequisites for installing the Microsoft Dynamics GP client application on a Windows Vista machine. | 8. | Microsoft Dynamics GP has not been tested with VMWare, Virtual Server, or any virtual machine technology; therefore, Microsoft Dynamics GP is not supported in any virtual machine environment. | 9. | Microsoft Dynamics GP must be installed in a domain environment. If a domain does not exist, products such as Business Portal and Analysis Cubes for Microsoft Office Excel may not function properly. |
| |
