Server Deployment Checklist
This topic describes steps for deploying a report server. These steps identify the decisions you must make and the information you need to complete server deployment. Following these steps can help you avoid errors that occur when a system is not properly configured or fully deployed.
Before You Install
Before you run Setup, you must have a Web server, a SQL Server instance, and several accounts that can be used by Report Server services. The computers you choose must satisfy minimum software and hardware requirements. For more information, see Hardware Requirements for Reporting Services and Software Requirements for Reporting Services.
- Decide on a Web server to host the report server. It can be any server that runs Internet Information Services (IIS) 5.0 or later. If you have one that is already configured for Web applications and it meets the minimum memory requirements, you can use it. If you choose a Web server that is hosting other server-based Web applications, additional testing and configuration may be required to ensure that the applications operate correctly with each other on the same server. For example, if you are running Windows SharePoint Services and Reporting Services on the same Web server, you must perform additional steps to complete a Reporting Services deployment. For more information, see the readme.
- Verify that the Web server is configured to use the .NET Framework version 1.1.4322. You can do this by examining the application configuration properties of the default Web site:
- In Internet Information Services, right-click Default Web Site and click Properties.
- Click Home Directory, and then click Configuration.
- Find .asax in the list of application mappings. The value in the executable path for .asax (and for other ASP.NET file extensions) should be %Windows%\MicrosoftNET\Framework\v1.1.4322.
- Decide on a SQL Server instance to host the report server database. You can use a local or remote SQL Server instance. You should choose an instance that is on a computer that has the storage capacity to accommodate your reports. For more information about the disk space requirements, see Report Server Database Requirements.
- Verify that the instance of SQL Server that hosts the report server database is physically secure. A malicious user who gains access to the report server database with permission to change the content or modify the schema is a serious security risk. To reduce this threat, ensure that the SQL Server instance hosting the report server database is physically secure from intruders.
- Decide which accounts to use for Report Server services. Reporting Services requires three accounts:
- Report Server Windows service requires an account to log on to the local system. Microsoft recommends that you use Local System if you are installing on Windows 2000. For more information about this recommendation, see Service Account.
- Report Server Web service requires an account to log on to the local system. Because it is an ASP.NET application, it runs using the ASPNET account. If you are running Windows 2000, you cannot specify a different account to use during Setup; you must use the account that is defined for ASP.NET. If you are running Windows Server 2003, the default is Network Service, but you can choose to run the service as Local System.
- Report Server Web service requires an account to log on to the SQL Server instance that hosts the report server database. You can specify a domain account, a SQL Server login, or Local System. You can also use the credentials that the Report Server Web service uses to log on to the system. For more information, see Report Server Database Setup.
- (Optional.) Find the name of the SMTP server that provides e-mail service to your organization. If you know the name of your SMTP server and a valid account to use, you can configure a report server to support e-mail report distribution during Setup. You can also perform these steps after Setup if you do not have an SMTP server immediately available. For more information, see Configuring a Report Server for E-Mail Delivery.
After you have decided on which servers to use and know which accounts you want to specify for each service, you are ready to run Setup. You run Setup on the Web server that hosts the Reporting Services server-side components. For more information about running Setup, see Installing Reporting Services.
After Setup Completes
Perform the following tasks after Setup is finished to complete the deployment:
- Install Oracle client tools on the report server if your reports use the Microsoft .NET Framework Data Provider for Oracle. After you install the client tools, you must restart IIS.
- (Optional.) Create entries for multiple domain name servers that can be used by the Report Scheduling and Delivery Processor in the event of a denial of service attack on an external server (such as an e-mail server) that is the recipient of report delivery. This step is not required, but it mitigates a possible security threat by providing a report server with an alternative way of delivering reports if the primary DNS server is unavailable.
- Verify that SQL Agent is running on the SQL Server instance that is hosting the report server database. SQL Agent must be running before users define subscriptions and other scheduled operations.
- Back up the symmetric key that supports encryption on a report server. For more information, see Managing Encryption Keys.
- Ping the Report Server Web service to make sure it is running. In a browser window, type http://localhost/reportserver.
- If you are using IIS 6.0 to host the report server, verify that the Web server name is a trusted site. Otherwise, certain pages in Report Manager will not open correctly.
- Use Report Manager to enable features and server access:
- In a browser window, type http://localhost/reports. This is the virtual directory for Report Manager.
- Click Site Settings to open the Site Settings page. You can set options to enable features and set maximum limits. For more information about the options, click Help.
- Click Configure site-wide security, and then click New Role Assignment.
- Type the name of group account for which you want to grant access to the report server. For widespread access, you can specify Everyone (a built-in IIS account) or Users (a built-in Windows domain account).
- Select System User, and then click OK.
- Click Home, click Properties, and then click New Role Assignment.
- Type the name of the group account you specified in step d.
- Select Browser, and then click OK.
The last set of steps that you perform in Report Manager result in role assignments that allow report users to access a report server. A new installation of Reporting Services grants report server access to local administrators only. Local administrator access is defined through a default role assignment that is created during Setup. Only users who are members of the built-in Administrators group have automatic access to a report server. To make a report server available to other users, you must create two role assignments (one for system-level access and one for item-level access).
Consider creating more role assignments if you want to support additional levels of access (for example, report authors who publish reports to a report server should have Publisher rights to the report server). Role assignments control all access to a report server, so it is important that you understand how to create and manage role assignments on your system. For more information, see Using Role-Based Security and Predefined Role Assignments.