Default Configuration for a Report Server Installation
When you use the SQL Server Installation Wizard to install the report server component of Reporting Services, Setup provides an option for installing the server in a default configuration. This installation option installs and deploys a report server. When Setup is finished, the report server is running and ready to use. In the Installation Wizard, the option name is Install the default configuration. In a command line setup, the default configuration is specified through the DEFAULT setting for the RSCONFIGURATION property.
Requirements
The default configuration installation option comes with a number of requirements and restrictions, described as follows:
- A local instance of the SQL Server Database Engine must be used to host the report server database. The Database Engine must be installed concurrently with the report server instance.
- The user account used to run Setup must have permission to access and create databases using the local Database Engine instance.
- The default Web site or application pool must be enabled in Microsoft Internet Information Services (IIS), and its Internet Protocol (IP) address must be mapped to (all unassigned). The report server and Report Manager virtual directories will be created in the default Web site.
- The default Web site cannot be configured for Secure Sockets Layer (SSL) connections.
- ASP.NET must be running under the default ASP.NET account. The report server Web service uses the ASP.NET account. On Windows Server 2003, the default ASP.NET account is Network Service. On a Windows 2000 server, the default ASP.NET account is a least-privileged account created specifically for the ASP.NET worker process. If ASP.NET is running under a non-default account, Setup cannot install the default configuration.
- The IWAM_computername account must be enabled before you run Setup. Setup uses this account to configure IIS.
Default Configuration Settings
The following table compares the settings used in a default configuration with those used in a files-only installation. Except for the Microsoft Windows service account, you cannot specify values in a default configuration during Setup.
| Operation | Default Configuration | Files-Only Installation |
|---|---|---|
Configures instance name |
Uses the SQL Server instance name |
Uses the SQL Server instance name |
Installs files |
Yes |
Yes |
Configures Web service account |
For Windows XP and Windows 2000, Setup uses the ASP.Net machine account or the Network Service account in machine.config. If the value is not one of these, default setup cannot be used. On Windows Server 2003, Setup uses the account associated with the application pool used with the default Web site. |
No |
Configures Windows service |
Uses the values specified in the Service Accounts page in the Installation Wizard. For Windows XP and Windows 2000, the default is Local System. For Windows Server 2003, the default is Network Service. |
Uses the values specified in the Service Accounts page in the Installation Wizard. |
Sets folder permissions |
Grants permission to the Web service account and Windows service account. |
Grants permission to the Windows service account. |
Creates report server database |
Yes. Creates the reportserver and reportservertempdb databases. |
No |
Configures a database connection |
Yes. The Web service account and Windows service account are granted rights to the database through the rsexecrole. |
No |
Creates virtual directories |
Yes. The virtual directories are created on the default Web site with default names determined by the instance name. |
No |
Configures e-mail delivery |
No |
No |
Registers the Report Server WMI provider |
Yes |
Yes |
Starts the Report Server Windows service |
Yes, if Auto-start service is specified and no setup errors occur. |
No |
Initializes the report server |
Yes |
No |
See Also
Reference
Report Server Installation Options
Concepts
Installing SQL Server Reporting Services
Installing Reporting Services Using Setup