Install report server

Privacy policy. Depending on options you selected during installation, the Report Server might require additional configuration before you can use it. At a minimum, a report server configuration consists of the following:. Setup configures the minimum settings if you select either of the following installation options: Native mode default configuration or SharePoint integrated mode default configuration. If you installed the report server in files-only mode this is the Install but do not configure option in the Installation wizard , only the service account is configured.

It's recommended that you configure web portal so that you can grant user access to the report server and manage report server content. If you deploy a report server in SharePoint integrated mode, use the Web front end of a SharePoint server to grant access. Additional features, such as report server e-mail and the unattended execution account, can be configured as needed. Start the Reporting Services Configuration tool and connect to the report server instance. Additional features such as Power BI integration and e-mail delivery with subscription processing require additional configuration.

Setup installs the following Reporting Services features when you select the default configuration for native mode option:. Report Server service which includes the Report Server Web service, background processing application, and the web portal for viewing and managing reports as well as permissions.

Connection information, also known as the data source name DSN , for the report server databases. Setup does not configure the unattended execution account, report server e-mail, back up the encryption keys, or a scale-out deployment.

You can use the Reporting Services Configuration Manager to configure these properties. A default configuration installs Reporting Services in an operational state so that you can use the report server immediately after Setup is finished.

Specify this mode when you want to save steps by eliminating any required configuration tasks you would otherwise have to perform in the Reporting Services Configuration tool. Installing the default configuration does not guarantee that the report server will work after Setup is finished. The default URLs might not register when the service starts. Always test your installation to verify that the service starts and runs as expected.

See Verify a Reporting Services Installation. The default configuration option uses default values to configure the core settings required to make a report server operational. It has the following requirements:. The Database Engine instance hosts the report server database that Setup creates and configures.

The user account used to run Setup must be a member of the local Administrators group and have permission to access and create databases on the Database Engine instance that hosts the report server databases. Setup must be able to use the default values to reserve the URLs that provide access to the report server and the web portal. Setup must be able to use the default values to create the report server databases. If you have existing databases from a previous installation, Setup will be blocked because it cannot configure the report server in the default configuration for native mode.

Users in a different domain than the reporting services point account need a two-way trust between the domains to successfully run reports. The specified Windows user account and password are encrypted and stored in the Reporting Services database.

Reporting Services retrieves the data for reports from the site database by using this account and password. The account that you specify must have the Log on locally permission on the server that hosts the Reporting Services database. After the wizard completes, Configuration Manager creates the report folders in Reporting Services.

It then copies its reports to the specified report folders. To list only site systems that host the reporting services point site role, right-click Servers and Site System Roles , and select Reporting services point. When Configuration Manager creates report folders and copies reports to the report server, it determines the appropriate language for the objects.

When you install a reporting services point on a site without language packs, the reports are installed in English. If you install a language pack after you install the reporting services point, you must uninstall and reinstall the reporting services point for the reports to be available in the appropriate language pack language. For more information, see Language packs. Configuration Manager does the following actions to install the reporting services point and to configure Reporting Services:.

Typically, this account is the site server local System account. Create the data source in Reporting Services with the stored credentials that you specified in the wizard.

This account is the Windows user account and password that Reporting Services uses to connect to the site database when you run reports. Retrieve the mapping between report folders and Configuration Manager secured object types. Configuration Manager maintains this map in the site database. Configure the following rights for administrative users in Configuration Manager to specific report folders in Reporting Services:.

Add users and assign the ConfigMgr Report Users role to the associated report folder for administrative users who have Run Report permissions for the Configuration Manager object. Add users and assign the ConfigMgr Report Administrators role to the associated report folder for administrative users who have Modify Report permissions for the Configuration Manager object.

Configuration Manager connects to Reporting Services and sets the permissions for users on the Configuration Manager and Reporting Services root folders and specific report folders. After the initial installation of the reporting services point, Configuration Manager connects to Reporting Services every 10 minutes to verify that the user rights configured on the report folders are the associated rights that are set for Configuration Manager users.

When users are added or user rights are modified on the report folder by using Reporting Services Report Manager, Configuration Manager overwrites those changes by using the role-based assignments stored in the site database. Configuration Manager also removes users that don't have Reporting rights in Configuration Manager.

When Configuration Manager installs the reporting services point, it adds the following security roles in Reporting Services:. ConfigMgr Report Administrators : Users assigned with this security role can do all tasks related to reporting in Configuration Manager.

Verify the installation of the reporting services point by looking at specific status messages and log file entries. Use the following procedure to verify that the reporting services point installation was successful.

If you see reports in the Reports subfolder of the Reporting node in the Monitoring workspace in the Configuration Manager console, you can skip this procedure. Specify a date and time for a period before you installed the reporting services point, and then select OK. Verify status message ID This status message indicates that the reporting services point was successfully installed.

Open the Srsrp. Look for the string Installation was successful. Step through this log file starting from the time that the reporting services point was successfully installed. Verify that the report folders were created, the reports were deployed, and the security policy on each folder was confirmed.

After the last line of security policy confirmations, look for the string Successfully checked that the SRS web service is healthy on server. When you create or edit reports in the Configuration Manager console, Configuration Manager opens Report Builder to use as the authoring environment.

Regardless of how you author your Configuration Manager reports, you need a self-signed certificate for server authentication to the site database server. Configuration Manager automatically installs the certificate on the site server and any SMS Provider roles.

You can create or edit reports from the Configuration Manager console when you run it from one of these servers. When you create or modify reports from a Configuration Manager console on a different computer, export the certificate from the site server. The specific certificate's friendly name is the FQDN of the site server in the Trusted People certificate store for the local computer.