There are two security groups needed for the Microsoft Dynamics GP 2013 web client and these should be created prior to starting the web client installation.

The first is the Web Client Users group, of which users who will log into the web client will need to be members. The second is the Web Management Console Users group which is the group for administrators of the Web Client.

I have created these groups in Active Directory as GPWebClientUsers and WebManagementConsoleUsers respectively.

To run Microsoft Dynamics GP Web Services, there are four service accounts which are required:

1. GP Web Client site application pool – This is the service account which runs the application pool on the web site hosting the Microsoft Dynamics GP web client.
2. Web Management Console application pool – This is the service account which runs the application pool on the web site hosting the Web Management Console.
3. Session Central Service – This si the service account which runs the Session Central Service.
4. Session Service – This is the service account which runs the Session Service on each session host machine.

For the single-server installation these accounts can be machine accounts but I would always recommend that even for this type of installation that they be limited privilege Domain user accounts which have a password that does not expire.

For a scale out, or multi-tenant configuration, these would need to be privilege limited Domain user accounts with passwords that do not expire. While these can all be the same accounts, I typically advise people to use a different account for each one (a legacy of dealing with Microsoft Dynamics CRM where it is recommended that each service is a different account).

In this single-server configuration I will be configuring four separate user accounts to use; one for each of the services.

In the next post, I’ll take a look at installing Internet Information Services (IIS).

The first post in this series was a brief introduction which outlined the components within a web client deployment and the second covered the deployment options which are available. In this post I’m going to take a look at the process for installing the web client runtime.

Microsoft recommend that Microsoft Dynamics GP be installed, configured and confirmed as operating correctly before any of the components for the Microsoft Dynamics GP web client are installed.

Even if you’re using the web client you will still need at least one accessible desktop client as even though most of the administrative tasks of Microsoft Dynamics GP can be performed with the web client, some, such as creating companies, cannot.

Each of the servers which is being used as a session host must have a Microsoft Dynamics GP desktop client installation which can be connected to the Microsoft Dynamics GP databases.

Continue reading “How To Install The Microsoft Dynamics GP 2013 (Beta) Web Client – Installing The Web Client Runtime”

The first post in this series was a brief introduction which outlined the components within a web client deployment which I’m going to follow up in this post with a look at the deployment options which are available.

There are three options when deploying the Microsoft Dynamics GP web client:

1. Single machine
2. Scale out
3. Multi-tenant

The single machine configuration is the simplest configuration available when deploying the Microsoft Dynamics GP web client. In this configuration, the web site, Session Central Service, Session Service and the Microsoft Dynamics GP web client runtime are all installed on a single server.

A typical single configuration machine is shown in the following diagram;

Continue reading “How To Install The Microsoft Dynamics GP 2013 (Beta) Web Client – Deployment Options”

I wrote this post before the excellant and most comprehensive write up on the Microsoft Dynamics GP 2013 Web Client Infrastructure Overview done by Aaron Donat on the Developing for Microsoft Dynamics GP blog and decided to post this anyway as it gives a quick overview of the different parts of the web client as I kick off a series of posts on how to install the GP Web Client.

The Microsoft Dynamics GP 2013 Beta, including web client, is only available to partners and one important point to remember is that there is no upgrade path from the 2013 Beta to 2013 RTM so GP 2013 Beta should only be used for testing purposes.

The Microsoft Dynamics GP web client provides access to Microsoft Dynamics GP through Internet Explorer using a Silverlight plugin and closely matches the the user experience and functionality of the traditional desktop client.

Continue reading “How To Install The Microsoft Dynamics GP 2013 (Beta) Web Client – Introduction”