
System Center Operations Manager 2007 Reporting Server Installation on Windows Server 2008 Guide for Operations Manager 2007
Microsoft Corporation
Published: October 2008
Author
Matthew J. Goedtel
Feedback
Send suggestions and comments about this document to mgoedtel@microsoft.com. Please include the document name with your feedback.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Revision History
|
Release Date |
Changes |
|
October , 2008 |
Original release of this guide |
|
October, 2008 |
Updated document to correct steps for enabling IIS Script Execution. |
Contents
This document provides deployment guidance for installing and configuring Microsoft System Center Operations Manager 2007 Reporting Server component on Windows Server 2008.
This section outlines the minimum software requirements that you must have for the Operations Manager Reporting component beyond the operating system.
Important
Verify that all appropriate security updates, hotfixes, and service packs have been applied to the operating system and to applications that are required for deploying Operations Manager components. You can do by visiting the Windows Update website at http://go.microsoft.com/fwlink/?LinkId=1623.
In addition to a supported operating system, you must have the following software:
n SQL Server 2005™ Standard or Enterprise Edition with Service Pack 2 and SQL Server Reporting Services component installed
n .NET Framework 3.0
n IIS 7.0 with ASP.NET enabled
n If you intend on installing the Operations Manager agent to monitor the Reporting Server, you will need to install the following hotfixes required for Operations Manager agent support on Windows Server 2008:
n 951327
n 952664
n 953290
The following steps are necessary before proceeding with the installation and configuration of SQL Server 2005 with Reporting Services.
1. Log onto Windows Server 2008.
2. Configure a server role and enable ASP.NET and IIS. To do this, perform the following steps:
a. Click Start, and then click Server Manager.
b. In Server Manager, right-click Manage Roles, and then click Add roles. The Add Roles Wizard starts.
c. In the Add Roles Wizard, click Select Server Roles.
d. On the Select Server Roles page, click to select the Web Server (IIS) check box, and then click Next.
Note: Because of role dependency, the File Server check box is automatically selected when you click to select the Web Server (IIS) check box.
e. On the Role Services page, expand Common HTTP Features, and then click to select the following check boxes:
n Static Content
n Default Document
n Directory Browsing
n HTTP Errors
n HTTP Redirection
f. Expand Application Development, and then click to select ASP.NET check box.
g. Expand Security, and then click to select the Windows Authentication check box.
h. Expand Management Tools, expand IIS 6 Management Capability, and then click to select the following check boxes:
n IIS Metabase Compatibility
n IIS 6 WMI Compatibility
n IIS 6 Scripting Tools
n IIS 6 Management Console
i. Click Next, and then click Install.
Note: If you do not enable these features, the Reporting Services option does not appear in the Feature Selection dialog box of the SQL Server Setup program.
3. Verify that the World Wide Web Publishing service is started. If the World Wide Web Publishing service is not started, configure the service to start automatically. To do this, follow these steps:
a. In Control Panel, click System and Maintenance.
b. Click Administrative Tools.
c. Double-click Services.
d. In the User Account Control dialog box, click Continue.
e. Right-click World Wide Web Publishing Service, and then click Properties.
f. In the World Wide Web Publishing Service Properties dialog box, select Automatic in the Startup Type list.
g. Click Apply, click Start, and then click OK.
The following steps are required to install SQL Server 2005 with Reporting Services. It is recommended that you use the slipstreamed version of SQL Server 2005 with Service Pack 2 instead of installing the RTM version first, and then applying the Service Pack 2 update.
Notes:
n When you install the release version of SQL Server 2005, you receive a warning message. The warning message explains that this program has known compatibility issues. Click Run program to continue the installation.
n In the Features Section dialog box, make sure that Reporting Services is selected.
n In the Report Server Installation Options dialog box, select one of the following options:
n Install the default configuration
n Install but do not configure the server
Note: If you select the Install but do not configure the server option, you can manually configure the report server after the installation has finished. However, you may experience problems when you manually configure the report server. For troubleshooting help, please see Knowledge Base Article 938245.
Once you have successfully installed SQL Server 2005 SP2 with Reporting Services, verify the SQL Server services are started before moving onto the next section.
The following steps are required to ensure Operations Manager Reporting Server operates correctly.
1.
Open
IIS Manager.
2.
Expand
the tree until you can select Application
Pools.
3.
Right-click
the ReportServer$Instance Pool and
select Advanced Settings.
4.
Select
Identity under Process Model, click
the browse (…) button.
5.
In
the Application Pool Identity window, select LocalSystem from the Built-in account list box. Press OK twice.
1. Click Start, click Run, type inetmgr, and then click OK.
2. In the Internet Information Services (IIS) Manager, expand Web Sites, expand Default Web Site, and then click the virtual directory for the report server (by default this is ReportServer$Instance1)
3. Under the Features View, double-click Handler Mappings.
4. Highlight ISAPI-dll, right-click and select Edit Feature Permissions
5. Click to select the Scripts check box, and then click OK.
1. Click Start, point to All Programs, right-click Internet Explorer, and then click Run as administrator.
2. In the User Account Control dialog box, click Continue.
3. Open Report Manager. By default, the URL of Report Manager is the following:
If you used a named instance of Reporting Services, the URL of the Report Manager is the following:
http://ServerName/reports$InstanceName
When the page renders, you should see the Home page appear empty without any error messages. After you have verified Report Manager is running correctly, proceed with the normal steps of installing Operations Manager 2007 with Service Pack 1 Reporting feature. For more information on the steps required, please see How to Deploy Reporting in Operations Manager 2007 in the Operations Manager 2007 Online Help.
If the page does not render correctly and you are receiving errors, please review Knowledge Base Article 938245 for additional details.