Microsoft Dynamics GP 2015 R2 was released at the end of May. As I mentioned at the time, I was away from home for work and rather busy otherwise so this series of posts has been somewhat delayed.
However, I am now getting my hands on GP 2015 R2 and thought I would do my usual set of posts on the installation of the various components and also the usage of the new functionality. This is going to be quite a long series of posts, so keep checking back regularly.
The sixth post covers a single machine deployment of the Web Client for Microsoft Dynamics GP. To install the Web Client run the setup.exe from the installation media and, under Additional Products select Web Client:
Continue reading “Hands On With Microsoft Dynamics GP 2015 R2: Web Client Install (Single Machine Deployment)”
If you do a scale-out deployment of the Microsoft Dynamics GP 2013 Web Client you may encounter trust relationship problems if you do not have the SSL certificates correctly installed:
An error occurred during session monitoring 'System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority 'sc1.domain.azurecurve.co.uk:48650'. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Continue reading “Troubleshooting The Microsoft Dynamics GP 2013 SP2 Web Client: Could Not Establish Trust Relationship”
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”