I have just installed the reporting for FIM R2 RC and generated my first reports. Though when I say “just” read that as “spent two days on it and reinstalled twice”. However it is now working (yay! Was it worth it? Not sure yet!) and here’s my write-up.
You should also refer to the following documents from the FIM R2 media:
- Test Lab Guide: Demonstrating Forefront Identity Manager 2010 R2 Beta Reporting
- Test Lab Guide: Installing Forefront Identity Manager 2010 R2 Release Candidate
Here’s what I’ve installed into my lab:
||Two named instances of SQL:- FIM (Database)- SCDW (Database, Reporting)|
||SCDW Manager cannot be installed on the same server as SCSM.|
I’ll assume you already have SQL installed. I created seperate instances for FIM and System Center.
- The instance for SC needs Database, Full Text Indexing and Reporting Services.
- If you use the default collation you get a warning during installation about multi-lingual environments, so if this is an issue you will need to install with a suitable collation.
The FIM Service and Portal may already be installed, but you should not yet have installed the Reporting component.
I also disabled all the Windows Firewalls just to get it working. I’ll look into what ports I need to open up when I switch them back on later.
Install System Center Service Manager on the FIM server. (Note: I don’t know that it needs to be on the FIM server – that’s just how it is in my lab).
After completing these options you should be able to proceed with the installation.
Install System Center Data Warehouse Management Server onto its dedicated (or at least, seperate) server.
|Straight off you may see a couple of warnings.
|Configure the databases – Click “Staging and Configuration” and “Data Mart” in turn and point it at the SQL server and instance – in my case hosted on the FIM server.|
|Here for the name I just added “FIM” after the “DW_” that was already there. And as above I was lazy and reused the FIMSyncAdmins group.|
|Set the details of the SQL Reporting Server to be used by SCDW.
I’ve ticked the box saying I’ve taken certain manual steps but actually I haven’t done it yet so we’ll go do that now.(Incidentally if you forget these manual steps all the DW Management Packs deploy except for the ones named “* Report Library”.)
|Here’s the link where the manual steps are described: http://technet.microsoft.com/en-us/library/ff461215.aspx
First you copy the file Microsoft.EnterpriseManagement.Reporting.Code.dll from the Prerequisites folder on the System Centre DVD to the ../ReportServer/bin folder relevant to your named instance of SQL (more details about how to find this folder in the technote).
|Then there’s a piece of XML to be pasted into the ../ReportServer/rssrvpolicy.config file. You don’t need to modify the XML, but you do need to copy it at the same level as the other CodeGroup nodes.
While it doesn’t say in the technote, there is a comment at the bottom saying you should restart Reporting Services, which sounds pretty sensible.
|Now back to the SCDW installation – specify a domain account to run the service. This account needs to be a local Administator on the SCDW server.|
|I just used the same account for the reporting account. Again not sure if this is a good or bad idea, but it’ll do for now.|
Now you should be able to click Install and let the installation run.
Register the DW server with SCSM
Next you have to register the SC Data Warehouse Management Server with SC System Manager.
The last step is just to click Create and the registration should complete.
Wait for the Management Packs to finish deploying
The first time I installed I had a lot of trouble with DW jobs seemingly never finishing and no data appearing in the reports. So the second time through I made sure each step completed without errors before continuing on.
In the System Center console, if you open Data Warehouse -> Management Packs, you should see a list of Management Packs. Wait until all of them have “Completed” as their Deployment Status.
If any come up as “Failed” then troubleshoot that before proceeding. Note that when looking for error messages you have to go into the Operations Manager event log on the Data Warehouse Management Server – and not the server where you’re running the console.
Install the Reporting component of FIM R2
Otherwise just configure as appropriate for your environment and complete your Portal re/installation.
Run the DW Configuration Script
Run the FIM powershell cmdlets to create Report objects
The reporting data is exported by a workflow that is triggered by the creation of Reporting Job objects in the FIM Portal. There are a couple of powershell cmdlets that do this for you.
Wait for DW Jobs to complete
You won’t see any data in the reports until the following Data Warehouse Jobs have completed:
In the FIM doco there’s a section showing you how to create a script called ETLScript.ps1 that forces these jobs to run straight away. However in my environment the first two scripts are set, by default, to run every 5 minutes, and the last one runs once an hour. So you can either run the script, or wait an hour or so and then find data in the reports.
I found the following powershell cmdlets useful while I was waiting for the pot to boil. They have to be run on the SCDW Server.
You have to add the pssnapin SMCmdletSnapIn first.
All going well you should eventually see some data in the reports, which can be viewed in the SC Service Manager Console under Reports.