Microsoft Dynamics GP 2013 Service Pack 2 is now available

Service Pack 2 for Microsoft Dynamics GP 2013 is now available for your consumption. Microsoft has released the product ahead of schedule - originally, September of 2013. I guess this will make for an even more exciting Microsoft Dynamics GP Technical Airlift 2013.

 

Service Pack 2 is probably the most comprehensive update so far to Microsoft Dynamics GP 2013 and includes a number of fixes and enhancements. Let's take a quick look:

 

Modules activated for Web Client:

• Field Service
• Service Call Management
• Depot Management
• Preventative Maintenance
• Project Accounting
• Manufacturing
• Bill of Materials
• Manufacturing Order Processing
• Master Production Scheduling
• MRP
• Manufacturing Suite
• Fixed Assets Enhancements
• Business Activity Statement (BAS) for Australian GST
• Payment Document Management (PDM)

 

Features Exclusive to Web Client:

• Visual Studio Tools for Web Client v1.0
• Keyboard Shortcut enhancements
• Change single machine configuration to support both the Web Client web site and runtime service using the same port  
• Add styling to ribbon to show focus  
• Web client messaging retry/refresh & Client Side error handling / notification improvements
• Better scrollbars for standard reports 

 

New Desktop & Web Client Features:

• GL - Roll down changes to Account Segment Description
• Reconcile checkbook without marking transactions
• Cash Receipts Inquiry display checkbook ID
• Customer Combiner & Modifier
• Vendor Combiner & Modifier
• Payables Void Enhancements
• AA Finance Charge assessment
• AA and Sales order deposits
• Payroll Inquiry Check Date Sort Options
• Applicant E-mail in HR
• Doc Attach 2.0:
• Document Flow
• Status Tracking
• Delete Password
• Attachment Properties
• Attachment Email
• Delete Utility
• SmartList Splitter
• SmartList Designer

Note: the SmartList Splitter was a cool piece of code made available with the Support Debugging Tool initially. If you are running Microsoft Dynamics GP 2010, you can take advantage of this via the Support Debugging Tool.

 

Service Pack 2 can be recognized by its new build number, 12.00.1482 and the Dexterity version is 12.00.0269. For more version details download the MDGP2013_MSPVersionList.xls file. For the install guide and a list of issues fixed, download the 12.0SP2_install_guide_ENUS.pdf file. Both files are available from the main Service Pack page (or from the links here).

 

Service pack 2 is available from the Service Pack 2 page or you can download the full updated DVD image:

PartnerSource
Product Release Downloads for Microsoft Dynamics GP 2013
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2013 

CustomerSource
Product Release Downloads for Microsoft Dynamics GP 2013
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2013 


The Microsoft Dynamics GP Support and Services Blog has more information related to Service Pack 2. Please visit their page for more information:

• Service Pack 2 for Microsoft Dynamics GP 2013 is now available!

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 on Windows Azure: Wrap Up

It's been fun trying to get Microsoft Dynamics GP 2013 Web Client to run on Azure. The bottom line is Windows Azure offers a very compelling deployment case for organizations running their applications (SaaS) and infrastructure (IaaS) in the cloud.

While many Azure platform features are still in Preview mode, I can say unequivocally that what's there works very well - too well, indeed. I had a few hiccups and I had to drop and recreate some VMs a few times, but I attribute that to the fact that I wasn't too aware of some of the feature settings. Also, a great deal had to do with the fact that my environment was running in free trial mode.

I also found that VMs tend to be a bit undersized on Azure. For example, a "Large" VM is 4 cores + 7GB in ram, which leads me to believe that the Azure platform is more geared towards lightweight applications than heavy, user-driven, business applications. Maybe I am making the wrong assumption here, but a decent size Dynamics GP deployment, involving 50+ users, may need up to 4 web servers and 4 session hosts to minimize any performance impact due to high user volume versus provisioned hardware capabilities.

Overall, the installation of Microsoft Dynamics GP 2013 Web Client wasn't without its head scratching moments. For example, certificates need to be switched to server public DNS names. While I got the Web Client up and running with the private DNS names, making the switch to public DNS for the certificates proved to be a task requiring reinstallation of the Session Service portion of the web client on the session host machine - changing the certificate for the IIS web site proved fairly simple.

