Since Operations Management Suite was announced at this year’s Microsoft Ignite event, here’s a quick post to show how to connect a single computer and also a System Center Operations Manager 2012 R2 Management Group to the Microsoft Operations Management Suite.
OMS provides a central portal for monitoring your server workloads whether they are based in a cloud service or your datacentres.
This enables you to manage your geographically separated environments as a single entity as seen in this handy Microsoft slide from the event.
OMS has built-in Solutions to analyse the various data coming back from your server agents. These include event logs, patch levels and malware protection. There are also a couple of role-specific Solutions such as Active Directory and SQL Assessment which can be used to guide you on health issues or compliance with best practices.
To get started, you’ll need to sign up for OMS and create a dashboard here
Once you’re logged in to the dashboard, go to ‘Getting Started’ and select some Solutions to add. I picked all the default offerings and we’ll look at configuring them in a later post.
Next download the Windows Agent and install it on your first computer.
I’m using a workstation for this as my servers are already being monitored by SCOM. You could in fact configure a computer to send events and monitoring data to both SCOM and OMS if you wanted; this could be useful for testing the platform if you’re planning to move servers away from SCOM.
Connect a Standalone Computer to OMS
Run the installer and step through the first screens – there are a few settings required.
Select to connect to Microsoft Azure Operational Insights (I expect this will be changed to OMS in later releases) and leave the SCOM option unticked.
Copy the Workspace ID and Key from the OMS page shown above to the installer and complete the remaining steps.
You should now see an additional entry in the Control Panel called Microsoft Monitoring Agent Properties which you can use to edit the ID and Key values later on if required.
In the dashboard you can now see your first data source is connected.
Connect SCOM to OMS
Next, we’ll move on to connecting our SCOM Management Group to OMS.
In the SCOM Management Console select Administration > Operational Insights Connection. Bear in mind you need the last update rollup for this option to be available as it replaces the Advisor option seen in previous patch levels. System Advisor agents are NOT compatible with OMS.
Click Register to Operational Insights Service.
Enter your Microsoft account credentials.
Select the OMS Workspace you created earlier and complete the wizard.
Once you’ve connected to an OMS Workspace the SCOM screen will change to this.
In the SCOM Management Console select Administration > Operational Insights Managed and click on Add a Computer/Group – in my case I’m using the SCOM server itself.
After a while you will see the second data source connected in the OMS dashboard. Mine took about an hour and I had to log into OMS again for the SCOM data source to show as connected.
Next on the Getting Started page add an event log for OMS to monitor. I’ve selected to collect Error events from the Operations Manager log as we’re using the SCOM server as a data source but you can just as easily add the System, Application or one of the more specific logs available.
Now you should see the Getting Started widget shows all steps completed.
Two sources is not a lot but once you’ve completed these steps for more standalone and SCOM monitored servers in your environment you will get a better picture of its overall health. Also if you’re using the free tier to test or demo OMS you should be aware there is a data upload limit of 500MB per day. You can see more on pricing on the Microsoft links below.
So this was a short introduction to start using the OMS service and getting some data to view on the dashboard. It will be great for organisations with disparate hybrid environments to be able to see the state of their services in a single view and to then be able to drill down into events and logs for more detail.