Category: Internet Information Services (IIS)

Microsoft Dynamics GP 2018 RTM has now been released. In a series of posts, I am be stepping through the installation of Microsoft Dynamics GP and additional products ; the series index for this series of posts is here and will automatically update as posts go live.

I am taking a small break (sort of) from that post, to cover the installation/configuration of the prerequisites for the installation of the Microsoft Dynamics GP 2018 RTM web client (the installation of which is part of the Hands On series.

This is the first of the posts on installing and configuring the web client prerequisites; in this post I am going to cover the binding of the self-signed security certificate (created in the last post).

To bind the certificate, launch Internet Information Services (IIS) Manager, expand the server node, the Sites node and click on Default Web Site (I am just using the default website in IIS for the web client) and then click Bindings in the Action pane:

Microsoft Dynamics GP 2018 RTM has now been released. In a series of posts, I am be stepping through the installation of Microsoft Dynamics GP and additional products ; the series index for this series of posts is here and will automatically update as posts go live.

I am taking a small break (sort of) from that post, to cover the installation/configuration of the prerequisites for the installation of the Microsoft Dynamics GP 2018 RTM web client (the installation of which is part of the Hands On series).

This is the first of the posts on installing and configuring the web client prerequisites; in this post I am going to cover the creation of a self-signed security certificate.

The web client is a web based service, which requires a security certificate to be created and bound to the web site. Once IIS has been installed, it is a simple process to create a self-signed security.

To do so, launch Internet Information Services (IIS) Manager and click on the server name in the navigation pane. in the detail pane, double click on Server Certificates:

Microsoft Dynamics GP 2018 RTM has now been released. In a series of posts, I am be stepping through the installation of Microsoft Dynamics GP and additional products ; the series index for this series of posts is here and will automatically update as posts go live.

I am taking a small break (sort of) from that post, to cover the installation/configuration of the prerequisites for the installation of the Microsoft Dynamics GP 2018 RTM web client (the installation of which is part of the Hands On series).

This is the first of the posts on installing and configuring the web client prerequisites; in this post I am going to cover the installation of Internet Information Services (IIS).

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:

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.

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:

cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319\

Then type the following and hit Return:

aspnet_regiis –i

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:

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.