How to install and configure System Center 2012 Operations Manager (SCOM 2012)

Hi all,

It's with a big pleasure that i explain you in this post how to install and configure System Center 2012 Operations Manager !

What's System Center 2012 Operations Manager?:

Operations Manager provides infrastructure monitoring that is flexible and cost-effective, helps ensure the predictable performance and availability of vital applications, and offers comprehensive monitoring for your datacenter and cloud, both private and public.

What's new in System Center 2012 Operations Manager?:

New Monitoring Capabilities

Network Monitoring

Operations Manager provides the ability to discover and monitor network routers and switches, including the network interfaces and ports on those devices and the virtual LAN (VLAN) that they participate in. You can also delete discovered network devices and prevent the deleted network devices from being rediscovered the next time discovery runs. For more information, see Monitor Network Devices.

Application Monitoring

In Operations Manager, you can monitor Internet Information Services (IIS)-hosted .NET applications from server- and client-side perspectives to get details about application performance and reliability that can help you pinpoint root causes of incidents. When you specify settings, the types of events to collect, the performance goals to measure, and servers to monitor, .NET Application Performance Monitoring reveals how web-based applications are running. You can see how frequently a problem is occurring, how a server was performing when a problem occurred, and the chain of events related to the slow request or method that is raising exceptions. This information is required to partner with software developers and database administrators to help ensure that applications perform correctly and reliably for your customers. For more information, see Authoring the .NET Application Performance Monitoring Template and Monitoring .NET Applications.

Location of .NET Application Performance Monitoring


Performance and Scale

Resource Pools

A resource pool contains only management servers and provides the ability to distribute workloads across multiple management servers, such as availability, network device monitoring, distributed monitor health rollup, and group calculation. For more information, see How to Create a Resource Pool.

Removal of Root Management Server

In Operations Manager, all management servers are peers; there is no root management server. The workload is split among all management servers in a management group, which provides high availability without requiring a cluster.

Improved Experience

Web Console

Operations Manager introduces a new web console that is optimized for faster load times and provides you with access to the new IT pro dashboards.

Dashboard Views

Operations Manager includes new comprehensive dashboard views that combine multiple panels of information into a single view. In Operations Manager, you can add the new dashboard views to My Workspace and the Monitoring workspace.

Creating Dashboard Views

Dashboard views have been significantly upgraded in Operations Manager from their capabilities in System Center Operations Manager 2007 R2, including custom layouts and nested dashboard views.

Display Dashboard Views in SharePoint

The Operations Manager web part displays specified dashboard views and can be added to Microsoft SharePoint 2010 sites. For more information, see Add a Dashboard to a SharePoint Site.

System Center 2012 - Orchestrator Replaces Connector Functionality

Connectors have been discontinued for System Center 2012 – Operations Manager and their functionality is replaced by System Center 2012 - Orchestrator. Orchestrator provides the ability to create and run automated workflows, called runbooks, made of multiple activities that each performs a distinct function. The connector functionality of enabling System Center Operations Manager 2007 R2 to synchronize alerts with remote systems is achieved by creating runbooks, using activities that interact with and one or more other products. Because runbooks can include sophisticated logic and activities from any number of Integration Packs, you can implement scenarios that cannot be easily achieved with connectors. Integration Packs will be delivered for each System Center component and provide additional activities specific to a particular component.

Operations Manager Module for Windows PowerShell

Operations Manager provides a Windows PowerShell 2.0 module containing a full set of new cmdlets. The cmdlets in this module are only compatible with Operations Manager. You can recognize the Operations Manager cmdlets by the "SC" preceding the noun. For additional information about the Operations Manager cmdlets, open the Operations Manager command shell and type Get-Help about_OpsMgr_WhatsNew. For information about how the Operations Manager 2007 cmdlets map to the Operations Manager cmdlets, type Get-Help about_OpsMgr_Cmdlet_Names.

To use the Operations Manager cmdlets, you must establish a connection to an Operations Manager management group. You can establish either a persistent connection in which you can run multiple cmdlets, or a temporary connection when running a single cmdlet. For more information about connections, open the Operations Manager Shell and type Get-Help about_OpsMgr_Connections.

UNIX- and Linux-Based Computers

In Operations Manager, you can perform privileged operations on UNIX-based and Linux-based computers using unprivileged Run As accounts by combining with “sudo” elevation on the target UNIX-based and Linux-based computers. This capability avoids the need for UNIX or Linux root passwords to be known on the management server, and keeps the privilege control entirely within the domain of the UNIX or Linux administrator. Operations Manager also includes new Windows PowerShell cmdlets for performing agent maintenance functions on UNIX-based and Linux-based computers, allowing for scripting and background operations.  In addition, the resource pool feature supports computers running UNIX and Linux.  If a management server fails, another management server in the resource pool can take over the monitoring, providing high availability. For more information, see Monitoring UNIX- and Linux-Based Computers

Operations Console

