Last week I posted the start of a series of posts on how to install Management Reporter 2012; how to install Management Reporter 2012 – Server Prerequisites, how to install Management Reporter 2012 – Server Installation and how to configure Management Reporter 2012.
Todays post is the final post in the series on how to install Management Reporter and covers the client installation.
The client installer is part of the same installation package as the server installation (download available here (PartnerSource or CustomerSource login required).
On Monday the new version of Management Reporter was released, on Tuesday I posted the first in a series of posts on how to install Management Reporter 2012 server prerequisites and yesterday I posted the second part of the series on how to install the server software. Today I’ll cover the configuration of Management Reporter 2012.
To quickly recap, 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 configuration is done using the Configuration Console which is installed as part of the server installation, so in my case it is on the Reporting Server (RPT1).
Yesterday, I posted the first in a series of posts on how to install Management Reporter 2012; how to install Management Reporter 2012 – Server Prerequisites. Today I’ll cover the server side of the installation.
The first step is to download the installation package; Microsoft Dynamics Management Reporter 2012 (PartnerSource or CustomerSource login required).
One thing to note about the installation of Management Reporter 2012 is that it has been much simplified over that of Management Reporter 2; some parts have been removed (no separate provider to install) and some has been moved to the new Configuration Console.
With the release of Management Reporter 2012 I thought it might be worth doing a series of posts on how to install this version.
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 DOMAIN.MSDynamicsERP.co.uk
- SQL Server (SQL1)
- Reporting Server (RPT1)
- Terminal Server (TS1)
All of the installation of Management Reporter server, and the server prerequisites, will be done logged into the Reporting Server (RPT1); the client and initial configuration will be done on the Terminal Server (TS1).
The prerequisites for MR 2012 are very similar to those of Management Reporter 2 which were covered hereThe prerequisites of Management Reporter 2012 differ from Management Reporter 2 in that only the .NET Framework 4 is common between the two versions. The addition that MR 2012 requires is the Microsoft Access Database Engine 2010 Redistributable to be installed.
In some recent posts I’ve covered installing Management Reporter (prerequisites, server and clients) as well as doing the initial setup.
Once Management Reporter has been installed and initialised, typically the next step would be to configure security access and then start creating the building blocks required for the needed reports.
However, if you’re creating a demo system you might instead install the sample reports supplied by Microsoft which can be downloaded from either CustomerSource or PartnerSource (login required) which is what I am going to cover in this post.
Over the last few posts I’ve covered installing the Management Reporter prerequisites, server and clients; now it’s time to configure Management Reporter for use.
At the end of last week, I posted the first two parts in a series of posts on how to install Management Reporter; how to install Management Reporter – Prerequisites and how to install Management Reporter – Server.
Today I’ll give a run through of the Management Reporter client installation. To install the client, the same installation packages used to install the server, Microsoft Dynamics Management Reporter SP1 (Full Install) and Management Reporter Service Pack 2 October Update (PartnerSource or CustomerSource login required), are used. Continue reading
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. Continue reading
I’ve done quite a few posts on bugs and other problems recently, so I thought it about time to do a few How To posts; I opened last week with a post on how to install a domain controller and I’ve decided to follow up with a post on how to install Management Reporter. Or at least I intented it to be a post about Management Reporter but I then realised how many screenshots I’d taken and decided to break it down into several posts; the first of which will cover the server prerequisites. Continue reading
The release of Management Reporter brought several advantages over FRx; x64 compatibility, replacement of the Access database with SQL Server and a modern client among them. However, one of the downsides is that Management Reporter requires a domain to be available for both the installation and running.
Where FRx could be run on any PC or laptop regardless of the operating system, Management Reporter can only be run on a server OS. This means that the Business Development Managers, and I, need either a laptop with Windows Server 2008, or better the R2 version, installed or we need a VM with the same. To make everyday life easier I opted for the latter as I can install it once and then copy the VM between machines.
I am a Microsoft Dynamics GP consultant by training, certification and experience but I don’t have a huge amount of experience with Active Directory. I am the most knowledgeable here about installing GP and Management Reporter though, so it falls to me to do the setup of the demo systems and I figured I might as well do the full monty rather than getting someone else to install the operating system and then passing it back to me.
To this end I needed to learn how to install and configure Active Directory Domain Services (ADDS) and I thought it best to document here for anyone else interested and also for my own future reference. Continue reading