Nonetheless, I had a lot of fun working on this "mini-project" so I leave you with a link to each of the articles I wrote on the subject:

Microsoft Dynamics GP 2013 on Windows Azure: Subscription Process
Microsoft Dynamics GP 2013 on Windows Azure: Provisioning Process
Microsoft Dynamics GP 2013 on Windows Azure: The Deployment Process

In closing notes, Azure provides a serious deployment option for middle market organizations looking for a serious infrastructure hosting partner. The deployment procedures for Microsoft Dynamics GP are no different than those for an on-premise or hosted network, however proper security planning goes a long way to ensure your financial data is highly secure. Still, more documentation on the Azure installation process is required, and I know it is being worked on as I type.

A big thank you goes out to Daryl Anderson, Senior Program Manager at Microsoft for all his guidance and assistance troubleshooting some of the difficulties I experienced during this effort. Daryl continues to work tirelessly to document the entire implementation process.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 on Windows Azure: The Deployment Process

Welcome to the third installment on Microsoft Dynamics GP 2013 on Windows Azure. In the previous article I showed how to provision the various VMs needed in our environment - see Microsoft Dynamics GP 2013 on Windows Azure: Provisioning Process. The following is a summary of the VMs with the applications and services they will be running:

Server Name	Function
ip-ads01	AD DS server
ip-sql01	Database Server
ip-gp01	GP and Session Service
ip-gpweb	IIS, Web Client, WMC, and Session Central

The deployment started out with some prep work, as follows:

Active Directory Server (AD DS)

On the AD DS server, I setup a few domain user accounts and security groups that will be needed to run both Microsoft Dynamics GP's Session Service and Session Central Service services on the GP server (ip-gp01) and the Web Client and Web Management Console application pools on IIS (ip-gpweb). In addition, I have created two security groups, GP Web Admins to add any Dynamics GP web administrative user, and GP Web Users to add any domain account that will be accessing the Microsoft Dynamics GP via the web client interface.

Active Directory Users and Computers

Microsoft Dynamics GP Server (Session Host)

With the domain accounts and groups needed out of the way, I proceeded to install Microsoft Dynamics 2013 and the Web Client Runtime on ip-gp01. The installation is straight forward as you would expect with most GP installs. If you have configured your DNS server properly the ODBC configuration done by Dynamics GP should happen without a hitch. Upon completing the initial file installation, you will run Dynamics Utilities to setup the application system database - thanks to the new named system database feature in Dynamics GP 2013, I have called this DYNGPSYS - and setup the sample company, Fabrikam.

On this server also, I will setup a self-signed certificate pointing to my public DNS for this machine, ip-gp01.cloudapp.net, which I will export and import on my local machine. Another certificate is created for the private DNS, ip-gp01.ip-forest.local to create a secure communication between the web server and the session host.

For this, I use a tool called selfssl.exe which you can download below. Selfssl is a part of the IIS Resource Kit. From the command prompt with elevated administrative rights you can run the following command:

selfssl /N:CN=ip-gp01.clouldapp.net /V:365 /P:443 /T

Once selfssl generates the certificate, you can proceed to import the certificate into the Personal root and the Trusted Root Certification Authority folder using the Certificates mmc snap-in on the ip-gp01 VM. In addition, this same certificate must be imported on the IIS VM in the Trusted Root Certification Authority folder to provide a secure path to Session Service.


IIS Web Server

Next up was prepping the web server, ip-gpweb. The first task of order is to add the Web Server  (IIS) role to this VM, carefully making sure you select ASP.NET 4.5 from the Application Development Role Services for IIS - ASP.NET 4.5 is required by the Web Client components.

ASP.NET 4.5

Following the installation of IIS, you will then proceed to create a physical folder for the web client files - I took the easy way out and setup a C:\inetpub\gpweb.

In addition, I imported both certificates created for ip-gp01 to the Trusted Root Certification Authority folder to provide a secure path to the session host machine.

Finally, I used the selfssl.exe utility to create a self-signed certificate for the public DNS name of my machine, ip-gpweb.cloudapp.net.

selfssl /N:CN=ip-web.cloudapp.net /V:365 /T /P:443

