Microsoft Dynamics GP server installation

Installing Release 10.0 on the server

Installation overview
In a multiuser local area network environment, Microsoft Dynamics GP applications are typically installed on a server, and then on each client. When you install Microsoft Dynamics GP on the server, both server and client components are installed on the server. Each client will have access to data stored on the server. You must install your company database on the server first. Then, from any client, you’ll install client components using the Microsoft Dynamics GP CD or using a client installation package.
Installing Microsoft Dynamics GP (server and first client)
Before beginning the installation, be sure you’ve completed the installation preparation steps listed in Part 1, Preparation, and that no other applications are running.
To install Microsoft Dynamics GP (server and first client):
1. Be sure that you’re logged in to Windows as a user with system administrator privileges.
2. Insert Release 10.0 CD 1 in the CD-ROM drive of your server computer. The main Microsoft Dynamics GP installation window should appear. If the window does not appear automatically, browse the CD and double-click the Setup.exe file.
3. Click Microsoft Dynamics GP.
The installation program verifies that your system has the minimum operating system required to run Microsoft Dynamics GP. If your system does not meet requirements, the installation will not continue.
4. If you are installing Microsoft Dynamics GP on a computer with an existing instance of Microsoft Dynamics GP Release 10.0, select the Create new instance option, enter a name for the new instance, and then click Next.
5. In the Country/Region Selection window, select the primary country or region where you do business. Your selection affects which features are available to install. Some features are available only in selected countries or regions. Click Next.
6. Follow the instructions in the window to accept the software license agreement.
To install Microsoft Dynamics GP, you must accept this agreement and click Next.

7. In the Select Features window, select the features to install.

