Here are my notes for installing SCOM on a single server. The DB will be on a different server.

Prerequisites:

In a nutshell you need to do these things first. For reference, Here is the official documentation. I also used Kevin Holman’s blog about a similar deployment here.

Create SCOM related accounts in AD:

• domain\scom_aa  [management server action account]
• domain\scom_srvc [System Center Configuration service and System Center Data Access service account]
• domain\scom_admins [SCOM Admins go in here]

Add scom_aa, scom_srvc and your own domain account to scom_admins. You may want to add your team’s accounts  in there as well.

Install Windows server 2012 and update it, add to domain etc.

Install the Report Viewer 2010. Download it from http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6442

Install the Web Server (IIS) role. There are many options which need to be selected under IIS. So it may be easier to use this command on a admin PowerShell console:

Add-WindowsFeature NET-WCF-HTTP-Activation45,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –Restart –source E:\sources\sxs

Note that you will need to insert your Windows Server 2012 installation DVD into the server’s E drive (or whatever drive letter you have).

Now you need to register ASP.NET with IIS.  The simplest way is to open an elevated command prompt and CD to C:\Windows\Microsoft.NET\Framework64\v4.0.30319. Then run this command:

aspnet_regiis.exe -r

DB installation. Since I already have SQL Server 2012 installed on another server I will not go into that here. That DB server is also hosting the DB for SCVMM.

Add the scom_aa group to the Local Administrators group on the SQL server and the SCOM server.

Database server/instance installation

I learnt that your DB instance cannot be shared with anything else. In my first attempt to install SCOM, I tried to use an existing DB instance, which was also hosting SC VMM. The setup failed. In my second attempt I installed a second instance on the shared DB server. That means VMM database will be on the existing instance. The SCOM database will be hosted by an additional instance on the DB server.

Install SQL server database:

Here is how I installed a second instance of the SQL server on the shared database server:

1. Insert DVD
2. Run setup.
3. Choose to “Perform a new installation”
4. I chose these features:
   • Database Engine Services.
   • Full-Text and Semantic Extractions for Search
   • Reporting Services – Native
5. Set the name of the new instance as SCOM, since it will not be used for anything else.
6. On the Server configuration screen, set SQL Server Agent to Automatic
7. Leave the rest as default and click next-next until you get the DB installed.

Ok, now that the DB installation is done. We can proceed with SCOM installation.

SCOM installation:

Logon to the server using your own admin account, the one you have already added to the scom_admins group.

1. Run setup from the SCOM DVD
2. Click Install
3. Select the first three features and leave the last one (Reporting server) unchecked. Reporting server is installed on the SQL server. Click next.
4. Change location (if needed). I chose to install it in the D drive.
5. Hopefully the prerequisites test will pass. If not, resolve any errors.
6. On the Configuration, Specify an installation option page, select Create the first Management server in a new management group, type in a simple name for your management group. I named it something related to our business name.
7. Click Next.
8. Accept license and click next.
9. On the operation database screen, type the server name of the DB and the port. If you run into a problem, you can find what the problem is by hovering your mouse pointer above the red X icon.
10. I left the SQL server port at default – 1433. The DB server was previously configured to be using dynamic ports (by default it is dynamic IF you setup a named instance). I read somewhere on the ‘net that SCOM 2012 does not support dynamic ports. However I did not have any trouble with it.
11. Click next.
12. On the next screen – Configuration, Configure the data warehouse database, in the Server name and instance name box, type the same DB server name as above.
13. click next.
14. On the Configuration, Specify a web site for use with the Web console page, select Default Web Site
15. On the next screen, choose Mixed authentication and click Next
16. On the accounts screen,  choose “Domain Account” for all 4 options and enter the credentials of the accounts you created earlier, for example:
    • Management Server action account = scom_aa
    • System Center Configuration service and System Center Data Access service account = scom_srvc
    • Data Reader account = scom_srvc
    • Data Writer account = scom_srvc
17. Click next
18. On the “help improve..” screen you may choose whatever you wish. I choose to participate. Maybe it will help Microsoft improve its products. click next.
19. On the Microsoft Update screen, I chose “On”. I think your domain policy will over ride this selection.
20. Look over the installation summary carefully. I took a screenshot of the web addresses listed at the bottom of that screen (for my notes).
21. If everything looks OK, click Install.
22. Note: the first time I did this, I ran into a problem. The SCOM installer itself crashed! I looked at the report and researched on the error, figured out that the database needs to be exclusive to SCOM. I fixed that problem (see above, the DB installation section), uninstalled SCOM, rebooted the server and tried setup again.
23. The installation completed successfully and I let it run Windows update. It immediately found one SCOM related update. I let it install it.
24. Then I ran Windows update again in the control panel. It found two more updates related to SCOM. I let it install and eventually it asked for a reboot. I let it reboot.
25. Now I start Operation Console from the Windows 2012 Metro interface. That starts the SCOM Operation manager application.
26. Now lets install Reporting Server. This will do on the DB server itself.
27. Logon to the DB server and run setup from SCOM DVD.
28. Choose only “Reporting server” from the features list to install.
29. Type in the name of a management server which you have just installed.
30. Choose the correct local SQL instance.
31. Enter the domain account domain\scom_srvc’s credentials as the Data Reader Account.

That’s it! I have successfully installed SCOM!

Now I will write about how to quickly become productive using SCOM.