I use this certificate to setup the web site in IIS, which is also a pre-requisite to the web client installation process:

Website created with self-signed certificate

Web Client Installation

The Web Client installation happens in two phases since I have provisioned a web server and plan to use a separate session host machine.

The Web Server

On the IIS server, you will need to run a custom install to select only the Web Server components.

Since you are working on Azure, to expose the website, you will need to create a new end-point on port 443 for the web server using the Azure Management portal (https://manage.windowsazure.com).

The Session Host Server

A custom installation to install the Session Server will do here.

The only tricky aspect is the runtime service, which requires a certificate to configure the service for SSL. Here I chose the cert previously created on ip-gp01. Note I am using port 443, which differs from the standard port, as it is the port I used when creating the certificate with the selfssl.exe utility.

Now that all is in place, you should be able to launch Internet Explorer from any machine outside of the Azure network and access Dynamics GP.

What I learned from this exercise:

1. Due to Azure's tight security, the provisioned servers have just the necessary TCP and UDP ports opened. On the SQL Server VM, you will need to open ports 1433 and 80 if deploying SSRS. SQL Server will also need to be reconfigured to support Mixed Mode Authentication prior to beginning the installation of Dynamics GP.

2. On the Dynamics GP and IIS servers, you will need to install .NET Framework 3.5 prior to running the Setup.exe application - by default, Windows Server 2012 installs .NET Framework 4.5. This could prove a bit confusing under Windows Server 2012, since during the confirmation process of adding the role, you are confronted with a warning message requesting an alternate path to the .NET Framework 3.5 installation files.

Add Roles and Features Wizard

As it turns out, the resolution is fairly well documented in Microsoft Support KB article 2734782 - http://support.microsoft.com/kb/2734782, which calls for running the Deployment Image Servicing and Management tool (Dism) from the command line. Now, I happened to have the Windows Server 2012 installation files on a 32GB pen drive a carry around. By remoting into the GP and IIS servers with my local drives enabled I was able to point to the Sources folder on my pen drive allowing the .NET Framework 3.5 to be installed.

Dism /online /enable-feature /featurename:NetFx3 /All /Source:(folder_name)\sources\sxs /LimitAccess
 

3. It's easier to download the Silverlight client on your local machine and move it to your IIS VM, than attempting to install it from your IIS VM directly. As it turned out, Internet Explorer security on Azure disables scripting, so accessing any Microsoft website, ironically becomes a nightmare. You can download Silverlight from http://www.microsoft.com/silverlight/

4. The tenant configuration file, TenantConfiguration.xml, must list (not point to, i.e., no UNC path) the paths on the session host server for each of the GP application runtime files requested. The tenant configuration file is a part of the Web Client files on the IIS VM.

There may certainly be other details that I may have forgotten to point out and other issues you may encounter along. This wasn't an easy process and frankly required quite a bit of research and bugging people like Microsoft's Daryl Anderson to get this right, but the effort was well worth it.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 on Windows Azure: Provisioning Process

Welcome to the second article on Microsoft Dynamics GP 2013 and Windows Azure of this installment. In the first installment, I showed how to create an Azure account and setup a subscription - see Microsoft Dynamics GP 2013 on Windows Azure: Subscription Process.

This time around I will review the virtual machines (VMs) provisioning process. For all intends and purposes, this environment will consist of an Active Directory Domain Server (AD DS), required to support authentication within our Azure environment; a Microsoft Dynamics GP application server, which will serve as a session host, therefore running GP and the Web Client Runtime; a Microsoft SQL Server database server, which will host the GP databases, the Web Management database, Session Central database, and Tenant Services database; and finally, a web server running IIS to support the Web Client itself along with the different session services required to run our web application.

For more information on Microsoft Dynamics GP 2013 web client architecture, see Dynamics GP 2013 Web Client Infrastructure Overview over at Developing for Dynamics GP.

All these VMs need to be a part of an Azure Virtual Network (AVN), so you must start by creating one. The purpose of this article is not to discuss how to setup an AVN as there are some considerations for this, especially if you are going to network with your on-premise network. For more information on the steps required see Create a Virtual Network in Windows Azure. Suffice to say, the AVN I created is a pure cloud network and will not interact with my on-premise network.

Provisioning the Virtual Machines

In order to begin the provisioning process, it is necessary to go to the Windows Azure management portal - https://manage.windowsazure.com. If you have completed a new subscription, the welcome page will direct you to setup a new asset for the environment.

Azure Management Console

Active Directory VM provisioning

The first thing in my list is an Active Directory VM which I will call ip-ads01. This VM will serve up my environment's domain controller - my domain will be called ip-forest.local - and will act as a DNS server as well. It will also allow me to create my environment's users and add the necessary security groups needed for the Web Client. Please consult with a network administrator on the steps required to setup AD DS. You can find more info in the following Microsoft TechNet article: AD DS Design Guide.

One of the cool aspects of Azure is the ability to select the type of memory and core you will be needing for your VM. I decided to go with a Large server, since I will be running Windows Server 2012 and AD DS management console tends to also use up some memory.

Once the server is been provisioned, setting up AD DS and making the server a primary domain controller should be fairly straight forward (using Server Manager) - dcpromo has been deprecated in Windows Server 2012 - see Introducing the first Windows Server 2012 Domain Controller (Part 1 of 2) over at the Server and Management team blog.

Dynamics GP VM provisioning

Once we complete the AD DS server setup, it's time to move on to provisioning the Dynamics GP VM. The process is similar to the Active Directory server provisioning. Here, I am also choosing a Windows Server 2012 machine to run the Dynamics GP client and the Web Client Runtime - in conjunction our session host server.

VM OS Selection

This server will be known as ip-gp01 and I will use a Large size setup to begin with. Note that in Azure you can change your VM configuration to increase or decrease the amount of resources you are using.

VM configuration

Next is the VM mode configuration, which could pretty much be summarized as setting up the VM's DNS on your Azure network. For obvious reasons, I am removing my Azure DNS extension in the picture below.

Finally, in the step of setting up the VM, you will want to assign an availability set. Again, not a topic for this article, but suffice to say something critical to consider during your Azure planning if you are to ensure maximum application uptime - see Manage the Availability of Virtual Machines for more information.

VM Options

Once you have navigated through the simple 4 step process, the provisioning process begins. From end-to-end this should be no more than 3 minutes, which I find to be very impressive.


Provisioning process kicked off for our first machine

SQL Server Provisioning

Not to be confused with SQL Azure, we will be provisioning a standard VM running a full version of Microsoft SQL Server 2012 Evaluation Edition. Interestingly enough, you can only get this on a Windows Server 2008 R2 operating system if you decide to use the standard gallery image. The alternative, of course, is to provision a standard Windows Server 2012 VM, then manually load SQL Server 2012 on it. Again, since this is a demo environment and my intent is not to install GP on the SQL Server - just one of those best practices items that I follow - I will continue and provision the standard image available from the gallery.

Microsoft Dynamics GP is not supported on SQL Azure (yet!) due to a number of design limitations in the latter, for example, cross-database operations. This is significant since Dynamics GP makes extensive calls to the system database from within the company database.


From here on, the VM configuration is standard. I chose to name this machine ip-sql01.

The final VM to provision is the web server, for which I will be using a Windows Server 2012 image and will add IIS later. You can follow the instructions in Installing IIS 8 on Windows Server 2012 after the provisioning process has been completed to get IIS up and running.

A few notes from this exercise...

1) Once you have provisioned all machines, you will need remote into each to change the DNS settings on each to point to your DNS server on your AD DS VM. At this point, you can join them to the domain. To remote into a machine, highlight the VM and click on the Connect button at the lower end of the screen.



