Gp Installation Presentation

  • 1,384 views
Uploaded on

Overview on Microsoft Dynamics GP 10 Installation and Configuration

Overview on Microsoft Dynamics GP 10 Installation and Configuration

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,384
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
36
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Installation Configuration By : Donald Dauphin Date: 11/17/2008
  • 2. Overview
    • GP 10 overview and key features
    • GP System Requirements & SQL Server Installation
    • Data Server Installation & Utilities
    • Client computers, components installation & Maintenance
    • System Manager (Security)
    • Post Installation Administration
    • Performance Optimization & Troubleshooting
    • Process Server
    • Reporting
    • Q & A
  • 3. Overview and key features
    • Microsoft Dynamics GP is a business management solution that provides growing and midsize organizations with complete and scalable financial and operational functionality, such as:
    • Advanced consolidation
    • Robust business intelligence
    • Rich reporting
    • Forecasting
    • Budgeting.
    • Etc..
    • Because this functionality is available right out-of-the-box, it is possible to integrate and automate HH* financial and operational processes more rapidly. With Microsoft Dynamics GP, HH can get up and running quickly, maximizing the productivity of staff members and increasing confidence that our solution will adapt to the changing needs of our business.
    • But, how do we get GP installed and configured @ HH?
    *HH stands for Hooper Holmes
  • 4. EASY!!!
    • What do we need?
    • Determine Installation type
    • Database Requirements
    • Server Requirements
    • Clients/Terminal Server Requirements
  • 5. GP System Requirements & SQL Server Installation
    • Client hardware Installation
    • Server hardware Installation
      • Customer 1 [ 0 – 15 users]
      • Customer 2 [10 – 30 users]
      • Customer 3 [25 or More]
    • Terminal Server Installation
    • Network Requirements
    • Database Installation
      • Service Account
      • Authentication Mode
      • Collation
      • Network Libraries (Protocols)
    • Post DB Installation
      • Backup DB (Master/Log)
    Microsoft Dynamics GP provides several hardware recommendations to meet the needs of a company. Software requirements must be met or Microsoft Dynamics GP will not install. Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Express can be used together with Microsoft Dynamics GP. This presentation discussed the prerequisites and hardware recommendations for hardware, server and SQL Server Installation and outlined Post-installation recommendations
  • 6. Client Hardware Installation               Vista Business               Vista Ultimate 8.0   2007         Vista Enterprise 7.0 7.0 2003         XP Pro >= SP2 6.0 6.0 XP 100 MB Full duplex 512MB 800 MB >= Intel P 4 2.4GHZ XP x64 Bit Pro Adobe IE MS Office Network Card Memory HD Space Processor OS
  • 7. Server Hardware Installation
    • Specs in a server environment will vary depending on the needs and requirements of the organization. To define those needs, we must determine the following:
      • Number of concurrent transactions
      • Number of transaction per day
      • Database is on dedicated Server
      • Heavy reporting using CR, Frx, Report Writer
      • Using Terminal Server
      • Etc…
    *See attach Server Requirement Sheet
  • 8. Terminal Server Installation                                   Server 2003 R2 x64 Ent           Server 2003 R2 x64 Standard         Presentation 4.0 Server 2003 x64 Ent 15 to 20 100 MB Full duplex >= 2 GB >= Dual Intel Xeon 3000 2.4 Ghz Presentation 3.0 Server 2003 x64 Standard Users Network Card Memory Processor Citrix OS
  • 9. Network Requirements
    • Dynamics GP Requires TCP/IP Protocols
    • Each computer used with GP must have a unique IP associated with it
    • Use Host name resolution on the network
    • All components (PC, Server, MTS) must belong to a domain.
  • 10. Database Installation
    • Set username/password for service account
    • Select ‘Mixed Mode’ as authentication Type
    • Set Collation to ‘Binary or Dictionary order, case insensitive
    *Collation = feature in SQL that determines how information is returned by SQL Queries
  • 11. Data Server Installation & Utilities
    • Microsoft Dynamics GP uses ODBC to communicate between the client workstation and the SQL Server.
    • The ODBC data source can be automatically created when Microsoft Dynamics GP is installed.
    • Microsoft Dynamics GP Utilities is used to complete the initialization and configuration of the databases once the software installation is complete. This includes creating and initializing the DYNAMICS system database, installing the sample database, and creating additional company databases.
    • A Basic or Advanced installation can be performed in Microsoft Dynamics GP Utilities. The Basic installation uses default settings to configure the application and the Advanced installation allows you to customize the settings.
    • The account framework for Microsoft Dynamics GP can contain up to 66 characters and 10 segments, with a maximum storage size of 82 bytes. The account framework is not easily changed and must accommodate the account formats of every existing company in Microsoft Dynamics GP and account for future growth.
    • If errors occur during the initialization process in Microsoft Dynamics GP Utilities, there are several things to check including:
      • disk space
      • file paths and
      • whether the databases are created before recreating the database initialization
  • 12. Client computers, components installation & Maintenance
    • Installing client workstations is similar to a server installation. After a client workstation is installed, Microsoft Dynamics GP Utilities must be used to synchronize the client application dictionary to the server account framework.
    • A client installation package can help to standardize and speed deployment of Microsoft Dynamics GP. A package can be deployed to users using a variety of methods.
    • Microsoft Dynamics GP service packs are typically released on a six month cycle and can be found on Customersource and Partnersource.
    • Automatic Updates allow an administrator or Partner to deploy updates to client workstations with minimal user involvement. Updates must be applied to the server first. Automatic Updates can include installation packages, which contain service packs or other updates, and customizations created by an ISV, Partner, or administrator.
    • Important files installed with Microsoft Dynamics GP include the Dynamics.dic, Dex.ini, Dynamics.set, Dynamics.exe, Dynutils.set, Dynutils.exe, and reports and forms dictionaries. Reports and forms dictionaries can be stored locally to achieve better performance.
    • Microsoft Dynamics GP uses identity columns called DEX_ROW_IDs for row level locking, and to uniquely identify records in a particular table.
    • Stored Procedures help to improve Microsoft Dynamics GP performance by encapsulating complex business logic, and knowledge of how stored procedures are used by Microsoft Dynamics GP can be useful when troubleshooting errors and issues.
  • 13. System Manager
    • Entering system password and registration information
    • Reviewing the Microsoft Dynamics GP launch file
    • Creating users within Microsoft Dynamics GP
    • Granting company access to users
    • Defining security permissions using roles, tasks, and alternate and modified reports and forms group IDs
    • Assigning security to users
    • Using the security synchronization utility
    • Viewing user activity
    • Setting user preferences
    • Entering company information
  • 14. Post Installation Administration
    • Each database has its own set of options. Select the Auto Create and Auto Update Statistics for each database.
    • The Full recovery model provides a point-in-time recovery, but transaction log backups must be scheduled to keep from using up disk space.
    • Backing up data is vital. Backup company databases daily. When using a Full recovery model, backup the Transaction Logs at least twice a day.
    • Backup the forms and reports dictionaries for any products where forms or reports are modified.
    • Use the Microsoft Dynamics GP SQL Maintenance option to update statistics, recompile stored procedures, and drop and recreate tables and stored procedures. Remember dropping a table deletes data in a table.
    • Create a Database Maintenance Plan to automate database and transaction log backups as well as data optimization.
    • Check Links and Reconcile are Microsoft Dynamics GP utilities that attempt to repair damaged data. Be sure to backup data prior to using Check Links or Reconcile
  • 15. Performance Optimization & Troubleshooting
    • Optimization and troubleshooting issues are an ongoing process that requires patience, perseverance and constant attention. Asking the right questions can help narrow down the problem, including, if the issue occurs on one or, all machines and with one or, all users. Knowing the troubleshooting information presented in this course helps determine a course of action to fix the problem.
    • There are many tools available for troubleshooting:
      • SQL Server Books Online
      • SQL Server Profiler
      • Microsoft Dynamics GP KnowledgeBase
      • Microsoft Dynamics GP documentation, and more
    • Performing routine maintenance, such as from a Database Maintenance Plan, helps keep the application running smoothly. In the event of an error, keep an open mind. Write down all error messages, use all available resources, and take the necessary time needed.
    • Any user with posting rights can perform the batch recovery process.
  • 16. Process Server
    • Load the Microsoft Dynamics GP client software, including Process Server, on the computers that serve as Process Servers.
    • If using the DPM to balance the processing load between process servers in a service, check the box for Enable load balancing. This is strictly optional.
    • If load balancing is used, specify the hostname of the DPM in the Manager Host field.
    • To log process server information for verification and troubleshooting purposes, check the box for Track Start and End Times.
    • Define the Process Servers and the Services when using load balancing and a DPM.
    • Define which processes are to be sent for remote processing and designate the destination Server or Service.
    • Use the Process Monitor and Process Server Logs to validate that processing is happening correctly.
    • Clear Process Server Logs regularly when tracking start and end times to create a process server log
  • 17. Reporting
    • Microsoft Dynamics GP Report Writer can be used to modify existing reports and to create custom reports. Modified reports can print in place of standard reports in Microsoft Dynamics GP; custom reports are printed from a special location. Both modified and custom reports are stored in the reports dictionary for the corresponding product.
    • SQL Server Reporting Services is a component of Microsoft® SQL Server® and can be used to create static and dynamic reports. Reports can be accessed in Microsoft Dynamics GP using the My Reports list. The Microsoft SQL Server Reporting Services Wizard streamlines deployment of the SQL Server Reporting Services reports. The SQL Server Report Wizard simplifies the process of creating a report.
    • Microsoft FRx is a financial reporting tool for Microsoft Dynamics GP. Microsoft FRx uses the SQL Server databases for Microsoft Dynamics GP to access financial information. The ODBC data source and databases are defined in the Company Information window.
    • The Report Scheduler is used to schedule the publication of reports on a regular basis. Reports are identified for publication, and then associated with a schedule and publisher. Reports must be published to a UNC path, and can be published to HTML, Comma Delimited or Tab Delimited formats
  • 18. Thank You!