e2e: Configuring a simple HTTP Reporting Services Point in Configuration Manager

Previously I posted a blog for configuring reporting service point for “HTTPS” in ConfigMgr, but I have seen sometime people getting confused due to Certificates and URLs configuration when they are trying to configure it for HTTP (Simple) Reporting Service Point. The goal of this blog is to provide a step-by-step guide for configuring a Reporting Services Point in System Center Configuration Manager (on HTTP).

A brief introduction

Reporting in System Center 2012 Configuration Manager provides a set of tools and resources that help you use the advanced reporting capabilities of SQL Server Reporting Services (SSRS) and the rich authoring experience that Reporting Services Report Builder provides. Reporting helps you gather, organize, and present information about users, hardware and software inventory, software updates, applications, site status, and other Configuration Manager operations in your organization. Reporting provides you with a number of predefined reports that you can use without changes, or that you can modify to meet your requirements, and you can create custom reports.

SQL Server Reporting Services

SQL Server Reporting Services provides a full range of ready-to-use tools and services to help you create, deploy, and manage reports for your organization and programming features that enable you to extend and customize your reporting functionality. Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality for a variety of data sources. Configuration Manager uses SQL Server Reporting Services as its reporting solution. Integration with Reporting Services provides the following advantages:

  • Uses an industry standard reporting system to query the Configuration Manager database.
  • Displays reports by using the Configuration Manager Report Viewer or by using Report Manager, which is a web-based connection to the report.
  • Provides high performance, availability, and scalability.
  • Provides subscriptions to reports that users can subscribe to; for example, a manager could subscribe to automatically receive an emailed report each day that details the status of a software update rollout.
  • Exports reports that users can select in a variety of popular formats.

In this example, we will use a scenario where my Report Server, SSRS (SQL Server Reporting Services) is locally hosted and the ConfigMgr Site Database is also located locally. However, you can have your Report Server at a Remote Site Server as well.

Verify and make sure that Report Server version and SCCM Database version is same, just to make sure that we don’t have any SQL compatibility issues.

60490-1

Open Reporting Services Configuration Manager Console and check the version of SQL Report Server

60490-2

Configuration of Report Server Database

Go to “Database” tab on ‘Reporting Services Configuration Manager Console’ NOTE If the Database is already created and configured at the time of SQL Reporting Service feature installation then skip this part (Database Configuration), else proceed accordingly for configuring the Report Server Database.

In my case the Database named “ReportServer_new” is already created and configured but I am proceeding with configuration of a New Database just so that you can see how this is done.

Click on ‘Change Database’

60490-3

Select “Create a new report server database” and click ‘Next’

60490-4

Provide the server name where the SCCM Database instance is hosted and click on ‘Next’

60490-5

Provide the name of Report Server Database you want to create. Here I have provided the name “ReportServer.”

60490-6

Provide the credentials as per your environment configuration. I suggest “Local System” as a good one to use.

60490-7

Click ‘Next’ to complete the configuration.

60490-8

Click ‘Finish’ to complete

60490-9

Once the Report Database is created you can verify the same by opening the SQL Management Console on the Site Database Server:

60490-10

Configuration of URLs

Go to “Web Service URL”. You will find that the URL is already created on Port:80 but is not active. To make it active click on “Apply”.

60490-11

Once you click on ‘Apply’, it will be Active and will appear like below:

60490-12

Go to “Report Manager URL” and do the same.

60490-13

Both URLs are Active now. Browse the ‘Web Service URL’ to make sure it is working.
60490-14

Installation of the Reporting Services Point role

Go ahead and add the ‘Reporting Service Point’ Role on the Server hosting SQL Reporting Services. In my case it’s the Primary Site Server.

60490-15
IMPORTANT While adding the role make sure that you specify the following:

  • “SCCM Site Database Server Name” at ‘Site Database Server Name’ (Example: PRI1.contoso.local)
  • “SCCM Site Database Name” at ‘Database Name’ (Example: CM_PRI)
  • “Reporting Service Instance Name” at ‘Reporting Services Server Instance’ (Example: MSSQLSERVER)
  • Set the “User Name” (Example: Contoso\Administrator)

Below is the screen shot for the same:

60490-16

Once the role is added you can verify the initiation of role installation and start of the Bootstrap Service in Sitecomp.log

Sitecomp.log

Starting bootstrap operations… SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:27:33 38092 (0x94CC)         Installed service SMS_SERVER_BOOTSTRAP_PRI1. SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:27:33 38092 (0x94CC)         Starting service SMS_SERVER_BOOTSTRAP_PRI1 with command-line arguments “PRI C:\Program Files\Microsoft Configuration Manager /install C:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe SMSSRSRP “… SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:27:33 38092 (0x94CC)           “C:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:PRI1.CONTOSO.LOCAL” executed successfully on server PRI1.CONTOSO.LOCAL. SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:28:09 38092 (0x94CC)         Bootstrap operation successful. SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:28:09 38092 (0x94CC)         Deinstalled service SMS_SERVER_BOOTSTRAP_PRI1. SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:28:09 38092 (0x94CC)       Bootstrap operations completed. SMS_SITE_COMPONENT_MANAGER 27-03-2017 17:28:09 38092 (0x94CC)

Verify that the role was added successfully by looking in SRSRPsetup.log

SRSRPSetup.log

<03/27/17 17:27:55> No versions of SMSSRSRP are installed.  Installing new SMSSRSRP. <03/27/17 17:27:55> Enabling MSI logging.  srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log <03/27/17 17:27:55> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR=”C:\Program Files\SMS_SRSRP” SRSRPLANGPACKFLAGS=0 <03/27/17 17:28:08> srsrp.msi exited with return code: 0 <03/27/17 17:28:08> Installation was successful. <03/27/17 17:28:08> Installation was successful.

Once the role installation is successful, look in the SRSRP.log and verify the HTTP URL you created. Also verify the SSRS Instance Version as well as the creation of the Source Folder and Data Source:

60490-17

Once all of the above things are verified and configured, it will start creating respective Folders of those reports and deploying Reports:

60490-18

Once all the reports are deployed it will check the SRS Web Service health and keep checking at regular intervals:

60490-20

Now you can go ahead and Run the Reports from ConfigMgr Console as well as from the URL directly.

Additional Information

Introduction to reporting in System Center Configuration Manager

How to: Start Reporting Services Configuration Manager

Configuring Reporting in Configuration Manager

 

rafid Rafid Ali, Support Engineer, Microsoft Enterprise Cloud Group