Management Console screen

2) On the SQL Server, you will need to open ports 1433 and 80 to the domain only. Port security is pretty tight for the provisioned VMs. In addition, you will need to change SQL Server security to Mixed Mode and configure SQL Server Reporting Services by using the standard Reporting Services Configuration tool.

3) The PING command line utility is disabled in Azure, so don't try to use it. You cannot ping a VM from another one. A good measure of success is attempting to add your servers in Server Manager on your AD DS VM. If you can add each server, you are good to go which means TCP/IP is working as expected within your Azure virtual network.

My next installment will focus on getting the GP session host up and running. As we move through each server installation, I will continue to point out other considerations in making this all work.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 on Windows Azure: Subscription Process

In my previous article, I provided an intro on the necessary elements required to deploy Microsoft Dynamics GP 2013 on Windows Azure - see Deploying Microsoft Dynamics GP 2013 on Azure - Introduction. Now, I begin a series of articles showing step by step how to configure the platform.

The first thing you will need to do is setup a subscription. As it turns out, Microsoft is running a 90-day free trial, how about that? The free trial allows you some good room to get a couple servers required for setting up a Microsoft Dynamics GP 2013 session host and the Web Client. Storage is set currently at 35 GB, so I believe we have plenty room to play.

So on we go by clicking the Free Trial option, which takes us to the Sign In page. Authentication is done via your Windows Live account, so one is effectively required.

