Best Practices

Part V (Installing Operations Manager 2012 R2) To start at the beginning check out: Part I

Install the SCOM pre-reqs:

Report Viewer

http://www.microsoft.com/en-us/download/details.aspx?id=35747

Launch PowerShell as an admin

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

Download SCOM 2012 R2 Media and Mount the media

Launch Setup

Click Install

Select All features and click Install

Click Next

Since we are installing on a DC it will prompt you to alert you this is not recommended. If this were anything other than a stand-alone test environment you should never do this.

Click Next

Create the first Management server in a new management group (Choose a Management group name)

Agree to the license terms — Click Next

Enter localhost or FQDN for the servername

Enter localhost or FQDN in the servername field

Click Next

Click Next

Click Next

Best practices is to use a separate account for each of these, but for the sake of these instructions one account will suffice

You will receive this prompt, again using a domain admin account is not recommended, but this is an isolated test environment so for simplicity I am making an exception.

Click Next

On (recommended) Next

Click Install

Click Close

Part IV (Installing SQL)

At this point depending on which System Center Product you are installing you may need to spin up more VMs. With SCOM you can create an all in one domain controller, SQL, SCOM Management Server though ultimately it is better to create a distributed environment with each of these items on a different VM. To save a bit on instruction writing I am going to create an all-in-one SCOM environment, but ultimately from this point it is easy to take what you have already learned to create a distributed environment. For excellent documentation on how to spin up test environments for each System Center product once you have Hyper-V and a domain controller in place I recommend taking a look at Kevin Holman’s quickstart guides:

http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx

http://blogs.technet.com/b/kevinholman/archive/2013/10/30/configmgr-2012-r2-quickstart-deployment-guide.aspx

http://blogs.technet.com/b/kevinholman/archive/2013/10/18/orchestrator-2012-r2-quickstart-deployment-guide.aspx

https://blogs.technet.com/b/kevinholman/archive/2013/10/18/service-manager-2012-r2-quickstart-deployment-guide.aspx

http://blogs.technet.com/b/kevinholman/archive/2013/10/18/app-controller-2012-r2-quickstart-deployment-guide.aspx

http://blogs.technet.com/b/kevinholman/archive/2013/11/07/dpm-2012-r2-quickstart-deployment-guide.aspx

https://blogs.technet.com/b/kevinholman/archive/2013/10/18/scvmm-2012-r2-quickstart-deployment-guide.aspx

Since screenshots can sometimes be a little bit more helpful I will walk you through a slightly more visual guide to installing SQL and then SCOM in Part V

Log into the Domain Controller with your sysctr account

Download SQL 2012 enterprise edition with SP1 x64

Right click and mount the media

Run setup

Select New SQL Server stand-alone

Click OK

Click Next

Click I Accept & Next

Click Next

Click Next

SQL Server All Features with Defaults– Next