Windows 8 and the Microsoft Dynamics GP Web Client Series - Part 1
Windows 8 and the Microsoft Dynamics GP Web Client Series
Part 1
This series narrate my personal experiences of installing Microsoft Dynamics GP 2013 Beta and the Web Client in an unsupported environment. The following installation steps are for testing purposes only and were done on a test box. If you are to test, please make sure your machine is not a production box.
"While it's not supported, it doesn't mean it won't work. It only means we haven't tested it"...
Microsoft Dynamics GP Support
After returning from the Microsoft Dynamics GP Technical Airlift 2012, I am more than drinking all this Microsoft Dynamics GP 2013 Web Client Kool-Aid. And why not? After all, this is probably the biggest release to ever hit the block since the days of Microsoft Dynamics GP 6.0 - if you've been around long enough, you will remember that v6 had the first major facelift in the product history.
So, I figured the first thing I would be doing is rebuilding my machine with the brand spanking new Microsoft Windows 8 Professional 64-bit operating system, which I downloaded from MSDN. And so I set out to backup all my files onto my home storage area network (SAN), to blow away my current (now former) Windows 7 Ultimate install.
Installing Windows 8 went extremely smooth, with the usual couple reboots before the desktop was ready. To complete my install, I have added the following applications to my system:
...in summary, everything not currently supported for the installation of the Web Client. You can read more about the system requirements on Microsoft Dynamics PartnerSource.
System Requirements for Microsoft Dynamics GP 2013
Nonetheless, off I went to install Microsoft Dynamics GP 2013 and the Web Client.
Web Client Installation Pre-requisites
1. Certificate. Checked! At this stage, I created a self-signed certificate as would normally be accepted (required?) to setup the Web Client in a single machine configuration environment.
2. Required user accounts and user groups. Checked! For this step, I use Computer Management to setup two local users to my machine, GPUser and GPWebAccount. The former is a test user account to access the Web Client, the latter, a test account to access the Web Management Console. NOTE: under the current system requirements, these accounts must be created under Active Directory in a Windows Server 2008 R2 environment, so here's the second difference with the standard pre-requisites.
As you can see from the error above, IIS 8.0 is blocking the installation of ASP.NET 4.0 as it is expecting ASP.NET 4.5 to be loaded. NOTE: under the current system requirements, ASP.NET 4.0 and .NET Framework 4.0 are supported. This makes for the third difference with the system recommendations. The URL provided with the error did not provide much assistance. The main question at this point was, if ASP.NET 4.0 cannot be loaded, how would I then load the ASP.NET 4.5 client? After much search, I found a TechNet article describing the steps required to load ASP.NET 4.5 on Windows 8.
TechNet: Installing IIS and ASP.NET Modules
This article proved to be a live saver, since in Windows 8, the .NET Extensibility 4.5 and ASP.NET 4.5 are considered Application Development Features under IIS 8.
Upon following the instructions in the article, I was now able to see the aspnet_client folder under the gpweb virtual directory.
So far, the pre-requisites outlined here line up with those of the standard pre-requisites. If you are unsure of the Web Client architecture, have a look at Aaron Donat's article over at Developing for Dynamics GP:
Dynamics GP 2013 Web Client Infrastructure Overview
Tomorrow, I will describe some of the issues I ran into prior to ironing out the ASP.NET 4.5 client installation on IIS 8.0. Suffice to say, I tried installing the Web Client prior to having ASP.NET installed and that caused some other issues.
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
Part 1
This series narrate my personal experiences of installing Microsoft Dynamics GP 2013 Beta and the Web Client in an unsupported environment. The following installation steps are for testing purposes only and were done on a test box. If you are to test, please make sure your machine is not a production box.
"While it's not supported, it doesn't mean it won't work. It only means we haven't tested it"...
Microsoft Dynamics GP Support
After returning from the Microsoft Dynamics GP Technical Airlift 2012, I am more than drinking all this Microsoft Dynamics GP 2013 Web Client Kool-Aid. And why not? After all, this is probably the biggest release to ever hit the block since the days of Microsoft Dynamics GP 6.0 - if you've been around long enough, you will remember that v6 had the first major facelift in the product history.
So, I figured the first thing I would be doing is rebuilding my machine with the brand spanking new Microsoft Windows 8 Professional 64-bit operating system, which I downloaded from MSDN. And so I set out to backup all my files onto my home storage area network (SAN), to blow away my current (now former) Windows 7 Ultimate install.
Installing Windows 8 went extremely smooth, with the usual couple reboots before the desktop was ready. To complete my install, I have added the following applications to my system:
- Microsoft Office 2013 Preview
- Microsoft SQL Server 2012 Standard Edition
- Microsoft SQL Server Reporting Services
- Microsoft Visual Studio 2012
...in summary, everything not currently supported for the installation of the Web Client. You can read more about the system requirements on Microsoft Dynamics PartnerSource.
Nonetheless, off I went to install Microsoft Dynamics GP 2013 and the Web Client.
Web Client Installation Pre-requisites
1. Certificate. Checked! At this stage, I created a self-signed certificate as would normally be accepted (required?) to setup the Web Client in a single machine configuration environment.
 |
| Server Certificates in IIS 8.0 |
 |
| New Self-Signed Certificate |
2. Required user accounts and user groups. Checked! For this step, I use Computer Management to setup two local users to my machine, GPUser and GPWebAccount. The former is a test user account to access the Web Client, the latter, a test account to access the Web Management Console. NOTE: under the current system requirements, these accounts must be created under Active Directory in a Windows Server 2008 R2 environment, so here's the second difference with the standard pre-requisites.
 |
| Web client test accounts |
 |
| Web Client website (gpweb) |
 |
| aspnet_regiis error installing ASP.NET 4.0 |
As you can see from the error above, IIS 8.0 is blocking the installation of ASP.NET 4.0 as it is expecting ASP.NET 4.5 to be loaded. NOTE: under the current system requirements, ASP.NET 4.0 and .NET Framework 4.0 are supported. This makes for the third difference with the system recommendations. The URL provided with the error did not provide much assistance. The main question at this point was, if ASP.NET 4.0 cannot be loaded, how would I then load the ASP.NET 4.5 client? After much search, I found a TechNet article describing the steps required to load ASP.NET 4.5 on Windows 8.
TechNet: Installing IIS and ASP.NET Modules
This article proved to be a live saver, since in Windows 8, the .NET Extensibility 4.5 and ASP.NET 4.5 are considered Application Development Features under IIS 8.
Upon following the instructions in the article, I was now able to see the aspnet_client folder under the gpweb virtual directory.
So far, the pre-requisites outlined here line up with those of the standard pre-requisites. If you are unsure of the Web Client architecture, have a look at Aaron Donat's article over at Developing for Dynamics GP:
Dynamics GP 2013 Web Client Infrastructure Overview
Tomorrow, I will describe some of the issues I ran into prior to ironing out the ASP.NET 4.5 client installation on IIS 8.0. Suffice to say, I tried installing the Web Client prior to having ASP.NET installed and that caused some other issues.
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
Comments
I am curious about GP2015 Web client and multi-tenant environments. Do you know if I need to have a separate certificate for 2 instances of GP on 2 different app servers?
Hope you're doing well!
Thanks!
Adam
Certificates are installed on the web server, not on the session hosts. Even if you have an IIS web farm load balancing scenario, you will only need one certificate assuming you are using a central certificate store.
MG.-