Don't worry! Even if you haven't signed into Windows Azure before, you will be prompted to follow the account creation process. You will now be able to see what's being offered as part of your 90-day free trial. Ah, don't forget your credit card. You will not be charged as your initial spending limit is defaulted to $0 during the free trial period. A credit card is also required to verify your identity.

Upon clicking the arrow to continue with the account creation and subscription process, you are now faced with the credit card entry window. Very simple! Pop out your shiny [favorite card name here] and just follow the data entry fields. Click the next button to validate the credit card info and complete the account setup and subscription.

Once the credit card is validated, you are good to go. You will now be sent back to the Azure home page where you can manage your account and go to the administrative portal. My next article will focus on how to provision the machines needed to setup our Microsoft Dynamics GP environment.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Deploying Microsoft Dynamics GP 2013 on Azure - Introduction

Today is the BIG DAY! Microsoft Dynamics GP 2013 has been released!

PartnerSource: Microsoft Dynamics GP 2013 Product Release Download page
Microsoft Download Center: Microsoft Dynamics GP 2013 What's New


With that said, I wanted to move forward and start to look at some really cool stuff you can do with Microsoft Dynamics GP 2013 and the Web Client. Now that I've had a chance to deploy the Web Client on a number of sandboxes here in my test lab and pretty much have all the on-premise deployment down, it's time to show you one more cool stuff: Microsoft Dynamics GP 2013 and Web Client deployment on Microsoft Azure platform.

Windows Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment. The overall goal of Windows Azure is to provide a scalable PaaS (Platform as a Service) and IaaS (Infrastructure as a Service) to subscribers.

Examples and SDKs are available in the Developer Center at

http://www.windowsazure.com/en-us/develop/overview/.

Microsoft Dynamics GP 2013 Azure Deployment

A Microsoft Dynamics GP 2013 deployment on Microsoft Azure focuses on 4 main aspects (assuming you have already completed all the sign up and subscription process):

1. Provisioning a virtual network, which can be optionally integrated to your local network.
2. Provision an Active Directory Domain Controller to manage the virtual network environment. (optional depending on whether you integrate the virtual network to your local network or not)
3. Provisioning the different virtual machines to support the IIS web server, Web Client, and Web Management Console applications; the various services (Session Central, Session Service, Tenant Services, and the GP Web Services) if deploying each service on separate servers; and the session hosts virtual machines to host the Microsoft Dynamics GP runtime client.
4. Provisioning a Microsoft SQL Server 2012 virtual machine and storage to host the various company and system databases and deploy a Reports Server.

NOTE: SQL Server 2012 will need to be reconfigured to support SQL authentication. The standard galleries provided on the Azure platform are configured by default to support Windows authentication. SQL Azure is currently not supported with Microsoft Dynamics GP 2013 on Windows Azure.

A simple Azure deployment environment is shown in the above picture.

Once the environment has been provisioned, the Microsoft Dynamics GP installation process is fairly comparable to that of an on-premise installation. The installation process will start by installing Microsoft Dynamics GP desktop client on the web client server (or on the SQL Server) and running GP Utilities to set up the databases. The installation is done via Remote Desktop Client which is used for management of the environment only.

Up next is the installation of the web client and web management console applications on the IIS web server. An endpoint will need to be created using the Azure Management Portal for Internet access to the virtual machines. Upon completing the deployment of the Azure environment, access to GP is achieved via Internet Explorer from outside the Azure virtual network.

