In my post two days ago on silently installing SQL Server 2017 Reporting Services (SSRS 2017), I just provided the most basic information on configuration. In fact, after installing SSRS 2017, it will be completely unconfigured. Configuration can be done using the Reporting Service Configuration Manager GUI. In my case, the configuration needs to be automated, so I use PowerShell.
I have posted my complete PowerShell script for configuration of SSRS 2017 to a GitHub Gist. It’s embedded below. The script itself has comments that will hopefully allow you to follow the flow, but here is a quick overview of the different steps:
- Get a WMI object with the configuration settings for the SSRS 2017 instance.
- Get a SQL script to create the ReportServer and ReportServerTempDB databases.
- Establish a connection to the default SQL Server instance on the same machine.
- Execute the SQL script.
- Get and execute a second SQL script, this time to set the permissions for the SSRS 2017 service account.
- Set the SSRS database connection to this newly created database.
- Configure the virtual directory name and URL of the web service.
- Configure the virtual directory name and URL of the report manager web app.
- Initialize the report server with encryption for sensitive data.
- Restart the service.
- Output the new configuration.
Note: I expect this script will also work with SQL Server 2016 Reporting Services. It will not work with earlier versions without changing the name of the Report Manager web application to ReportManager.