Yesterday, I posted the first in a series of posts on how to install management reporter; how to install Management Reporter – Prerequisites. Today I’ll cover the server side of the installation.
The first step is to download the installation packages; Microsoft Dynamics Management Reporter SP1 (Full Install) and Management Reporter Service Pack 2 October Update (PartnerSource or CustomerSource login required).
The server configuration I am using is four separate servers, all running Windows Server 2008 R2, but could easily be installed on one machine, or virtual machine, for use as a test system;
- Domain Controller (DC1) running the ideal domain (a slight departure from my usual azurecurve) on
- SQL Server (SQL1)
- Reporting Server (RPT1)
- Terminal Server (TS1)
The server installation is done on which the same machine that the prerequisites were installed upon; the Reporting Server (RPT1). Run the SP1 respun installer and select Management Reporter Server;
Accept the License Agreement;
Ensure all services are selected on the Customize Installation step;
At the Configure Service Account stage you have thee options for installing Management Reporter (Custom account, NT AUTHORITY\NETWORK SERVICE and NT AUTHORITY\LOCAL SERVICE);
When installing Management Reporter it is always advisable to install it with a Custom Account, but when making a demo system I often just use the NT AUTHORITY\NETWORK SERVICE account; in this instance I have a domain user, IDEAL\DynamicsGPUser;
This is a new installation of Management Reporter so select Create a new database;
As mentioned at the start of the post I have a separate SQL Server in this system so I entered the SQL database server name SQL1 (although if I had a CNAME DNS Alias configured for GPLIVE I should have used that instead) along with the sa username and password;
Check the database connection details;
For the Management Reporter Administrator I re-used the Service Account user but this could be any user within your organistion; I would generally advise that a ‘special’ user be used for this rather than someone from within your organisation. After all, this person may leave but creating, for example, a ReportingAdministrator user avoids this potential issue;
Next a Web Application Port needs to be specified. This wil default to 4712 but can be changed (ensure the selected port is open in the Windows Firewall);
Unfortunately, there is no confirmation step showing all selections just a step to click Install;
Once Management Reporter has finished installing you’ll see the following;
Which means it is time to install Management Reporter SP2. Run the setup and select Management Reporter Server;
Confirm the upgrade of Management Reporter from 2.0.1663.3 to 2.0.1700.31;
Fill in the details for the database server (the same details as in the original SP1 respun install);
And confirm the update should be installed;
Once the update has successfully installed a confimration will be displyed;
The final stage of installing the server component of Management Reporter is to install the Microsoft Dynamics ERP Data Provider ¯ Dynamics GP 2010. To do this you do not need to install the SP1 provider and upgrade it, you only need to run the Management Reporter SP2 setup (if you have previously installed the SP1 data provider you should uninstall it before installing the SP2 version);
If they are not present the Dexterity Shared Components 11 x64 will be installed (the standard Microsoft Dynamics GP Dexterity Shared Components 11 are the x86 version);
Confirm acceptance of the License Agreement;
Once installed successfully a confirmation dialog will be displayed and the server side installation of Management Reporter is completed.
Tomorrow I will be back with another post covering the client side of the installation.