6.5.5 SQL Server Reporting Services
Rebind existing SSRS HTTPS endpoints through the ReportServer WMI provider
The SQL Server Reporting Services (SSRS) template replaces the certificate on existing Report Server HTTPS bindings. It supports SSRS 2016 and later and Power BI Report Server.
Configure HTTPS once first
HTTPS must already be configured in Report Server Configuration Manager. The template preserves and renews existing bindings; it does not create the initial Web Service or Web Portal HTTPS configuration.
If the deployment reports “No SSRS SSL bindings found”, configure HTTPS on the selected port in Report Server Configuration Manager and retry.
Instance name
Set Report Server instance name to the instance shown in Report Server Configuration Manager:
| Product | Common instance name |
|---|---|
| SSRS 2017 and later | SSRS |
| SSRS 2016 and earlier | SQL instance name, commonly MSSQLSERVER |
| Power BI Report Server | PBIRS |
The template selects the newest ReportServer WMI version namespace below that instance. An incorrect instance name produces a “Could not find SSRS WMI version namespace” error.
Binding replacement
Set HTTPS port to the port used by the current Report Server bindings. The template snapshots every SSRS binding on that port, removes each old binding, and recreates it with the new thumbprint. This covers both the Web Service and Web Portal when they share the port.
The template then restarts the Reporting Services or Power BI Report Server service. Use a deployment window when a short reporting outage is not acceptable.
For a product overview, see certificate automation for SQL Server Reporting Services.