System Center Operations Manager 2012 Beta – Installation

As part of the Operations Manager 2012 Community Evaluation Program (CEP), I was able to get my hands on Operations Manager 2012 Beta for evaluation purposes.

I have prepared test environment for that purpose and evaluation of OpsMgr 2012 Beta started with the installation. In my case, I have decided to use a Windows Server 2008 R2 virtual machine which has SQL Server installed locally and which is also Active Directory Domain Controller. Of course, this is not recommended nor best practices configuration for production environments, but it should work for testing purposes within lab environments.

After promoting server to Active Directory Domain Controller, and after successful installation of the SQL Server 2008 R2 (using the SQL_Latin1_General_CP1_CI_AS collation), I’ve decided to start the installation of OpsMgr 2012 Beta. Let me now share my experience…

In my test environment, all SCOM features are installed on the same server. They are:

  • Management server,
  • Management console,
  • Web console and
  • Reporting server.

Note that in OpsMgr 2012 there is no root management server (RMS) – all management servers are now peers and workload is split among all management servers in a management group. This now means that clustering is not required to provide fault tolerant and highly available solution.  Thumbs-up for that!

If you also decide to put all SCOM features on the same server, before running setup make sure that Web Server (IIS) role is installed on it. You can easily do that by using the Add Roles Wizard.

When running Add Roles Wizard to install Web Server (IIS) role, the following role services must also be included:

  • IIS6 Metabase Compatibility role service,
  • ASP.NET, including required role services for it,
  • Windows Authentication role service,
  • Static Content role service,
  • Default Document role service,
  • Directory Browsing role service,
  • HTTP Errors role service,
  • HTTP Logging role service,
  • Request Monitor role service,
  • Request Filtering role service,
  • Static Content Compression role service and
  • IIS Management Console role service.

Then, another software requirement for the Operations Manager 2012 is Microsoft .NET Framework 4 which you can find on Microsoft Download Center at the following location:

In order to save some time, it is better to install .NET Framework 4 after the Web Server (IIS) role. If you have installed Web Server (IIS) role after installing .NET Framework 4 you will receive the following errors in the prerequisites checker of the OpsMgr 2012 Setup Wizard:

The ISAPI and CGI Restrictions are disabled or missing: Web Console cannot operate properly because the ISAPI and CI Restrictions in Internet Information Services (IIS) are disabled or missing for ASP.NET 4.0.

ASP.NET 4.0 Registration Check: The ASP.NET 4.0 handler is not registered with IIS.

Hopefully, this error is well documented in the Quick Start Guide to Microsoft System Center Operations Manager 2012 Beta, as well as on Microsoft TechNet. To resolve it, there are two steps which must be taken:

You must open a Command prompt as Administrator and run the following command which registers ASP.NET 4.0 with
IIS: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –r

You should receive the following output:

Start installing ASP.NET (4.0.30319) and changing IIS configuration to use this version of ASP.NET.

Finished installing ASP.NET (4.0.30319) and changing IIS configuration to use this version of ASP.NET.

Secondly, run Internet Information Services (IIS) Manager, open ISAPI and CGI Restrictions properties of the web site, select ASP.NET v4.0.30319, and then click Allow.

NOTE: ISAPI and CGI Restrictions in IIS for ASP.NET 4 are not enabled by default so this step is also applicabe in case if you have installed IIS before installing .NET Framework 4.

Once this was configured, prerequisite checker of the OpsMgr 2012 Setup Wizard did not report any issues and I was able to proceed with the installation.

There were two more errors on which I bumped into, but they might be specific to my test environment only.

On the Configure the operational database page of the OpsMgr 2012 Setup Wizard, setup wizard was not able to successfully validate SQL Server using NetBIOS computer name with an error saying: “This SQL server could not be found”. I solved this issue by typing LOCALHOST as the server name.

Second problem was related to the fact that OpsMgr 2012 in my test environment is running on a server which is also an Active Directory Domain Controller.
Management Server was in “Not Monitored” state because Run As accounts did not have the “Allow log on locally” right. You can identify this kind of
problem by the occurrence of the following event in Operations Manager event

Log Name: Operations Manager
Source: HealthService
Event ID: 7002
Task Category: Health Service
Level: Error
Description: The Health Service could not log on the RunAs account <service account name> for management group <management group name> because it has not been granted the “Allow log on locally” right.

After granting “Allow log on locally” right, health state of the management
server turned into healthy (green) state.

Operations Manager 2012 is now up and running and I am looking forward in evaluating it.

System Center Operations Manager 2012 Beta – Installation