You will notice some subtle changes to the Operations console. The Actions pane is now the Tasks pane, and includes a new section called Navigation Tasks that makes it easy for you to open views for a selected object. The Tasks pane offers two tabs: one for actions and one for resources and Help links. The Navigation and Tasks panes can be minimized or expanded instantly by clicking the arrow in the title bar of the pane.

 

Let's GO! Big Smile Big Smile Big Smile for the requirements!

Big Smile System Center 2012 Operations Manager Big Smile DOWNLOAD SOURCE HERE

Minimum Hardware Requirements

Use the Operations Manager Sizing Helper to determine hardware requirements for each System Center 2012 – Operations Manager server feature. If you want to install more than one feature on the same computer, use the higher of the recommended hardware requirements for any of the combined features.

Supported Processors, Memory, and Disk Space

noteNote
Operations Manager does not support installing the 32-bit agent on a 64-bit operating system. Operations Manager provides native support for x86-based computers for agents and consoles, and x64-based computers for all server features and support for agents on computers with 64-bit Itanium processors.

Minimum Software Requirements

Operations Manager server features require a supported operating system.

Note the following database considerations for Operations Manager:

  • Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
  • Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
  • SQL Server collation settings for all databases must be SQL_Latin1_General_CP1_CI_AS; no other collation settings are supported.
  • The SQL Server Agent service must be started, and the startup type must be set to automatic.
  • Side-by-side installation of System Center Operations Manager 2007 R2 Reporting and System Center 2012 – Operations Manager Reporting on the same server is not supported.
  • The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start. For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
  • If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see tempdb Database.

If you want to install more than one Operations Manager feature on the same computer, you must install the prerequisite software for all of the combined features.

Requirements by Feature

Management Server

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1.
  • Processor Architecture: must be x64.
  • Windows PowerShell version: Windows PowerShell version 2.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
  • Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For more information, see the following documents:

Operations Console

Web Console

  • Operating System: Windows Server 2008 R2 SP1.
  • Processor Architecture: must be x64.
  • Web browsers: Internet Explorer 7, Internet Explorer 8, Internet Explorer 9
  • Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console and the following role services installed:

    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Logging
    • Request Monitor
    • Request Filtering
    • Static Content Compression
    • Web Server (IIS) Support
    • IIS 6 Metabase Compatibility
    • ASP.NET
    • Windows Authentication
  • Selected website for web console: requires a configured http or https binding.

    WarningWarning
    Installing the web console on a computer that has SharePoint installed is not supported.
  • Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For more information, see the following documents:

    Sources Prerequisite

Let's GO! Big Smile Big Smile Big Smile  for the SCOM installation!

I have take in my example:

1 Domain controller Acttive Directory (installation not detailed in this post)

1 Windows 2008 Server R2 for SCOM 2012 and Reporting rôle on the same server [but attention, normally you install the reporting role on another server, read this > Operations Manager Reporting on the same server is not supported (Microsoft information)]

With SQL 2008 SP1 R2 + CU 4 (not detail in this post bue necessary to install before scom 2012) Collation fo Database SQL = SQL_Latin1_General_CP1_CI_AS

Have administrators Right lol Big Smile

 

Launch and decompress the install file...

Launch the Setup.exe and Click on Install

 

Click on :

Management server

Management console

Web console

Reporting server:

Attention, normally you install the reporting role on another server, read this > Operations Manager Reporting on the same server is not supported (Microsoft information)

And click Next

Click Next

That's possible that you have some parameter to activate...

In this example under, i will do configure the ISAPI and CGI restrictions for ASP.NET v4.0.3019 in IIS and configure the ram memory (for SCOM 2012, this minimum requirement is to have 4GB )

For configure the ASP.NET v4.0.3019,  open the IIS console and select the server; select ASP.NET v4.0.3019; right click on, select Allow.

And for resolve my memory requirement, i just upgrade my VM to 4Go Big Smile

 

Return to the setup and select Next at this step

Select create the first Management server in a new management group and click Next (in my example, i take AdminGroup)

Approve the licence terms and click Next

Type the server name; leave the default and click Next

Type the server name; leave the default (the database creation launch automatically when the sql server is available...) and click Next


Click Next

It's necessary to configure the Sql Server Agent service with > Startup type = Automatic

Click Next

Select Use Mixed Authentification Click Next

Insert Domain user name; password; let by default other parameter and click Next

Select and participate to the SCOM 2012 improvement ; and click Next

Click On and Next

Click Install

Installation in progress...

Setup is complete, installation finish !!! Big Smile Big Smile Big Smile

Great,your SCOM 2012 installation is ready!!!

I like very the DotNet Framework 4 for the console display, beautiful !!!  ENJOY ALL Big Smile

Long life to System Center 2012 Product !!! Big Smile Big Smile Big Smile

Comments

# How to install and configure System Center 2012 Operations Manager (SCOM 2012)

Hi all, It's with a big pleasure that i explain you in this post how to install and configure System