Install System Center Operations Manager
We are now finally ready to install SCOM.
Install SCOM
Start by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as en_system_center_2012_operations_manager_with_sp1_x86_x64_dvd_1347175). Start by running the setup.exe.
On the splash screen click the Install link.
On the Select Features screen, select the feature you want to install. In our example, we are installing all features on the same server, so we will select all of them and click Next.
Next chose the location that you want to install the software to, and ensure there is enough space. Then click Next.
The Setup Wizard will then check the prerequisites that are needed, based on what features you selected to install. If there are any issues you will need to address these before you can continue. Review the information and the resolution(s) provided.
For example, you will need to install the Web Server (IIS) role, including some non-default elements along with the Microsoft Report Viewer 2010 Redistributable Package.
NOTE: I didn't have time to document how to install these roles/features, hopefully you are able to accomplish it without issue. However, if anyone needs it, please message me and I will work to add it in.
Once you address all prerequisite needs, the setup wizard should appear as follows. Click Next.
On the Installation Option screen, choose the appropriate option. In our example, since this is the first Management Server that we are installing, we will choose the ‘Create the first Management server in a new management group’ option, and also enter a Management Group Name.
Next read and accept the license terms, and click Next.
On the Configure Operational Database screen, fill in the SQL server and instance name. When you do, the data and log folders paths will auto-populate. Now click Next.
On the Configure Data Warehouse screen, fill in the SQL server and instance name. When you do, the data and log folders paths will auto-populate. Now click Next.
Next select a SQL server instance to use for the Reporting Services, then click Next.
Next select the IIS website to use for the Web Console, and then click Next. Note: if you chose to use SSL, you will need a certificate.
For the Authentication Mode, chose the applicable option based on how you plan on using the web console. For our example, we will only use it in an Intranet environment, so we will choose ‘Use Mixed Authentication’ and click Next.
For the Operations Manager accounts, fill in the appropriate information and click Next. Note: As part of your preparation for installing SCOM, you can follow your provisioning process and have these accounts pre-created. You should also take note of the level of access each account requires.
You can choose if you want to participate in the Customer Experience Improvement Program (CEIP). Make your choices, and then click Next.
For the Microsoft Update screen, choose if you want to automatically apply updates. Note: In a Production environment, you will probably not want to turn this on, because there are applicable change management procedures to follow, and you should test updates in a non-Production environment.
On the Installation Summary screen, review the input and selections made, and click Install.
The installation may take several minutes, but once it has been completed, click Close. Note: If you do not want to launch the SCOM console immediately, then de-select the ‘Start the Operations console when the wizard closes’ checkbox.
Congratulations, you have now successfully installed SCOM!
In the next part of the series, we will install Audit Collection Services (ACS), since it is not a part of the main installation.
BONUS: How to Install the SCOM Agent
Now that you have SCOM setup, you need to install the Agent on the systems you want to monitor.
Start by launching the SCOM console, and navigate to the Administration pane. From there, under Device Management find ‘Agent Managed’. Right-click on the Agent Managed item, and choose Discovery Wizard.
The Computer and Device Management Wizard will start. You must first choose why type of device you want to discover and manager. You have 3 choices, Windows Computers, UNIX/Linux Computers, or Network Devices. For our example we will choose Windows Computer, and then click Next.
On the Auto or Advanced screen, you can choose to let SCOM scan the domain to find the computers, or if you want more control over which systems are monitored, you can choose the Advanced Discovery. If you choose the Advanced option, you can also choose if you want to discover only servers, clients, or both. Additionally, you can choose which Management Server you want the discovered systems to be managed by.
Since we only have one Management Server in our lab, we only have one option, but in a Production environment you can use this to balance the load between multiple Management Servers.
Make your appropriate selections, and click Next.
Next you need to specify the Discovery Method that will be used. Again, you can allow SCOM to scan Active Directory, or you can manually type the computer names for it to check against.
From my own personal experience, it is usually best to manually type the names of the computers, as this gives you more control over what systems are added to SCOM, and how many at a time.
Choose your appropriate options, and click Next.
You can now specify the Administrator Account to use. We will accept the default selection to use the Management Server Action Account, and then click Discover to initiate the process.
SCOM will then go off and attempt to communicate with the specified systems.
Here is a diagram that shows how computer discovery works in SCOM.
The systems that SCOM is able to communicate with will appear in the Discovery Results. From there, select the device(s) that you want to install the SCOM agent on.
In our example we will install the SCOM agent on all systems in our lab environment.
Make your selection(s) and click Next.
On the Summary screen, you can control where the SCOM Agent will be installed. In my personal experience, the default location is sufficient. You can also provide an Agent Action Account. In a lab environment, we can use the Local System, however, in a Production environment I have personally seen a designated Agent Action Account (usually a Service Account) be used in this context.
Make the appropriate selection/input, and click Finish.
SCOM will then start the Agent installation task. Depending on your network, the number of devices, etc. it may take a while to complete.
When the discovery and agent installation completes, it should look like this. You can click Close on the status window.
Returning back to the SCOM console, you will now see the system(s) that you discovered and installed the Agent on.
Congratulations, not only do you have a working SCOM environment, but you also have SCOM actively monitoring!
