Detent Point

SqlCertForge TLS certificate binding for SQL Server and Reporting Services

Get-RsHttpConfig

Inventories everything Reporting Services owns in the Windows HTTP layer — reserved URLs, SSL certificate bindings, and the real browseable URLs — in one r...

Domain: SSRS / PBIRS · Risk: Read-only · Runs on: Windows, PowerShell 5.1 or 7

This answers “what does this report server currently expose, and with which certificate?” in a single command, without changing anything. It replaces squinting at raw netsh output. It’s in the free, read-only tier, so it’s the natural starting point for auditing an estate before any work is planned.

Returns, in one read: reserved URLs (ListReservedUrls, including strong-wildcard + forms), SSL certificate bindings (ListSSLCertificateBindings — which thumbprint is bound to which application/IP/port), and registered URLs (GetReportServerUrls, with + resolved to real host names). Replaces eyeballing netsh http show urlacl / show sslcert. Never throws.

Recipe 01 — Inventory the local PBIRS instance

Get-RsHttpConfig -RsInstance 'PBIRS'

Lists every reserved URL, SSL binding, and registered URL.

Recipe 02 — Inventory a remote SSRS server

Get-RsHttpConfig -RsInstance 'SSRS' -ComputerName RS01 -Credential $cred

Recipe 03 — Pull just the SSL bindings for a report

(Get-RsHttpConfig -RsInstance 'SSRS').Data.SslBindings |
    Format-Table Application, CertificateHash, IPAddress, Port

Reporting Services keeps three related lists in Windows: the addresses it has reserved, which certificate is attached to each, and the actual URLs a browser would use. Reading these by hand means parsing cryptic netsh output.

This command gathers all three into one tidy result, so you can see at a glance what the report server exposes and which certificate secures it — a safe look with no changes.

Question Answer
Outbound calls? None. WMI reads on the local (or named) RS server.
What it changes Nothing — read-only.
Privileges RS admin (read); WinRM for remote.
Licence Free. Read-only inventory needs no licence.
Dependency Why Required?
SSRS 2016+ or PBIRS The service being inspected. Yes
WinRM to remote nodes Only for remote reads. No (local)
  • A non-mutating inventory of the report server’s HTTP surface — reserved URLs, bound certificate thumbprints, and live URLs — ideal for a compliance sweep.
  • Surfaces exactly which certificate secures each endpoint, so an auditor can confirm it against policy.
  • Free to run across an estate, so coverage isn’t gated by licensing.