Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. How to deploy Microsoft Dynamics GP and Microsoft Business Solutions - Great Plains in a Terminal Server environment

How to deploy Microsoft Dynamics GP and Microsoft Business Solutions - Great Plains in a Terminal Server environment

View products that this article applies to.

INTRODUCTION

This article discusses tips to deploy Microsoft Dynamics GP and Microsoft Business Solutions - Great Plains in a Terminal Server environment.

↑ Back to the top

More Information

Follow these tips when you deploy Microsoft Dynamics GP or Microsoft Business Solutions - Great Plains in a Terminal Server environment:
  • We recommend that you have a dedicated server that is running Microsoft SQL Server and a dedicated server that has Terminal Server or that has Terminal Services enabled.
  • Verify that the terminal server meets the system requirements. To see descriptions of the system requirements, visit the following Microsoft Web site:
    https://mbs.microsoft.com/customersource/support/documentation/systemrequirements/
  • Citrix can also be installed in the environment. However, Citrix is not required.
  • When you install Microsoft Dynamics GP onto a terminal server, make sure that you are a local administrator and that you start the installation in Add or Remove Programs.
  • If you have modified dictionaries that are shared on the server, we recommend that you put the modified dictionaries onto the server that is running Terminal Server. Modified dictionaries are dictionary files such as the Reports.dic file and the Forms.dic file.
  • Microsoft Product Support Services supports the default configuration for Microsoft Dynamics GP. In this configuration, remote workstations start Microsoft Dynamics GP from the installation folder that is located on the terminal server. Remote workstations do not use user profiles or roaming profiles for the Dex.ini file or for the Dynamics.set file. Instead, remote workstations use the same Dex.ini and Dynamics.set files that are located in the installation folder.
  • When you set up Named Printers on a Terminal Server environment, you should consider the following:
    • Named Printers is machine-based. This utility stores a computer ID in the Dex.ini file for each workstation. Additionally, all settings apply only to the current workstation. Therefore, in a Terminal Server environment, all users share the same settings because the users are using the same workstation.
    • We do not recommend that you use Workstation Printers with Named Printers because the Workstation Printers can change depending on which computer is used to log on to a Terminal Server session. It is best to select only printers that are permanently visible to Terminal Server.
    • You can set up printers on a user basis. This enables different users to have different configurations on a single Terminal Server workstation.
    • If you are using multiple application folders on one Terminal Server or on multiple Terminal Servers, make sure that each Terminal Server has its own computer ID. You might need to manually edit the ST_MachineID setting in the Dex.ini file and then individually configure Named Printers on each instance of Terminal Server.
    • For a simple site where all users have the same printers defined, use System or Company class printers to set up Named Printers as if it is a single workstation.
    • For a more complex site where several remote locations access the server, you should use user class printers. You should do this so that each user has an individual configuration defined. However, when you use a user class printer, you must define it for all users. This may be time-consuming. Usually, all the users from a single remote location will want the same configuration. Named Printers lets you quickly set this up. To do this, you have to use Template Users feature in Named Printers.
    • For more information about setting up named printers, see the SystemAdminGuide.pdf file.
  • Do not use the local hard disk on the remote workstations for the placement of the Dex.ini file or of the Dynamics.set file. This configuration will create performance issues.

    Notes

    Many Microsoft Dynamics GP processes read back to the Dex.ini file.

    Put the Dynamics.set file and all dictionary files that are listed in the Dynamics.set file onto the server that is running Terminal Server.
  • When you set up named printers for users who access Microsoft Dynamics GP by using Terminal Services, visit the following Microsoft Web site to verify that the printer and the printer driver are supported:
    https://mbs.microsoft.com/customersource/support/documentation/systemrequirements/
  • Printer drivers that will be used by a remote workstation must be installed on the server that is running Terminal Server before the remote workstation logs on to that server.

↑ Back to the top

Keywords: kbfreshness2007, kbmbsgp10,, kbhowto, kbinfo, kbmbspartner, kbmbsmigrate, kb

↑ Back to the top

Article Info
Article ID : 872242
Revision : 1
Created on : 1/7/2017
Published on : 9/12/2011
Exists online : False
Views : 238