When you click a button for a feature, a pop-up menu of options appears. Refer to the table for more information about each option.
8. Specify the folder where you want the Microsoft Dynamics GP files installed. The default folder is C:\Program Files\Microsoft Dynamics\GP. To select a different folder, click Browse.
After you have specified the installation folder, click Next.
9. To set up an ODBC data source, enter the name you assigned to the SQL Server when you installed Microsoft SQL Server. A data source name called Dynamics GP also is created using SQL Native Client. If you don’t want to set up an ODBC data source, mark the Do not create a data source option. Click Next.
10. In the Install Program window, click Install.
11. The Installation Progress window appears, where you can view the status of the installation.
12. In the Installation Complete window, click Exit.
13. Before you start Microsoft Dynamics GP Utilities, check for and install current Microsoft Dynamics GP service pack for Release 10.0. See CustomerSource (https://mbs.microsoft.com/customersource) for the latest service pack information.

Account framework

Understanding the account framework
The framework you’ll enter includes maximums for the account length, the number of account segments, and the length of each segment. These maximums will be used for the account format in all companies you’re planning to set up. You’ll enter the specific account format for each company when you access Microsoft Dynamics GP and set up the company.
Maximums you enter for account framework during installation will apply to additional companies you set up later. For example, you could enter the account framework maximums shown in the following table during the installation process.

With these maximums for the account framework defined during installation, you wouldn’t be able to set up the following account format for a company.

Although the maximum account length and number of segments is within the limit, this account format is invalid because the length of the first segment—8—exceeds the segment maximum that was defined during installation.

Planning your account framework
When planning an account framework, think about the account format you’ve used with your previous accounting system and consider future expansions and the account format for additional companies you may add to your system later. Plan the maximum number of segments you’ll use in any company, and the maximum length of each segment.
It’s important to consider what your current and future needs are for the framework; after you’ve entered the framework, it’s unlikely that you’ll be able to change it. If you find that you need to change your account framework, contact your reseller or Microsoft Dynamics GP Technical Support.
To use one of the default charts of accounts provided with Microsoft Dynamics GP or to complete the orientation training using the sample company, set up the account framework with maximums that are at least the size listed below. To preview the default charts of accounts for various business and industry types, review the Default Charts of Accounts for Microsoft Dynamics GP article (http://go.microsoft.com/fwlink/?LinkId=89042).

SQL Server Agent

SQL Server Agent
When you install Microsoft Dynamics GP on the server, an automated database
maintenance job is created. SQL Server Agent is used to run automated jobs.
Be sure that the SQL Server Agent service is set up to start automatically with the operating system if you are using Microsoft SQL Server. In SQL Server Service Manager, select SQL Server Agent from the list of services and mark the Auto-start service when OS starts option.
Jobs are customizable, and you can select how frequently they should be completed.
You may want certain jobs to run every half hour, while others should run once at night. For more information on scheduling jobs, refer to Microsoft SQL Server Books Online.
Microsoft SQL Server 2005 Express doesn’t include SQL Server Agent. Refer to
Support Hot Topic on CustomerSource https://mbs.microsoft.com/ customersource for more information about scheduling a backup.
Enabling Delete PJournal job The Delete PJournal job is created during the installation of Microsoft Dynamics GP.
By enabling the Delete PJournal job, the speed of the posting process is increased.
To enable Delete PJournal job using Enterprise Manager:
1. Open SQL Server Enterprise Manager.
(Start >> Programs >> Microsoft SQL Server >> Enterprise Manager)
2. Expand Microsoft SQL Server, expand SQL Server Group, and expand the instance of SQL Server used for GP.
3. Expand Management, expand SQL Server Agent, and click Jobs.
4. Right-click on Remove Posted PJournals for your company database and click
Properties to open the Properties window.
5. Unmark and mark the Enable option.
6. Click Apply and then click OK

To enable Delete PJournal job using SQL Server
Management Studio:
1. Open SQL Server Management Studio.
(Start >> Programs >> Microsoft SQL Server 2005 >> SQL Server Management
Studio)
2. Log in to Microsoft SQL Server 2005.
3. Expand SQL Server Agent, and click Jobs.
4. Right-click on Remove Posted PJournals for your company database and click
Properties to open the Properties window.
5. Unmark and mark the Enable option.
6. Click Apply and then click OK.

Installing Microsoft SQL Server 2005 Express Edition

Installing Microsoft SQL Server 2005 Express Edition
Microsoft SQL Server 2005 Express Edition has a maximum database size of 4 GB. You can download Microsoft SQL Server 2005 Express from www.microsoft.com.
The version of Microsoft Dynamics GP that runs on Microsoft SQL Server 2005
Express is limited to 10 users.
Microsoft SQL Server 2005 Express doesn’t include SQL administrative tools. You can download Microsoft SQL Server Management Studio Express and SQL Server 2005 Books Online for SQL Server Express from www.microsoft.com.
Use the information in this section to install Microsoft SQL Server 2005 Express on your computer.
To install Microsoft SQL Sever 2005 Express Edition:
1. Insert the SQL Server 2005 DVD. The main SQL Server installation screen should appear. If you do not see this screen, browse the DVD and double-click the Splash.hta file.
2. Click Run in the SQL Server Installation Wizard.
3. Mark the option to accept the terms of the End-User License Agreement and then click Next.
4. In the Installing Prerequisites window, click Install to install the software components that are required for Microsoft SQL Server 2005 Express. After the components are installed, click Next.
5. In the Welcome to the Microsoft SQL Server Installation Wizard window, click Next.
6. Your computer is scanned for conditions that may stop installation. To proceed with the installation, click Next in the System Configuration Check window. For more information about the items that are checked, click Help.
7. Enter your name and company in the Registration Information window, and click Next.
8. In the Feature Selection window, select the features for your installation and specify the location to install Microsoft SQL Server Express Edition. Click Next.
9. In the Authentication Mode window, select Mixed Mode as the authentication mode. Mixed Mode is required by Microsoft Dynamics GP.
With Mixed Mode, users can connect using Windows Authentication or SQL Server Authentication. You must enter and confirm the system administrator password when you select Mixed Mode.
10. Specify whether or not to allow error and usage reporting in the Error and Usage Report Setting window. Click Next.

11. In the Ready to Install window, review the list of components that will be installed and click Install.
12. The Setup Progress window appears, allowing you to view the status of the installation. Click Next after the installation has been completed.
13. In the Completing the Microsoft SQL Server Installation Wizard window, click Finish to exit the installation wizard.
14. Restart the computer if you are instructed to do so.

To install Microsoft SQL Server 2005 (cont)

13. In the Collation Settings window, select Binary or Dictionary Order, Case- Insensitive as the sorting option and click Next. See Selecting a SQL Server collation on page 15 for more information about collation options.
You should check the compatibility of all the products you have that will use SQL Server before deciding on the collation option.
Binary To use Binary sorting, use the Collation designator option and sort order and make the following selections in the Collation Settings window.

Dictionary Order, Case-Insensitive To use Dictionary Order, Case-Insensitive sorting, choose SQL Collations and make the following selections in the ollation Settings window.

14. In the Error and Usage Report Settings window, select to allow error and usage reporting. Click Next.
15. In the Ready to Install window, review the list of components that will be installed and click Install.
16. The Setup Progress window appears, allowing you to view the status of the installation. Click Next after the installation is completed.

17. In the Completing the Microsoft SQL Server Installation Wizard window, click Finish to exit the installation wizard.
18. Restart the computer if you are instructed to do so.

To install Microsoft SQL Server 2005:

1. Insert the SQL Server 2005 DVD. The main SQL Server installation screenshould appear. If you do not see this screen, browse the DVD and double-clickthe Splash.hta file.
2. Click Run in the SQL Server Installation Wizard.
3. Mark the option to accept the terms of the End-User License Agreement and then click Next.

4. In the Installing Prerequisites window, click Install to install the software
components that are required for SQL Server 2005. After the components are
installed, click Next.
5. In the Welcome to the Microsoft SQL Server Installation Wizard window, click Next.
6. Your computer is scanned for conditions that may stop installation. To proceed with the installation, click Next in the System Configuration Check window. For more information about the items that are checked, click Help.
7. Enter your name and company in the Registration Information window, and
click Next.
8. In the Components to Install window, select the components for your SQL
server installation and click Next.

To install individual components, click Advanced.
If you are installing a failover cluster, see How to: Create a New SQL Server 2005 Failover Cluster (Setup) in the MSDN Online Library (http://msdn2.microsoft.com/ms179530.aspx).
9. The Feature Selection window opens if you selected to install individual
components. Select the program features you want to use and specify the location to install SQL Server 2005. Click Next.
10. In the Instance Name window, select a default or named instance for your installation.
• To install a new default instance (the primary instance on the computer), click Default instance and click Next. There can be only one default instance.
• To install a new named instance, click Named instance and then enter a unique instance name. Click Next.
• If a default or named instance is already installed, select the existing instance for your installation and click Next. The instance upgrades and you will have the option to install additional components.
For information about using instances of SQL Server, see your SQL Server documentation. We recommend that you have a dedicated server.
11. In the Services Accounts window, specify the user name, password and domain name for the service accounts. We recommend that you use the same account for each service and automatically start services. Click Next.
12. In the Authentication Mode window, select Mixed Mode as the authentication mode. Mixed Mode is required by Microsoft Dynamics GP.
With Mixed Mode, users can connect using Windows Authentication or SQL Server Authentication. You must enter and confirm the system administrator password when you select Mixed Mode.

Microsoft SQL Server configuration

Microsoft SQL Server configuration

This chapter guides you through the Microsoft SQL Server 2005 and the Microsoft SQL Server 2005 Express installation and setup process for Microsoft Dynamics GP. It’s important that you install and set up Microsoft SQL Server according to these instructions. If you’ve already installed and set up SQL Server using different options, you may have to change those options. Changing options after they’ve been set sometimes involves reinstalling SQL Server.
• SAN and NAS disk support
• Selecting a SQL Server collation
• Understanding sorting options
• Installing Microsoft SQL Server 2005
• Installing Microsoft SQL Server 2005 Express Edition
• SQL Server Agent
• Enabling Delete PJournal job
SAN and NAS disk support
Because Microsoft Dynamics GP relies on SQL Server to maintain databases and make databases available, there are guidelines you must follow when configuring SQL Server disk support.
We recommend that you use a Storage Area Network (SAN) or locally attached disk to store your Microsoft SQL Server database files because this configuration optimizes SQL Server performance. By default, use of network database files stored on a networked server or Network Attached Storage (NAS) is not enabled for SQL Server. However, you can configure SQL Server to store a database on a networked server or NAS storage server. Servers used for this purpose must meet SQL Server requirements for data write ordering and write-through guarantees.
If you are using Microsoft SQL Server Express Edition, SAN and NAS disk support isn’t typically used.
For more information, see Microsoft Knowledge Base article Q304261 (go to support.microsoft.com and search for the article number) or contact the SQL Server Support Team.
Selecting a SQL Server collation
A SQL Server collation—a set of rules that determines how character data is sorted and compared—includes character set, sort order, and locale-specific settings. See your SQL Server 2000 or 2005 documentation for more information about collation settings.
The SQL Server collation you select determines how information is presented in
response to SQL queries and affects the performance of the system.
The code page for character data is defined by the Windows locale selected when the operating system was installed. The code page contains the valid set of
characters in your SQL Server database. A character set consists of 256 uppercase and lowercase letters, numbers, and symbols. The first 128 characters are the same for all character sets. The supported character set in the United States is the 1252/ ISO character set.
It is important to select the correct collation for Microsoft Dynamics GP when
you’re installing SQL Server. Using SQL Server collations that include Binary (sort order 50) or Dictionary Order, Case-Insensitive (sort order 52) sorting is required for Microsoft Dynamics GP. To change these settings at a later time, you must reinstall SQL Server and Microsoft Dynamics GP.
You should check the compatibility of all the products you have that will use SQL Server before deciding on the collation option.
Understanding sorting options
Using SQL Server collations that include Binary (sort order 50) or Dictionary Order, Case-Insensitive (sort order 52) sorting is required.
Binary sort order assigns characters numeric values of 0 through 255. Dictionary Order, Case-Insensitive (DOCI) sort order makes no distinction between uppercase and lowercase characters. DOCI is the most common sort order.
The following table shows the differences between Dictionary Order, Case-
Insensitive and Binary.
Installing Microsoft SQL Server 2005
We recommend that you follow the instructions in this section if you have not yet installed Microsoft SQL Server 2005. For information about upgrading SQL Server, see the SQL Server installation documentation. (In the window that appears when you insert the SQL Server DVD, select Browse Setup/Upgrade Help.)
With SQL Server 2005, you can have multiple instances of SQL Server on the same physical server. We recommend that you have a dedicated a server. See your SQL Server 2005 documentation for more information about multiple instances.

Network configuration

Network configuration
This post contains information about network configuration that must be in
place before installing Microsoft Dynamics GP, and includes the following sections:
• Domain
• Network protocol tuning
• TCP/IP
Domain
To use Microsoft Dynamics GP, your Web server, back office server, Terminal Services server (if applicable), and client workstations must belong to a domain. A domain is a group of computers that are part of a network and share a common directory database. A domain is administered as a unit with common rules and procedures. Each domain has a unique name.
Network protocol tuning
To optimize your network for Microsoft SQL Server and Microsoft Dynamics GP, refer to the following guidelines.
• Limit the network to one protocol. (TCP/IP is required.)
• Remove unused network protocols. On Windows 2003 Server, choose Start >>
Settings >> Control Panel >> Network Connections; right-click on your local
area connection and choose Properties.
• Use 100 MB Full Duplex or 1 GB Ethernet for optimal performance. For more
information about system requirements, see http://go.microsoft.com/fwlink/

• Use switches rather than hubs, if optimal performance is required.
TCP/IP
Transport Control Protocol/Internet Protocol (TCP/IP) is required for Microsoft
Dynamics GP. If you’re using TCP/IP, review the information in this section to be sure that the network is set up properly. Then use your networking protocol documentation to install and test the protocol on all clients and servers before you install Microsoft Dynamics GP.
IP addresses

Each computer that you use with Microsoft Dynamics GP must have a unique IP number (Internet Protocol address) associated with it. For more information about IP addresses, consult your network administrator or refer to your networking protocol software documentation.
TCP/IP name resolution
You should use some type of name resolution in your network, so that each computer is identified by a unique host name. Name resolution is a method of identifying each computer and can be accomplished by having a specific server act as a domain name server or putting a hosts file on each client and server.
For more information about name resolution using either a domain name server or hosts files, consult your network administrator or refer to your networking protocol software documentation.
Testing TCP/IP connectivity
To test connectivity between clients and servers, use an application distributed with most TCP/IP packages called ping. The ping application will attempt to send a network message or set of messages to a designated computer and inform you whether the message arrived at that computer. Be sure you ping the host name and the ID address of every computer in your system before installing Microsoft Dynamics GP.

Microsoft Dynamics™ GP10 Requirements

System requirements
The following components must be installed before you can install Microsoft
Dynamics GP.
• Windows Installer 3.1
• Microsoft .NET Framework 2.0
• Microsoft SQL Server Native Client
• Dexterity® Shared Components
• Microsoft Application Error Reporting 11.0
If one of these components isn’t installed on your computer when you attempt to install Microsoft Dynamics GP using the CD, the Component Installation window opens. This window shows whether or not the component is installed. Click Install to install the missing component or components. After all the components are installed, the installation of Microsoft Dynamics GP continues.

Home page prerequisites
The Microsoft Office Outlook® area of your home page displays appointments and the number of unread e-mail messages that you have. To use the Microsoft Office Outlook area, you must have Microsoft Outlook 2003, Microsoft Outlook 2007, or Microsoft Outlook XP installed. Outlook can be installed as a single product or as part of a Microsoft Office 2003 edition, Microsoft Office 2003 edition, or a Microsoft Office XP edition.
The metrics area of your home page displays graphical representations of Microsoft Dynamics GP data. For the metrics to be displayed on your home page, you must have Office Web Components installed on your computer. Office Web Components can be installed as a single product or as part of a Microsoft Office 2003 edition or a Microsoft Office XP edition. If you are using Microsoft Office 2007, you must use the Office Web Components for Microsoft Office 2003.

Supported system requirements

For current system requirements for Microsoft Dynamics GP, see
http://%20go.microsoft.com/fwlink/?LinkId=82118 The system requirements include supported databases and operating systems, hardware recommendations, client requirements, and Terminal Server requirements.
Recommended system requirements depend on the number of users and transactions. If there will be many users performing concurrent tasks, such as depreciation, posting, or heavy reporting, enhancing your hardware and system software improves performance.

About remote access
You can use Windows Server 2003 Terminal Services with Citrix Presentation Server 3.0 or Citrix Presentation Server 4.0 (optional) with most database configurations to provide remote access to Microsoft Dynamics GP in a Wide Area Network (WAN) environment.
A Windows Server 2003 Terminal Server computer with Citrix Presentation Server is supported only as a client.
For more information about system requirements see http://go.microsoft.com/fwlink/?LinkId=82118. You also should refer to the documentation provided by Citrix for more information.