Let’s learn to Install ConfigMgr SSRS Reporting Services Point. We can make beautiful reports with the data collected by the Configuration Manager. SCCM has 500+ default reports those are available out of the box and ready to use.
Before you can view or manage reports from the admin console, you need a reporting services point. Reporting Services connects to the Configuration Manager site DB to retrieve data that is returned when you run reports.
SQL Server Reporting Services (SSRS) is one of the requirements for the SCCM CB reporting services point. The SQL reporting service is part of SQL Server installation. You can refer to SQL installation and SQL reporting service role installation details from the previous blog posts.
Reporting in ConfigMgr has the following dependencies:
- SQL Server Reporting Services
- Reporting services point
- Optional – Power BI Report Server
- .NET Framework 4.8
- SQL Server Native Client
- Other details here.
It’s not recommended to change the reporting server URL. This change can create issues when you try to access reports from the admin console.
You also need to have appropriate SCCM permission to install the site system role.
The user account you use to create the reporting services point must have Read access to the site database.
The current user must have Read access to WMI on the site system.
The account that you specify must have the Log on locally permission on the server that hosts the Reporting Services database. This is for the Reporting services point account mentioned in the below section.
Install Reporting Services Point
Let’s see how to install reporting service points.
- Launch admin console.
- Navigate to \Administration\Overview\Site Configuration\Servers and Site System Roles.
- Right-click on the SQL server where I’m planning to install Reporting service point.
- Select Add Site System Roles.
- Use the site server’s computer account to install the site system if the site server and site system servers are in the same domain and
- your site server account should be added to the local administrator’s group on the remote site system servers.
If the servers are not in the same domain and don’t have a two-way trust, try to use the next option – “Use another account for installing this site system“.
Click on the Next button.
Click on the Next button from Specify Internet Proxy Server page.
Click on Reporting Services Point.
Click on the Next button.
NOTE! – Reporting services server instance should automatically get detected. If the reporting service is not showing up by default, then you need to perform some troubleshooting with SQL Server Reporting Services Configuration Manager from the Start menu. Also, check the permissions section to get more details.
Click on the Verify button to confirm Site Database connection settings.
Normally Site Database server name, Database name, Folder Name, and Reporting services server instance will get automatically populated.
Select the Reporting Services Point Account – Specify the credentials that SQL reporting Services will use when connecting to the Configuration Manager site database.
Select the service account by clicking on the Set button.
The permission section above should be taken care and as per that guidance use the appropriate permission.
Click Next, Next, and Close.
SSRS Reporting Point Log files
Let’s check the SCCM Reporting Services point. If you are installing SCCM Reporting services point on the remote server, then the log files will be located in C:\SMS\Logs\.
Let’s see whether the SSRS reports are available or not.
Launch Admin console. Navigate to \Monitoring\Overview\Reporting\Reports. Launch any particular report from the console itself.
Anoop is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.