Now that IIS is installed, we need to create a security certificate for use with the Microsoft Dynamics GP 2013 web client.
In a production environment I would use a proper signed certificate but for testing purposes, I’m going to go with a self signed certificate.
To create a self-signed certificate, open Internet Information Services (IIS) Manager, select the machine running the web site (in my case the machine is called GP2013TEST) and then double click on Server Certificates;
Microsoft are posting the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The forty fourth feature they’ve announced is Multitenant SQL Server Reporting Services Reports.
The current version of Microsoft Dynamics GP only supports a dedicated instance of SQL Server Reporting Services for each Microsoft Dynamics GP data instance. With the introduction of the Multi-tenant System Database Architecture, the SQL Server Reporting Services needed to be updated to allow for similar functionality.
With this Multi-tenant SQL Server Reporting Services Reports feature, multiple data instances can be deployed to a single SQL Server Reporting Services instance by allowing the implementer to to deploy the reports to a “tenant” folder.
Continue reading “MDGP 2013 Feature of the Day: Multitenant SQL Server Reporting Services Reports”
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:
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;
There are two security groups needed for the Microsoft Dynamics GP 2013 web client and these should be created prior to starting the web client installation.
The first is the Web Client Users group, of which users who will log into the web client will need to be members. The second is the Web Management Console Users group which is the group for administrators of the Web Client.
I have created these groups in Active Directory as GPWebClientUsers and WebManagementConsoleUsers respectively.
To run Microsoft Dynamics GP Web Services, there are four service accounts which are required:
For the single-server installation these accounts can be machine accounts but I would always recommend that even for this type of installation that they be limited privilege Domain user accounts which have a password that does not expire.
For a scale out, or multi-tenant configuration, these would need to be privilege limited Domain user accounts with passwords that do not expire. While these can all be the same accounts, I typically advise people to use a different account for each one (a legacy of dealing with Microsoft Dynamics CRM where it is recommended that each service is a different account).
In this single-server configuration I will be configuring four separate user accounts to use; one for each of the services.
In the next post, I’ll take a look at installing Internet Information Services (IIS).
Microsoft are posting the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The forty third feature they’ve announced is Update Item Allocation Inquiry In Field Service.
In the Item Allocation Inquiry window, Field Service now appears in the Module Restrictions box. You can now view item quantities allocated from Service Calls, RTVs and Depot work order documents. You can also use the Document Number field zoom to open the Field Service series inquiry window displaying the original document;
Continue reading “MDGP 2013 Feature of the Day: Update Item Allocation Inquiry In Field Service”
The first post in this series was a brief introduction which outlined the components within a web client deployment and the second covered the deployment options which are available. In this post I’m going to take a look at the process for installing the web client runtime.
Microsoft recommend that Microsoft Dynamics GP be installed, configured and confirmed as operating correctly before any of the components for the Microsoft Dynamics GP web client are installed.
Even if you’re using the web client you will still need at least one accessible desktop client as even though most of the administrative tasks of Microsoft Dynamics GP can be performed with the web client, some, such as creating companies, cannot.
Each of the servers which is being used as a session host must have a Microsoft Dynamics GP desktop client installation which can be connected to the Microsoft Dynamics GP databases.
The first post in this series was a brief introduction which outlined the components within a web client deployment which I’m going to follow up in this post with a look at the deployment options which are available.
There are three options when deploying the Microsoft Dynamics GP web client:
The single machine configuration is the simplest configuration available when deploying the Microsoft Dynamics GP web client. In this configuration, the web site, Session Central Service, Session Service and the Microsoft Dynamics GP web client runtime are all installed on a single server.
A typical single configuration machine is shown in the following diagram;
I wrote this post before the excellant and most comprehensive write up on the Microsoft Dynamics GP 2013 Web Client Infrastructure Overview done by Aaron Donat on the Developing for Microsoft Dynamics GP blog and decided to post this anyway as it gives a quick overview of the different parts of the web client as I kick off a series of posts on how to install the GP Web Client.
The Microsoft Dynamics GP 2013 Beta, including web client, is only available to partners and one important point to remember is that there is no upgrade path from the 2013 Beta to 2013 RTM so GP 2013 Beta should only be used for testing purposes.
The Microsoft Dynamics GP web client provides access to Microsoft Dynamics GP through Internet Explorer using a Silverlight plugin and closely matches the the user experience and functionality of the traditional desktop client.
Continue reading “How To Install The Microsoft Dynamics GP 2013 (Beta) Web Client – Introduction”
Microsoft are posting the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The forthy second feature they’ve announced is Edit Remit To Address.
In Payables Management when entering an invoice, you select the vendor address to which an invoice is to be paid. Now, with Microsoft Dynamics GP 2013, you can edit the remit-to address ID after the invoice is posted.
This is done by loading the open invoice in the Edit Payables Transaction window where the remit-to address ID can be changed;
This new feature is targeted at the following roles:
I covered a wide variety of topics mainly around GP and related products as well as a few around SQL Server but I’ve not actually done a post on the “correct” installation process of installing SQL Server for use with Microsoft Dynamics GP (I highlight correct as I’m sure some people will disagree with how I am doing the installation).
With the release of Microsoft SQL Server 2012 I thought it was time to rectify this. I am going to be installing the Enterprise Edition of Microsoft SQL Server 2012 but the process is the same for each of the versions. The install is being done as I usually do them on a VM for testing/demo purposes; I would pay more attention to security and the location of the log and data folders if this were being done on a production machine.
To install SQL Server, run the setup utility on the installation media which will open the SQL Server Installation Center;
