The following are the steps and links associated with building an all-in-one OpsMgr 2012 environment. This blog post specifically was written using Hyper-V on a Windows Server 2012 environment. Please note that running Operations Manager 2012 (RTM) running on Windows Server 2012 is NOT a supported configuration.

Why am I trying this when I know it’s not supported? 

  • I know that someone out there other than me will eventually end up doing this so it’s best to get the ideas out ahead of time and find out what works and what doesn’t.
  • Secondly, with the release of SP1 for OpsMgr 2012 this will become a supported option so this is good preparation for what is coming early next year.

Preparing for installation of OpsMgr 2012 All-In-One:

  1. Installed Hyper-V on the server (or Windows 8 system) where the all-in-one environment will be installed.
  2. After adding the Hyper-V role,  we created a new virtual machine called “All-In-One” with a dynamically expanding drive, and mounted the Windows 2012 media.
  3. After booting up and installing the operating system the next step was to activate the operating system. After activation Microsoft Update was utilized to bring the system to current patch levels.
  4. This system is running Windows Server 2012 so we configured it to use dynamic memory (startup memory = 1024 mb, maximum memory = 8192 mb).
  5. Next, we hard-coded the IP address on the server (and the DNS server as itself), and then executed the process to make this server a domain controller. The domain installation process for a domain controller is shown at: https://www.catapultsystems.com/cfuller/archive/2012/10/12/goodbye-dcpromo-it’s-been-fun.aspx.
  6. Next was the installation of prerequisites for Operations Manager, including the Web Server role (IIS) [installed all features other than FTP just for the lab], SQL Server 2008 R2 (including Reporting Services, and don’t forget SQL server full text search), SQL Server 2008 R2 SP1, and Report Viewer Controls. The remote registry service had to be started on the server to allow installation as shown below in the screenshot. Details on installation in Windows 2008 for the various individual components is available from Microsoft at http://technet.microsoft.com/en-us/library/hh205990.aspx.  

image.

Installation of OpsMgr 2012:

  1. Installing all the Operations Manager 2012 components followed. This includes the Operations Database, Management Server, Operations Console, PowerShell, and Web Console components. After the installations completed, we rebooted the system then installed the Reporting and Data Warehouse components (remember to make sure that the SQL server agent service is running)… The completed installation screen is shown below.
  2. We also installed UR3  for Operations Manager 2012.
  3. Next we downloaded all relevant management packs – SQL Server 2008, Windows Core OS 2012, IIS 2012 and Power Management 2012.
  4. From SystemCenterCentral.com we downloaded and installed the ReSearch This! management pack to tune alerts in our All-In-One environment.
  5. In the Alerts view of the Operations Console, we customized the view to add the Last Modified and repeat count fields – this makes it easier to locate alerts that occurred once versus those that are recurring.
  6. Alert tuning was next but I was highly impressed as there we currently no active alerts in the all-in-one environment based upon the management packs which were currently available.

image

The OpsMgr 2012 Console and Windows 2012 activation shown below.

image

image

How about running OpsMgr 2012 on core?

Wait, but will it run on core? I would need an external console of course to connect since the GUI would be removed but it might work. I went ahead and removed the UI features to see how it work function.

image

image

After converting the system to run without the UI components and rebooting the “System Center Data Access” service was not able to startup correctly and could not be connected to via a remote console as shown in the screenshots below.

image

image

image

This may work with the release of System Center 2012 Service Pack 1. This would be an interesting new ability to be able to run OpsMgr 2012 management servers in core!

 

Summary:

  • System Center Operations Manager 2012 will install and appears to function on Windows Server 2012 but this is NOT a supported configuration at least until System Center 2012 Operations Manager SP1 is released.
  • Based on tests in my environment running OpsMgr 2012 RTM on core does not work due to issues with the System Center Data Access Service.