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! 
for the requirements!
System Center 2012 Operations Manager : 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
 Note |
|
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
- Microsoft Report Viewer 2008 SP1 Redistributable Package
- Microsoft .NET Framework 3.4 SP1 hotfix
- Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
- File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
- Server
Operating System: must be Windows Vista, Windows 7, Windows Server
2008, Windows Server 2008 R2, or Windows Server 2008 R2 SP1.
- Processor Architecture: must be x64 for servers and x64 or x86 for a client computer.
- Windows Installer version: at least Windows Installer 3.1.
- Windows PowerShell version: Windows PowerShell version 2.0.
- Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see the following documents:
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.
 Warning |
| 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! 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
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
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 !!!
Great,your SCOM 2012 installation is ready!!!
I like very the DotNet Framework 4 for the console display, beautiful !!! ENJOY ALL
Long life to System Center 2012 Product !!!