Monday, November 1, 2010

High-Level SCOM 2007 Install

  • Determine IP addresses and server names
    • server names CANNOT be changed once SCOM is installed
  • From the SCOM 2007 R2 media, run SetupOM.exe and click “Check Prerequisites”.
  • Choose what components will be installed on the machine (do this for each server)
  • Root Role Components – Server, Console , Power Shell, Web Console
  • Install .NET 2.0 and 3.0 Framework, Powershell, IIS and anything else it advises
  • Register the 64-bit version of ASP.NET (if installing on 64-bit OS)
  • Install 4 required Windows Server 2008 hot-fixes to support OpsMgr Server roles on Windows Server 2008 – 951327, 952664, 953290, 951116
  • Create five (5) service accounts and one (1) security group in Active Directory
    • sa_opsmgradmin
    • sa_sdkconfig
    • sa_mgmtsvraction
    • sa_datareader
    • sa_datawhwrite
  • Create a Security Group - sa_opsmgradmins > add sa_opsmgradmin & any other OpsMgr admins
  • On the SQL server & SCOM server(s), add the security group created above to the local administrators group
SQL Installation & Configuration

  • Install SQL Server – Reporting components and Tools (Management Studio)
    • Note: Reporting Services can be installed on any server if there is an issue with installing the SCOM Reporting component on the SQL Server
  • Install SQL SP3 (if SQL 2005), Install SQL SP1 (if SQL 2008) *Service Packs are included in the slip stream CD.
  • Take snapshot if virtual
  • Run Reporting Services Configuration Wizard (steps will vary slightly between SQL 2005 and 2008)
    • Wizard will create two DBs – ReportServer & ReportServerTemp and two virtual directories -
    • Select and create a web service URL > accept defaults > click apply
    • Select and create report manager URL, accept defaults, click apply
    • Confirm Report Server website is up and running – http://localhost/reportserver, http://localhost/reports (navagable from the server that Reporting Services is installed to)
    • Confirm Reporting services is configured correctly. Take a snapshot
  • Install OperationsManager database on SQL server (click “Install Operations Manager 2007 R2” from the media and select only the Operations Manager DB – not the Management Server, Web Console or any other options)
  • Set DB to autogrow – do this in the SQL Management Studio after the DB is created
  • Install OperationsManagerDW on SQL server (click “Install Operations Manager 2007 R2 Reporting” from the media and select only Operations Manager Datawarehouse – not the Reporting Server option)
  • Set DB to autogrow – do this in the SQL Management Studio after the DB is created
  • Add login in SQL MGMT Studio for sa_opsmgradmin - set default DB to OperationsManager (or you can run install as sa_sql)
    • Server Roles - public, sysadmin
    • User Mapping - public, dbowner (on OperationsManager)
  • From the SCOM 2007 R2 media, run SetupOM.exe and click “Check Prerequisites”.
SCOM Installation & Configuration

  • Install SCOM -
  • Install Management Server first (will become Root MS since it’s the first MS in the environment) Roles: Management Server, User Interfaces, Command Shell, Web Console
    • Update mommodules kb941811 if issues
  • If installing to default SQL Instance, use only server name when specifying SC Database Server Instance
  • Use Windows Auth if installing the Web Console
  • Confirm Health of Mgmt Group by opening the console
  • Take registry backup/snapshot if virtual
  • Import the Windows Server Core OS MP to get base metrics
    • Adminstration Console, Right-Click, Import Mgmt Packs
  • Install Reporting once it’s confirmed that the Management Group is healthy (optional)
  • Install Audit Collection Services once it’s confirmed that Reporting & the Management Group are healthy
  • Navigate to http:// \Reports_
  • Click on Audit Reports
  • Click Show Details in top right corner
  • Click DB Audit
  • Edit Connection String to point to the correct data source and catalog
  • Select “Credentials stored securely in the Report Server”
  • Use SQL Service Account
  • Check “use as windows credentials” when connecting to the data source”.
  • Open SQL Management Studio
  • Navigate to Security>Logins, Right Click Data Reader Service Account, Select Properties
  • Click User Mapping
  • Select “OperationsManagerAC”
  • Add “DB_Owner” and “Public” mappings
  • Click OK
  • If errors are still occurring for remote access. Try enabling Remote Errors (
  • Requires a new database to be created (best practice)
  • Requires ACS Reporting services to be installed
Best Practices
  • Enabled Network Adapter monitoring state (include Override Mgmt Pack)
Service Level Dashboard (Dundas Gauges)
  • Ensure sa_opsmgradmins group has local admin access

No comments:

Post a Comment