This is just the proverbial tip of the iceberg. In the next few days, I will be whipping out the credit card to setup an Azure subscription and walk through all the different provisioning steps and the Web Client installation process. I will detail all of these in a series of articles to come.

Special thanks to Daryl Anderson, Senior Program Manager and Aaron Donat, Senior Escalation Engineer at Microsoft for their input and editorial contribution to this article

Downloads

Microsoft Dynamics GP 2013 and Windows Azure (D109GPandAzure.pptx)

Resources

To read more about Microsoft plans for the Dynamics applications and Azure, click on the following link over at MSDynamicsWorld:

Microsoft Shares Updated Azure Plans for Dynamics NAV 2013, GP 2013, AX

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Windows 8 and the Microsoft Dynamics GP Web Client Series - Update

Since the last time I blogged about Web Client and Windows 8, a lot has transpired since - and I mean a lot! You can read the complete series of previous articles here:

Windows 8 and the Microsoft Dynamics GP Web Client Series - Wrap Up

The first major development is, since the Microsoft Dynamics GP 2013 Beta code was released on PartnerSource, around the time of the Microsoft Dynamics GP Technical Airlift 2012 event in Fargo, the Microsoft Dynamics GP development team has put out two major build updates - internally, they continue to create builds almost on a daily basis to keep up with testing demands.

The two builds I have received so far (12.00.1118 and 12.00.1204) have been pretty darn stable on Windows 8 Professional and Windows Server 2012 Standard editions, with the latter build featuring a blazing fast - and I mean super fast - web client. Much faster than the Beta release and certainly much faster than build 12.00.1118.

The second major development is the web client installation process now adds a few more setup screens (I will follow up in a new article), creates one more database for the Session Central service (GPWEBCLIENTSESSIONCENTRAL), and automatically install the certificates for Silverlight access to the local resources on your computer - the Silverlight certificate installer works well on Windows Server 2008 R2, but had issues with Windows 8 and Windows Server 2012, since the certificate stores are slightly different on these releases of Windows. We (with the help of Aaron Donat) completed the certificate installation manually, which wasn't much of a big deal.

If installing Multi-Tenant Services, the main item to keep in mind is that the user account that is running the Application Pools MUST NOT BE an administrator account - I ran into this issue and this is probably what was causing the following error when attempting to access the Web Management Console.

The only solution to this problem (at the moment) is to uninstall web client and reinstall using a non-admin user for the Application Pool. The installer takes care of setting the proper SQL Server permissions for the account to be used on the application pool.

In summary, if you are going to use the same user account for ALL of the services, then you won’t be able to get into the Web Management Console. Please use a different account for the Application Pools. All other services could use the same account if desired - even on a Single Machine deployment.

Some of the logging options have also changed with build 12.00.1204 (and presumably any new build after that).  In order to get the exceptions to appear in the Dynamics Event Log or back to the Errors.aspx page, the web.config file must be edited to include additional information right after the closing system.servicemodel tag and between the system.diagnostics tags. This will start dumping the exceptions to the Dynamics event log. This should be incorporated as part of the web.config by the time Microsoft Dynamics GP 2013 is ready to be shipped.


Web.config

If you also want to have the stack trace dumped out to the Errors.aspx page as well, add the following KEY to the appSettings section and set the value to true.

Stay tuned for my next article which will walk through the new installation procedures for web client and keep an eye over at Developing for Dynamics GP for new articles further detailing some of these changes.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Windows 8 and the Microsoft Dynamics GP Web Client Series - Part 2b

Windows 8 and the Microsoft Dynamics GP Web Client Series
Part 2b

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

---

Now that we have Microsoft Dynamics GP 2013 and the Web Client Runtime installed, it's time to take a look at the Web Client installation process.

Web Client Installation

The installation process starts with the usual legalese stuff around Licensing Agreement and why you must accept these terms - pretty simple: you don't and you cannot install the software.

License Agreement

Once you pass the first screen, you are at the point of choosing between the two installation options. In the case of a single server (or word warrior workstation like mine) you will want to choose the Single Machine option. However, if you have multiple servers playing in your environment and you want the ability to segment services and what's not, then the Custom option is the way to go.

Installation Option

