OpsMgr 2007: How to make your Reporting install a success
The MOMTeam blog just posted a great list of prerequisites that will help ensure that Reporting installs successfully. Before you install Reporting you'll want to give this a quick read:
Detailed below are some validation steps that should be completed before attempting to install Operations Manager 2007 Reporting.
During this installation, you are prompted for two accounts: the Data Warehouse Write account and the Data Reader account. These accounts are created as domain user accounts and added to the local Administrators group on the target server.
· Data Warehouse Write account: This account is assigned write permissions on the Data Warehouse database and read permissions on the OperationsManager database.
· Data Reader account: This account is used to define what user SQL Reporting Services uses to run queries against the Operations Manager Reporting Data Warehouse. This account is also used for the SQL Reporting Services IIS application pool account to connect to the RMS.
Before you perform this procedure, be sure that the account you plan to use for the Data Warehouse Write Account has SQL Login rights and is an Administrator on the computers hosting both the Operations Manager database and Reporting data warehouse. Otherwise, setup fails and all changes are rolled back, which might leave SQL Reporting Services in an inoperable state.
All permissions are shown below:
- Make sure the user running setup has following permissions
- User is local administrator (Needed to run MSI, to configure SSRS)
- User is Ops Manager Administrator (Needed to configure Reporting roles, creating instances)
- User is SysAdmin in Ops DB (Needed to configure dwsynch_users role)
- User is SysAdmin in DW DB (Needed to configure OpsMgrWriter, OpsMgrReader roles)
J.C. Hornbeck | Manageability Knowledge Engineer