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:
In what looks to be the first in a set of analytics dahsboards, Mark Polino has released a Sales Analytics dashboard on his DynamicAccounting.net site.
The dashboard builds on the ideas covered in Mark’s recent Building Dashboards with Microsoft Dynamics GP 2013 and Excel 2013 and can provide a really good shortcut to getting started using an Excel dashboard rather than rolling your own from scratch.
Continue reading “Sales Analytics Dashboard Available Now From DynamicAccounting.net”
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:
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:
I updated one of my Microsoft Certifications yesterday by taking the MB3-700 Microsoft Dynamics GP 2013 Installation & Configuration exam.
The exam was fairly similar to the GP 2010 version I took a while ago, but this time round had a number of questions on the Web Client. Fairly fortunate that I’ve started writing a series of posts on it.
I’m looking to do the Financials exam later in the month and, if one is released, would like to get the Inventory & Order Processing certificate updated as well.
Back in April I did a series of posts on the new Microsoft Dynamics GP 2013 Web Client covering the installation and first use. In that series of posts I look at installing the web client as a single machine deployment.
Well, I thought it was time to do a series of posts on installing the Web Client as a scale-out deployment; that is, one where the components of the Web Client are installed on separate machines. This type of deployment is typically done by larger organisations who have need for multiple session hosts (the web client equivalent of a Terminal, or Citrix, server).
To install the scale out deployment of Microsoft Dynamics GP 2013 Service Pack 2, I have configured a number of test servers with, predominantly, Windows Server 2012 to use for his series of posts (Server Name in parenthesis):
I did, briefly, consider writing an overview of the architecture, services and infrastructure of the Web Client, but quickly decided that the Dynamics GP 2013 Web Client Infrastructure Overview post by Aaron Donat on the Developing for Dynamics GP blog was much more comprehensive than anything I would have done.
Over the coming days and, possibly, weeks, I will be taking a look through all the steps needed to create a scale out deployment of the Microsoft Dynamics GP 2013 SP2 Web Client (and only 10 months later than I told Brian R. that I would be doing this series of posts).
In Microsoft Dynamics GP 2010, Microsoft changed the underlying tables used by the Check Remittance; I believe this was for purposes of efficiency. However, the downside is that the table, pmRemittanceTemp, used to replace PM_Payment_WORK did not contain the vendor’s address or a link to a table which did.
In the past I have tended to use VBA to add the vendor’s address to the Check Remittance because it was quick and easy to do and I didn’t revisit this approach until Microsoft Dynamics GP 2013 was released. And the reason I revisited, was because of the new Web Client which does not support VBA customisations.
As always, I figured I might as well do a blog post about this and had it scheduled in to write when Richard Wheeler asked the question on the Community Forum. So, here is the step-by-step guide to adding the vendor address back onto the Check Remittance modified report.
Continue reading “Adding the Vendor’s Address To The Check Remittance”
After upgrading a client from Microsoft Dynamics GP 10 to 2013 they started getting a problem when creating, or editing, creditors. The error only came up when they had loaded the options window:
Microsoft Dynamics GP – Please enter a valid tax registration number.I did some testing and found that this error was produced when the Country Code field was set. Microsoft Dynamics GP 10 didn’t exhibit this behaviour, but there is a difference in the installation of version 10 and 2010. And that difference is the VAT Daybook.
In Microsoft Dynamics GP 2010, and later, the VAT Daybook module needs to be installed to use the VAT 100 report which I had installed during the upgrade process.
In this case, the client operates only in the UK and doesn’t need to have Tax Registrations recorded in GP, so they were able to just stop setting the Country Code field on the addresses.
I have received a copy of the newly published Microsoft Dynamics GP 2013 Reporting, by David Duncan and Chrisopher J Liley, from Packt Publishing to review. This is an update of a previous book the pair wrote for Microsoft Dynamics GP 2010:
The book covers an extensive range of the reporting tools in, or available with, Microsoft Dynamics GP 2013: