Scribd
Upload
2 views

02 Installing SCOM

The document outlines the installation process for System Center Operations Manager (SCOM), detailing prerequisites, hardware and software requirements, and account configurations. It describes the roles of various accounts such as Action, SDK and Config Service, Data Warehouse Write, and Data Reader accounts in the monitoring process. Verification steps post-installation are also provided to ensure successful setup.

Uploaded by

shrikantnpar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
2 views

02 Installing SCOM

The document outlines the installation process for System Center Operations Manager (SCOM), detailing prerequisites, hardware and software requirements, and account configurations. It describes the roles of various accounts such as Action, SDK and Config Service, Data Warehouse Write, and Data Reader accounts in the monitoring process. Verification steps post-installation are also provided to ensure successful setup.

Uploaded by

shrikantnpar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 18

Installing SCOM

Overview
• Installing Pre Requisites
– Hardware and Software
• Installing the RMS
– Accounts
– Extending the Schema
– Pre req Checker
– Installing the database and RMS
– Verifying
Hardware and Supported
Configurations
• Please give detail information by using
document
Software Requirement
• Windows Server 2003/2008
• SQL Standard 2005 sp2
• Active Directory and DNS
• Certificate ( Optional)
• User Accounts ( lots of accounts)
SCOM Accounts
• Action
• Runas
• SDK and Config Service
• Dataware house write
• Data Reader
Action

• The various Operations Manager 2007 server


roles, root management server, management
server, gateway server and agent, all contain a
process called MonitoringHost.exe.
• MonitoringHost.exe is what each server role
uses to accomplish monitoring activities, such
as executing a monitor or running a task.
Action
• For example, when an agent subscribes to the event log to read events, it is the
MonitoringHost.exe process that runs those activities. The account that a
MonitoringHost.exe process runs as is called the action account. The action account for the
MonitoringHost.exe process running on an agent is called the agent action account. The
action account used by the MonitoringHost.exe process on a management server is called
the Management Server action account. The action account used by the MonitoringHost.exe
process on a gateway server is called the gateway server action account.
SDK and Config Service Account

• The SDK and Config Service account is one set of credentials that is used
by the OpsMgr SDK Service and OpsMgr Config Service to update and read
information in the Operations Manager database. Operations Manager
ensures that the credentials used for the SDK and Configuration action
account will be assigned to the sdk_user role in the Operations Manager
database
SDK and Config Service Account

• The SDK and Config Service account can be configured as either Local
System or as a domain account. A Local User account is not supported.
• If the root management server and the Operations Manager database are
on different computers, the SDK and Config Service account will need to
be changed to a domain account. For better security, we recommend that
you use an account different from the one used for the Management
Server Action Account.
Data Warehouse Write Account

• The Data Warehouse Write Account writes


data from the root management server or
management server to the Reporting data
warehouse and reads data from the
Operations Manager database.
Data Reader Account

This account is used to deploy reports, define


what user the SQL Reporting Services uses to
run queries against the Reporting data
warehouse, and for the SQL Reporting
Services IIS Application Pool account to
connect to the root management server. This
account is added to the Report Administrator
User Profile.
Extending the Schema

• On the CD Support tools:


– Momadmin.exe
Do the installation
Verification
• Program Files\System Center operations
manager
• Scroll down to look for .installlog files. 4 files.
• Check the event viewer. Brand new event log
provider is created named as operation
manger.
• Look for event if 29000 ops mgr config service
is started
• 26361 talks of sdk service is started.
Review
• Installing Pre Requisites
– Hardware and Software
• Installing the RMS
– Accounts
– Extending the Schema
– Pre req Checker
– Installing the database and RMS
– Verifying

You might also like