In this blog post I will go through the installation process of my “lab” machine with all relevant SCOM roles installed on a single box. I’ve prepared a virtual machine running Windows Server 2008 R2 fully patched and SQL Server 2008 R2 fully patched (incl. SP1). If you know SCOM 2007, you should know that 2012 now requires you to install DW components because some dashboard widgets depend on DW data. You also need to stick with the default collationin order to run SCOM (SQL_Latin1_General_CP1_CI_AS) and last but not least, you need Full Text Search enabled. Because I’m also going to install the web consoles, I’ve added the IIS role to my Windows Server 2008 R2.
To download SCOM 2012 RC, go to: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27974
A word of caution though: “Upgrades from RC to RTM in *any* scenario will not be supported by Microsoft support unless you are part of the TAP program for the specific product that they are trying to upgrade. Only TAP customers are licensed to run pre-RTM software inproduction.”
After we took care of all the required stuff, let’s jump in and start the setup:
As mentioned before, I will install all components for a typical single-server lab configuration.
In my case, the prerequisites checker failed with the following errors:
This happens if you install IIS role after you’ve installed the .NET 4 Framework. It’s easy to fix. Just go to the .net 4 framework directory and execute:
After you’ve registered .NET 4 in IIS, go to the ISAPI and CGI Restrictions and enable both, the 32 bit and 64 bit ISAPI extension:
Since I’m installing a fresh, new management group for my lab environment, I select to create a new management group and give it a meaningful name
Oddly enough (maybe this is an RC thing), the next page shows the license terms. Usually it’s one of the first pages in the setup wizard. Anyway, agree to the terms and continue.
I think this is pretty much self explanatory. I did increase the initial database size because 1 gig of operational data is reached quickly. Let’s head over to the next page:
Here’s an interesting part. In previous versions 2007 and 2007 R2, data warehouse was an optional component. In 2012 it’s mandatory. At least having the DW database is mandatory. Having reporting is still optional (as you could see in the very first setup page).
SQL reporting services (SRS) are also used exclusively in 2012 as it was in the 2007 and 2007R2 versions. You need to have a dedicated SRS instance because after setup is done with SRS (mainly putting a custom security model on top of it) it’s “SCOM-ified” and unusable for other stuff!
The next two pages are dedicated to the web console:
If you want to publish the web console to the internet, I strongly recommend to enable SSL.
Since I’m using this internally in my lab only, I leave the default settings.
The new consolidated account configuration page makes it much more easier to configure all the action accounts.
The next page is dedicated to error reporting and customer experience improvement. Enable those settings if you can!
Verify the summary page and click next to start the installation process:
That’s it. After the installation finished you can close the installer and start the Operations Console: