Keep up to date with the latest information about Microsfot Dynamics GP through articles from the Perfect Image and azurecurve blog.
Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Installing The Client
February 3rd, 2014 by
While most people reading this series are likely to already have an up and running Micrsoft Dynamcis GP system, I am going for completion in coverage for this series so I am going to be doing posts on items such as installing the client (this post), installing the server and deploying the sample company.
To install the Microsoft Dynamics GP 2013 SP2 client, run the setup.exe on the installation media. This will check if required components are installed or not and run the Microsoft Dynamics GP 2013 Bootstrapper Setup to install any missing components:
Under the Install heading click Microsoft Dynamics GP:
Select your country/region (I figure as the majority of readers are in the US, I might as well choose United States) and click Next:
Buck the trend and read the License Agreement and then click Next
Choose the features to install; I haven’t selected the Web Client Runtime at this point as I want to get the Microsoft Dynamics GP fully installed and configured with the Fabrikam sample company before doing so.
Click Next to continue:
Specify the SQL Server which wll host the Microsoft Dynamcis GP SQL databases as we’ll allow the installer to create the required ODBC entry.
You can also change the System Database Name at this stage. This is useful if you are going for a multi-tenant install (such as if you are a hosting partner), but this post is about is scale-out deployment so I’m happy to accept the default DYNAMICS:
Click Install to proceed with installing the Microsoft Dynamics GP client:
Once the installation is complete, a confirmation page will be displayed:
With the Microsoft Dynamics GP client installed on one machine, we can move onto creating the server install and creating the system database.
We will need to have the Microsoft Dynamics GP client installed on all of the Session Host machines.