Skip to content

reporting-services-configuration-manager-native-mode.md

Latest commit

 

History

History
74 lines (48 loc) · 7.75 KB

reporting-services-configuration-manager-native-mode.md

File metadata and controls

74 lines (48 loc) · 7.75 KB
title What Is Report Server Configuration Manager (Native Mode)?
description Learn about the Report Server configuration manager so that you can configure a SQL Server Reporting Services (SSRS) installation in native mode.
ms.reviewer randolphwest
ms.date 01/07/2026
ms.service reporting-services
ms.subservice report-server
ms.topic overview
ms.custom
updatefrequency5
helpviewer_keywords
Reporting Services Configuration tool
configuration options [Reporting Services]
report servers [Reporting Services], configuring
components [Reporting Services], Reporting Services Configuration tool

What is the Report Server configuration manager (native mode)?

[!INCLUDE ssrs-appliesto] [!INCLUDE ssrs-appliesto-2016-and-later] [!INCLUDE ssrs-appliesto-pbirsi]

You can use the configuration manager in Power BI Report Server to configure a SQL Server [!INCLUDE ssRSnoversion] (SSRS) installation in native mode to perform the following tasks:

  • Configure the Report Server service account: You configure this account during setup. If you update the password or want to use a different account, you can modify it by using the Report Server configuration manager.

  • Create and configure URLs: The report server and the [!INCLUDE ssRSWebPortal] are [!INCLUDE vstecasp] applications that you access through URLs. The report server URL provides access to the SOAP endpoints of the report server. The [!INCLUDE ssRSWebPortal] URL opens the [!INCLUDE ssRSWebPortal]. Use the Report Server configuration manager to configure a single URL or multiple URLs for each application.

  • Create and configure the report server database: The report server is a stateless server that requires a [!INCLUDE ssNoVersion] database for internal storage. Use the Report Server configuration manager to create and configure a connection to the report server database. You can select an existing report server database that already contains the content that you want to use.

  • Configure a scale-out deployment in native mode: [!INCLUDE ssRSnoversion] supports a deployment topology that allows multiple report server instances to use a single, shared report server database. To deploy a report server scale-out deployment, use the Report Server configuration manager to connect each report server to the shared report server database.

  • Back up, restore, or replace the symmetric key: A symmetric key encrypts stored connection strings and credentials. You need a backup of the symmetric key if you change the service account or move a report server database to another computer.

  • Configure the unattended execution account: This account enables remote connections during scheduled operations or when user credentials aren't available.

  • Configure the report server email: [!INCLUDE ssRSnoversion] includes a report server email delivery extension that uses Simple Mail Transfer Protocol (SMTP) to deliver reports or report processing notifications to an electronic mailbox. Use the [!INCLUDE ssRSnoversion] configuration manager to specify which SMTP server or gateway on your network to use for email delivery.

To fully deploy, you need to use [!INCLUDE ssNoVersion] [!INCLUDE ssManStudio] to enable other features or modify default values. You can also use the web portal to grant access to the server. For more information about the report server, see Configure and administer a report server (SSRS native mode).

Note

Reporting Services integration with SharePoint is no longer available in SQL Server versions 2016 and newer. From the [!INCLUDE ssSQL11] release and newer, the [!INCLUDE ssRSnoversion] configuration manager isn't designed to manage SharePoint mode report servers. You manage and configure SharePoint mode by using SharePoint Central Administration and PowerShell scripts.

Versions of Reporting Services

The Report Server configuration manager is version-specific. You can't use the Report Server configuration manager that's installed with this version of [!INCLUDE ssNoVersion] to configure an earlier version of [!INCLUDE ssRSnoversion]. If you're running both older and newer versions of [!INCLUDE ssRSnoversion] side-by-side on the same computer, you must use the Report Server configuration manager that comes with each version to configure each instance.

Get started

  1. Ensure that your system and permissions are set up correctly. For more information, see Hardware and software requirements for SQL Server 2016 and SQL Server 2017.

  2. To start the Report Server configuration manager, go to the Windows Start menu and enter Report Server. Select Report Server Configuration Manager from the search results.

    Alternately, depending on your version of Microsoft Windows, you can select Start and go to All Programs. Go to [!INCLUDE ssCurrentUI] Reporting Services, and select Report Server Configuration Manager.

    To configure a report server instance from a previous version of [!INCLUDE ssNoVersion], open the program folder for that version. For example, go to [!INCLUDE ssSQL14] instead of [!INCLUDE ssCurrentUI] to open the configuration tools for [!INCLUDE ssSQL14] server components and select Report Server Configuration Manager.

  3. In Server Name, specify the name of the computer where the report server instance is installed. The name of the local computer appears by default. To connect to a report server installed on a remote computer, enter the name of a remote [!INCLUDE ssNoVersion] instance.

  4. If you specify a remote computer, select Find to establish a connection.

  5. In Report Server Instance, select the report server instance that you want to configure. Only report server instances for the specified version of [!INCLUDE ssNoVersion] appear in the list. You can't configure earlier versions of [!INCLUDE ssRSnoversion].

  6. Select Connect.

Related content