In the last couple of posts, I showed how to configure the server of Microsoft Dynamics GP by creating the System database and how to create a new company. In this post I’m going to run through deploying the Fabrikam, Inc. demo company.
To create the company, open GP Utilities () by right clicking and select Run as Administrator. Log in as the SQL System Administrator (sa);
Continue reading “How To Deploy The Demo Company In Microsoft Dynamics GP 2010”
In the last post, I showed how to configure the server of Microsoft Dynamics GP by creating the System database. In this post I’m going to run through the company creation process.
To create the company, open GP Utilities () by right clicking and select Run as Administrator. Log in as the SQL System Administrator (sa);
Continue reading “How To Create A Company In Microsoft Dynamics GP 2010”
In the last post I explained how to install the Microsoft Dynamics GP client and in this one I’m going to cover the server configuration. There is no server installation as such, as this can all be done from any client installation of Microsoft Dynamics GP.
To configure the Microsoft Dynamics GP server, right click on GP Utilities and choose Run as Administrator () and log in as the SQL System Administartor (sa);
Continue reading “How To Install Microsoft Dynamics GP 2010 – Server Configuration”
Having installed Microsoft SQL Server 2012 into a test environment and created the ODBC for connecting GP to SQL Server the next step is to install the Microsoft Dynamics GP client.
Microsoft Dynamics GP 9 was the last version which had a separate Server and Client installation; all versions since then have had only a single setup utility for both server and client.
When the setup utility (setup.exe) from the Microsoft Dynamics GP installation media is run, the Microsoft Dynamics GP 2010 Bootstrapper Setup will run to install the prerequisites;
Continue reading “How To Install Microsoft Dynamics GP 2010 – Client”
I’ve recently had the need to document the install process for Microsoft Dynamics GP 2010 for a new client so I thought I might as well finish off the task and but turning it into a small series of blog posts, the first of which will cover the manual creation of an ODBC connection.
To connect the Microsoft Dynamics GP client to the databases on SQL Server, an ODBC connection needs to be setup. In an x86 version of Windows this can be done using the ODBC Control Panel applet, but in an x64 version you need to use the x86 version of the ODBC Data Source Administrator.
The easiest way of accessing this is by using the Run window and opening %windir%\SysWOW64\odbcad32.exe;
Continue reading “How To Create An ODBC For Microsoft Dynamics GP 2010”
In this post I’m ging to give a run through of the installation process of the web client itself.
To install the web client run the Microsoft Dynamics GP 2013 setup utility and select Web Client from the list;
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).