Microsoft Dynamics GP 2018 RTM has now been released. In a series of posts, I am stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.
Before installing the Microsoft Dynamics GP 2018 RTM Web Client, I will be installing the prerequisites. As with the eConnect 18 Prerequisites, I am breaking out the Microsoft Dynamics GP 2018 RTM Web Client prerequisites into their own mini series. This is the series index and will automatically update as posts go live.
If a wildcard domain certificate has been used then you won’t need to follow the steps in this post. If, like me, you’re using individual machine certificates then you will have problems with trust relationships between servers unless you install the certificate from each machine on all of the others.
To accomplish this, the certificates need to be exported and then imported. As an example, I am going to transfer the certificate from the Session Control Server (SC1) to the first Session Host (SH1).
To do this open Internet Information Services (IIS) Manager, select the machine and double click Server Certificates:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Avoiding Trust Relationship Problems”
In addition to an SSL certificate for the Session Control Server certificates are also needed for the Session Hosts.
It is possible to add SSL certificates without the use of IIS, but I am not an expert in this area. To this end, I installed IIS the same way as on the Session Control Server and then created the certificate the same way too.
However, you choose to create the certificate for the Session Host machines, make sure you have one for each of the machines or apply the wildcard SSL certificate to each.
If anyone knows a way of applying a certificate to a machine without installing IIS I’d appreciate you leaving a comment below.
Now that the SSL certificate for the Session Central Server has been created, it needs to be bound to the website to which the Session Control Server will be installed.
To bind the certificate, open Internet Information Services (IIS) Manager and, in the Connections pane expand the server and Sites nodes and then right click on the website you intend to use, which in this example is the Default Web Site and select Edit Bindings…:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Binding An SSL Certificate To The Session Control Website”
The Session Control and Session Host machines require an SSL certificate. In a production environment I would recommend using a wildcard SSL domain certificate, but as this is only my test environment I am going to use a self-signed SSL certificate.
To create a self-signed SSL certificate, open Internet Information Serices (IIS) Manager and double click on Server Certificates:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Creating A Self-Signed SSL Certificate On The Session Central Server”
Before we can start installing the Microsoft Dynamics GP 2013 SP2 Web Client, there are a few steps which need to be completed.
The first of them is to install the IIS Web Server on the machine which will operate as the Session Control Server. In my case, this is the SC1 machine which is running Windows Server 2012. IIS is installed via Server Manager by clicking Add roles and features:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Installing IIS On Session Control Server”