Installing SQL Server Reporting Services
-Building the foundation for a solid Reporting Services instance.
-Second step in the process is Reporting Services to conform to the particulars of your environment.
These configurations are made to the RS Server.config file via the Reporting Services Configuration Tool. This tool is quite similar in concept and practice to the Surface Area Configuration Tool that is utilized to configure the SQL Server Database Services instance post-install.
-Issuing a Certificate and Enrolling it on Report Server.
-Configuration of the Report Database and URLs
-Installation of the Reporting Services Point role.
Issuing a Certificate and Enrolling it on Report Server
Configuration of the Report Database and URLs
Open the “Reporting Services Configuration Manager” by connecting to the correct Instance. Verify that the version of ‘Reporting Service Instance’ is the same as ‘SCCM Database Instance’. If not, upgrade the Reporting Service Instance first.
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”.
“Report Manager URL”:
Next select “Database”.
NOTE: If the Database is already created and configured then skip this part (Database Configuration), else proceed accordingly for configuring the Report Server Database.
Database named “ReportServer_New” is already created and configured but you have to proceed with configuration of a New Database.
Select “Create a new report server database”:
Provide the server name where the SCCM Database instance is hosted:
Provide the name of Report Server Database you want to create. Here I have provided the name “ReportServer”:
Provide the credentials as per your environment configuration. I suggest “Local System” as a good one to use.
Click on finish button
Report Database is created you can verify the same by opening the SQL Management Console on the Site Database Server:
NOTE You can also verify the version of ‘SQL Instance’ on which the SCCM Site Database is hosted and compare it with ‘SQL Reporting Services Instance’ hosted on the Report Server.
Now go back to “Web Service URL” to configure it for HTTPS. Click on “Advanced..”:
Remove the TCP Port 80 (HTTP) identity and add the SSL identity by clicking on “Add”:
Desired to gain proficiency on SSRS?
Explore the blog post on SSRS training to become a pro in SSRS.
SSL Port 443 will be already selected. Select the Web Server certificate we previously enrolled:
Create the required HTTPS URL automatically that you can verify here:
Click OK to finish the Web Service URL configuration:
Click on the URL to verify that its running and verify that it’s connecting via HTTPS:
Now do the same for Report Manager URL:
Installation of the Reporting Services Point role
Add the Reporting Service role on the Report Server hosting the SQL Reporting Services.
While adding the role make sure that you specify the following:
-“SCCM Site Database Server Name” at ‘Site Database Server Name’ (Example: PRI.contoso.com)
-“SCCM Site Database Name” at ‘Database Name’ (Example: CM_MUM)
-“Reporting Service Instance Name” at ‘Reporting Services Server Instance’ (Example: MSSQLSERVER)
-Set the “User Name
Now, verify the initiation of role installation and start of the Bootstrap Service in Sitecomp.log. Do this by looking at the Site System name (i.e. Report Server):
Verify that the role was added successfully by looking in SRSRPsetup.log on the Site System (located at \\<Drive>\SMS\Logs):
Verify the SSRS Instance Version as well as the creation of the Source Folder and Data Source:
All of the above things are verified and configured, it will start deploying Reports and creating respective folders of those reports:
All the reports deployed successfully, you can verify the URLs in the ConfigMgr 2012 console as well:
Start running the reports from the ConfigMgr 2012 console using HTTPS mode by using the HTTPS URL.
For indepth understanding click on