The Windows User Group window allows you to specify either the Web Client User group or user account and the Web Management Console user group that will be allowed to access the Web Client or administer the environment, respectively. Here we will be using the local accounts we setup in Part 1 of this series.

Typically, most customers will already have an Active Directory group in their domains where they already have Microsoft Dynamics GP users added to, since nowadays you need something similar to access SQL Reporting Services and Business Analyzer reports (if you are into making administration easier). So this is where I recommend using what you already have.

As for the Web Management Console, this will probably continue to be in the domain of the Microsoft Dynamics GP system administrator or simply become an extension to the functions of the overall system administrators in the organization.

Windows User Group

The next option is to enter the domain account that will be used as the application pool identity for the Web Client website. Again, here we will use the account we created in Part 1 of this series.



Web Site Configuration

Next up is creating a database to store our Web Management Console settings. If you are going to use Windows Trusted Authentication, the account you are using should have at least dbcreator rights on SQL Server to be able to do this.

Web Management Console database

Session Central service communicates with the website and maintains stats on all the session services running on the session host machines. Session Central service listens in on port 48650 by default (you can configure your own). If using SSL, you must select the personal store certificate created in Part 1 of this series. The port will automatically be setup on the firewall by the installation.

Session Central Service

As far as analogies go, think of Session Central service as a Distributed Process Manager (DPM). For more information on DPM, take a look at the Microsoft Dynamics GP 2010 Architecture Whitepaper.

Session Service is a Windows service that runs on the Session Host machine and is responsible for authorizing users, creating user sessions, retrieving existing sessions, and monitoring sessions to report back to the Session Central service.  The Session Service will also start a shell instance of Dynamics GP,  also referred to as a Runtime.Process.exe, at the time a requesting GP Web Client users is authenticated as a valid user.

Session Service listens in on port 48651 by default (you can configure your own). If using SSL, you must select the personal store certificate created in Part 1 of this series. The port will automatically be configured on your firewall by the installation.

Session Service

Again, as far as analogies go, think of Session Service as a Distributed Process Server (DPS) instance. For more information on DPS, take a look at the Microsoft Dynamics GP 2010 Architecture Whitepaper.

Finally, we need to specify the Runtime Service URL which by default listens in on port 48652. This URL provides the information for building the user's session address (in the form of https://machineaddress:48652/RuntimeService/pID) where pID is the process ID generated by the GP shell application.

Runtime Service URL

This is the only part of the configuration where an SSL certificate is strictly required.

The final aspect is to review the installation settings and kick off the install itself.

Install Progress

Progress Bar

A key troubleshooting aspect from all of the above is to ensure that the GP Session Central Service and GP Session Service are running. For that, you can check the Services panel under Administrative Tools or Computer Management.

GP Session Central Service and GP Session Services should now be running 

This concludes the installation portion of the Web Client and so far we have not ran into any issues with the process itself.

---

Now, it's time to launch the Web Client...

In my first attempt to launch the client I received the following error:

HTTP Error 403.14 - Forbidden

The Web server is configured to not list the contents of this directory.

Most likely causes:

A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

Things you can try:

If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.

Enable directory browsing using IIS Manager.
1.     Open IIS Manager.
2.     In the Features view, double-click Directory Browsing.
3.     On the Directory Browsing page, in the Actions pane, click Enable.

Verify that the configuration/system.webServer/directoryBrowse@enabledattribute is set to true in the site or application configuration file.

 

Detailed Error Information:

Module	DirectoryListingModule
Notification	ExecuteRequestHandler
Handler	StaticFile
Error Code	0x00000000
Requested URL	https://mgb003:443/
Physical Path	C:\inetpub\gpweb
Logon Method	Anonymous
Logon User	Anonymous

 More Information:

This error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server.

View more information »

Clearly, I did not want to enable directory browsing, but after noticing that the site wasn't even launching it was evident that the ASP.NET client was not installed on the site. As mentioned yesterday, this problem was solved by applying the steps outlined in the TechNet article, Installing IIS and ASP.NET Modules. I once more checked my website and now had the following folder under my Web Client website.

aspnet_client folder under gpweb Website

The fun did not end there. So, I will cover some troubleshooting topics tomorrow, before continuing into other findings.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More