Tag: Microsoft Dynamics GP 2016 R1

Typically for a production environment, an installation of the web client would be done as a scale-out deployment whereby the different components are installed on different servers.

As I am working on a small number of servers in my demo environment (a Domain Controller, a SQL Server and a Web Client Server) I will be doing a single-machine deployment with the sessions central and session host services on a single machine.

To do this I have the Microsoft Dynamics GP desktop client installed on the Web Client: this is the only machine with a client installed.

To do this, I need to add the Web Client Runtime feature to the installation of the desktop client. To do this open the Programs and Features applet in Control Panel, select Microsoft Dynamics GP 2016 and click the Change button:.

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install the Web Client Runtime”

One of the new features introduced in Microsoft Dynamics GP 2016 R1 was an OData service which provides a new way to report off Microsoft Dynamics GP. Before OData can be used, the service ust be installed from the Dynamics GP installation media.

Load the setup utility from the installation media and, under Additional Products, click on :

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install The OData Service”

Microsoft Dynamics GP PowerShell has a number of cmdlets which can be used to administer Microsoft Dynamics GP. Before you can use them GP PowerShell needs to be installed.

The following command can be used to return all available cmdlets for Dynamics GP PowerShell:

Get-Command -module GP2016

The following example shows how GP PowerShell can be used to create a new company:

Add-CompanyDatabase -GPClientDirectory "C:\Program Files (x86)\Microsoft Dynamics\GP2016" -SqlAdmin "sa" -SqlAdminPassword "password" -SqlServerName "2016R1-SQL\GP" -CompanyName "azurecurve Publishing" -CompanyDbName "A16R1"-SqlMdfFilePath "C:\SQL Server\Data\" -SqlMdfFileName "GPSA16R1Dat.mdf" -SqlLdfFilePath "C:\SQL Server\Data\" -SqlLdfFileName "GPSA16R1Dat.ldf"

The supplied parameters and their values are:

• -GPClientDirectory “C:\Program Files (x86)\Microsoft Dynamics\GP2016”
• -SqlAdmin “sa”
• -SqlAdminPassword “password”
• -SqlServerName “2016R1-SQL\GP”
• -CompanyName “azurecurve Publishing”
• -CompanyDbName “A16R1”
• -SqlMdfFilePath “C:\SQLServer\Data\”
• -SqlMdfFileName “GPSA16R1Dat.mdf”
• -SqlLdfFilePath “C:\SQLServer\Data\”
• -SqlLdfFileName “GPSA16R1Dat.ldf”

You would replace the text between the quotation marks with the values you want to use to create the company.

Enter the cmdlet and parameters into GP PowerShell and hit return and the cmdlet will launch GP Utilities and create the new company; if you have any missing parameters or errors the launch will fail (usually with a less than helpful message).

Microsoft Dynamics GP 2015 RTM introduced PowerShell which can be used for a number of administrative purposes. To use the supplied cmdlets, Microsoft Dynamics GP PowerShell needs to be installed from the downloaded media.

Once you have the media downloaded, run the setup utility and, under Additional Tools, select GP PowerShell:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install Microsoft Dynamics GP PowerShell”

Microsoft Dynamics GP supports the use of cross-platform companion applications (such as the Business Analyzer app).

Run the Microsoft Dynamics GP setup utility and, under Additional Tools select Companion Application Services:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Installing the Companion Application Services”

Once the Web Services have been installed and configured, it is recommend that they be verified to ensure everything is working as it should. There are four items which need to be checked.

The first check, is to make sure that the Windows service is running; check this by opening the Services Control Panel applet (easiest to do by hitting Win+R and typing services.msc; scroll down and find Microsoft Dynamics GP Service Host. Ensure it is running and set to Automatic:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Web Services Verification”

With the Web Services for Microsoft Dynamics GP installed, it is time to do the configuration. The final step of the installation allows you to open the Web Services Configuration Wizard automatically, or it can be launched from the Windows start menu:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Web Services Configuration”

Since the introduction of Workflow 2.0 in Microsoft Dynamics GP 2013 R2, I have been doing a lot more installs of the web services. There are one or two gotchas (more at the configuration stage than the installation stage though) which I will highlight as we go through these next few posts.

Start the setup utility on the installation media. As web serices are likely to be installed on a server which does not already have any Dynamics GP components installed you will see the Bootstrapper Setup; click Install to install the required components:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Web Services Installation”

If you have a number of clients to install then the best way of doing this is to create an installation package. Do this by launching the setup utility and, under Install click Create Installation Package:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Create An Installation Package”

Once Integration Manager has been installed there is a final admin step which is required. Before it can be used, it needs to be run as an admin (to prevent errors) and the registration keys entered.

Find Integration Manager on the Windows start menu, right click and Run as Administrator:

Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Integration Manager First Run”