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:
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…:
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:
This is not something I need for the series of posts I am currently writing on the Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment as my web server is running Windows Server 2012, but you may be performing the install on Windows Server 2008 R2 so I thought I would include this for completeness.
If you are running Windows Server 2008 R2 then extending a website with ASP.NET 4.5 required the use of the command line.
Open a Command Prompt with Administrative permissions and type the following and then hit Return:
Then type the following and hit Return:
Once the command has finished running, the website will be extended with ASP.NET 4.5 and be ready for the Session Control Service to be installed.
Extending a website with ASP.NET 4.5 required the use of command line (which I will cover in the next post), but Windows Server 2012 requires this be done using the Server Manager (there may be a PowerShell command to do this, but, if so, I don’t know what it is).
As I mentioned in a comment in the last post, if you’re installing IIS to configure the web client then you don’t need to treat this step separately, but merely add the step to the installation options for IIS.
To extend IIS on Windows Server 2012, you need to open Server Manager and click Add roles and features:
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:
Earlier in this series of posts, I took a look at installing the Web Client Runtime and adding the IIS server role. In this post I’ll take a look at installing a self-signed certificate (self-signed is really only a valid option for a demo or test system; on a live system you should really use a real certificate.
To create a self-signed one, open Internet Information Services (IIS) Manager and click on Server Certificates;
In this series of posts, I’m taking a look at installing the Microsoft Dynamics GP 2013 Web Client as a single machine deployment. To be able to install the Web Client, we need to have ISS installed. The server I am installing this on is a Windows Server 2012 so this is done via the Server Manager.
To add the ISS Role, click on Add Roles and Features;
To function the Microsoft Dynamics GP 2013 web client requires a web server running IIS with a web site bound to an SSL certificate.
The operating system of the web server must be one of the following:
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2012
Once you have installed one of the above, I chose Windows Server 2008 R2 for this install, the Web Server (IIS) role needs to be installed via Server Manager.
Open Server Manager and click the Add Roles link;