Along with the web client which gives access to the normal functionality of Microsoft Dynamics GP there is also a Web Management Console which can be used by administrators to manage the web client.
The Web Management Console is accessed via the web browser by replacing the GP part of the address wit WebManagementConsole and logging in with a Domain Account which is part of the Domain Group assigned to the Web Management Console:
The Microsoft Dynamics GP Web Client is very similar in form and function to the desktop client, but there are some differences between the two.
The first of the differences is with the menu bar. The first image below shows the menu bar in the desktop client; the second shows that of the web client. As you can see the main difference is in the absence of the drop down menus from the web client:
With all components of the web client installed and configured, it’s time to verify that the web client is actually working correctly.
The way of doing this is quite simple; log in and check if data can be loaded, updated and saved. Open Internet Explorer and navigate to the log in page; enter your Domain user name and password:
The Microsoft Dynamics GP web client relies on Silverlight which needs to be installed on every client. When you log into the web client, and don’t have Silverlight installed, you’ll be presented with the option to install it:
To avoid certificate errors with the Web Client, the security certificate from the web server needs to be installed onto the client machines (i.e. all of the PCs which will be running IE to connect to the website).
Before the certificate is loaded, you’ll see the following error when navigating to the GP web client:
The performance of the web client can be improved by installing the Microsoft Dynamics GP Web Resource Cache.
To install the Microsoft Dynamics GP Web Resource Cache start the Setup.exe and select GP Web Resource Cache under Additional Products:
After installing the Session Hosts you will be prompted to run the Web CLient Configuration Wizard. We ran this after installing the Session Central server to create the databases; it needs to be run again now, to tell the Session Host which Session Central Database should be used:
In this post I’ll take a look at installing the session host servers; I’ll step through this process once, but it will need reproducing on all of the session host machines (which in my case is two).
Log onto the session host server and start the Microsoft Dynamics GP setup utility (setup.exe on the installation media). As the session host will already have the Microsoft Dynamics GP client and runtime installed, you will not see the Bootstrapper and be presented with the installation choices.
Select Web Client under Additional Products (fifth bottom):
After installing the Session Central the databases used by the web client need to be created and configured. This is done using the Microsoft Dynamics GP Web Client Configuration Wizard (available on the Windows Home screen or Start menu if you’re using an older version of Windows).
The next step in installing the web client is to install the session central server. This is done by running the setup.exe and click OK to allow the Microsoft Dynamics GP 2013 Bootstrapper Setup to install the prerequisites:
