Default Configuration for a Native Mode Installation (Reporting Services)

Default configuration for native mode refers to a Reporting Services installation where Setup both installs and configures a report server instance. After Setup is finished, the report server is running and ready to use. A native mode report server runs as a stand-alone application server. Native mode is the default mode.

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 Report Manager), Report Builder, Report Designer Preview, the Reporting Services Configuration tool, and the Reporting Services command line utilities (rsconfig.exe, rskeymgmt.exe and rs.exe). This option does not apply to shared features such as SQL Server Management Studio or Business Intelligence Development Studio, which must be specified as separate items if you want to install them.

Setup configures the following for a native mode report server installation:

  • Service account for the Report Server service.

  • Report Server Web service URL.

  • Report Manager URL.

  • Report Server database.

  • Service account access to the report server databases.

  • DSN connection 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 tool to configure these properties. For more information, see Reporting Services Configuration Tool.

When to Install the Default Configuration for Native Mode

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.


This installation option uses default values to configure the core settings required to make a report server operational. It has the following requirements:

  • Reporting Services and SQL Server Database Engine must be installed together in the same instance. 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 Report Manager. These values are port 80, a strong wildcard, and the virtual directory names in the format ReportServer_<instance_name> and Reports_<instance_name>.

  • Setup must be able to use the default values to create the report server databases. These values are ReportServer and ReportServerTempDB. 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. You must rename, move, or delete the databases to unblock Setup.

If your computer does not meet all requirements for a default installation, you must install Reporting Services in files-only mode and then use the Reporting Services Configuration tool to configure it after Setup is finished.

Do not try to reconfigure your computer only to allow a default installation to continue. Doing so could require several hours of work, effectively eliminating the time-saving benefit the installation option provides. The best solution is to install Reporting Services in files-only mode and then configure the report server to use specific values.

Default URL Reservations

URL reservations are composed of a prefix, host name, port, and virtual directory:




The default prefix is HTTP. If you previously installed a Secure Sockets Layer (SSL) certificate, Setup will try to create URL reservations that use the HTTPS prefix.

Host name

The default host name is a strong wildcard (+). It specifies that the report server will accept any HTTP request on the designated port for any host name that resolves to the computer, including http://<computername>/reportserver, http://localhost/reportserver, or http://<IPAddress>/reportserver.


The default port is 80. If you install Reporting Services on 32-bit Windows XP SP2, the default port is 8080. Note that if you use any port other than port 80, you will have to explicitly add it to the URL when you open a Reporting Services Web application in a browser window.

Virtual directory

By default, virtual directories are created in the format of ReportServer_<instance_name> for the Report Server Web service and Reports_<instance_name> for Report Manager. For the Report Server Web service, the default virtual directory is reportserver. For Report Manager, the default virtual directory is reports.

An example of the complete URL string might be as follows:

How to Install a Report Server in the Default Configuration for Native Mode

You can specify a native mode default configuration through the command line or in the Installation wizard. The following topics provide step-by-step instructions:

Example Command Line Script

The following example includes the Database Engine Service because it is required for a default configuration.


Installation Wizard

When you select Reporting Services in the Feature Selection page, Setup provides a Reporting Services Configuration page that allows you to specify the installation mode. To specify a default native mode installation, select Install the Native mode default configuration on the Reporting Services Configuration page.