SCOM: Add community power and keep the engine running…

  Let’s face it: a good program is like a car. You need to maintain it properly to keep it in running condition. Well this is also the case with SCOM. I visit a lot of clients and one of the main questions I get is in fact how to make sure SCOM stays healthy and running. Well there are some indicators in SCOM itself suggesting that there are issues with the install but unfortunately they are easily missed or looked over. So this is where the awesome SCOMunity steps in! This post should become your one stop location to find some of the leading community management packs you’ll need to keep your SCOM environment going or at least very easily pinpoint where there are (potential) issues. These are management packs I actually install at almost every client I visit: TAO Yang’s Self Maintenance management pack Tao has been...
Read More

Microsoft Operations Management Suite: Remove workspace

  This blog post is part of the Microsoft Operations management Suite Quick start guide which can be found here: http://scug.be/dieter/2015/05/08/microsoft-operations-management-suite-quickstart-guide/   One of the things I’ve noticed right away when I fist opened the Microsoft Operations Management Suite (OMS) was the fact that I had different workspaces. They were all created in opinsights because the fact I added 3 different management groups in their respective SCOM console. No sweat of course. I now build 1 management group in my lab environment where I configured everything so I wanted to get rid of the other workspaces. Turns out there are 2 ways you can delete a workspace and in fact this was not clear in the beginning. How to get to the “close workspace” option The remove option is well hidden in the menu’s to probably avoid deletion by accident which is actually a good thing but it’s a little bit too...
Read More

Microsoft Operations Management Suite: Connect Datasources

  This blog post is part of the “Microsoft Operations Management Suite: Quickstart guide” which can be found here: http://scug.be/dieter/2015/05/08/microsoft-operations-management-suite-quickstart-guide/   After we have successfully created our workspace and have installed our Solutions it’s now time to bring in our data to start the magic and witness the insight in our data that OMS can bring Here you have 3 options: Attach Servers directly (limited to 64 bit): This is used if you want to attach a server which is not monitored by SCOM. A certificate will be generated and inserted into a package that downloads and installs the Microsoft monitoring agent service onto the desired server and connects the server to your OMS. Attach System Center operations manager: You can attach various management groups in OMS. If you click connect you will be guided to the on boarding process for connecting a SCOM environment to OMS. More on this later Attach Azure Storage account: you can add a Azure storage account to facilitate the availability options regarding...
Read More

Microsoft Operations Management Suite: Configure Workspaces

This blog post is part of the Microsoft Operations management Suite Quick start guide which can be found here: http://scug.be/dieter/2015/05/08/microsoft-operations-management-suite-quickstart-guide/   A wokspace is basically the same as your management group in SCOM. It contains all the differernt Solutions, connected datasource and azure account to start working. You can have several workspaces based with one account but interaction between different workspaces is not possible. Create a workspace In this scenario we are going to build a new workspace. Just choose the name / email and the region and click create Next up we need to link the Azure subscription we have associated to our Microsoft or corporate account. Note that having an Azure subscription is not a prerequisite for this step (you can just click not now) but it is highly recommended. To make sure you are the proper owner of the email (note that it doesn’t have to be an email that is by default the email address associated to your account) Microsoft is sending you...
Read More

Microsoft Operations Management Suite: Quickstart guide

  So Microsoft Operations Management Suite (OMS) was launched during Ignite 2015 and is awaiting your data to show its power to give you the insights in your environment and actually manage your environment not limited to the boundaries of your own environment or your azure environment. But before we can play with the goodies we need to configure everything correctly. This guide will grow in time to be your one stop to get you going, configuring and using Microsoft Operations Management Suite (OMS) . Bookmark this post to get regular updates on my journey through OMS to help you save some time while exploring the possibilities of OMS. Below is a list of topics that can be used to already start your journey: Microsoft Operations Manager Suite: A first glance Microsoft Operations Manager Suite: Configure Workspaces Microsoft Operations Manager Suite: Connect Datasources Microsoft Operations Manager Suite: Remove a workspace ...
Read More

Microsoft Operations Management Suite: A first glance

This blog post is part of the “Microsoft Operations Management Suite: Quickstart guide” which can be found here: http://scug.be/dieter/2015/05/08/microsoft-operations-management-suite-quickstart-guide/ It has been a while since i was been blown away by news about SCOM and monitoring in general. During the recent keynote of Ignite in Chicago however Microsoft delivered… I personally was surprised by the vast number of announcements regarding System Center in general and monitoring and management tools in particular.  One of the coolest things for me personally was the announcement of Microsoft Operations Management Suite (OMS). A little bit of history is in its place to show you this is not a product which was born overnight. The first sign that Microsoft was working on a service to monitor and aggregate data in the cloud emerged when System Center Advisor was launched. System Center Advisor was a small tool which gave you a quick overview of your compliance level of your environment and check to see how you are doing in...
Read More

SCOM: Configure a monitor recovery task for a healthy state

During a recent project a client had a small request to create a monitor and run a command when a device was not accessible anymore. Easy right! But (yep there’s always a but) they wanted to run a command when the monitor was returning back to a healthy state to restart a service when the device came back online… Hmmm and all in 1 monitor. So the conditions were as follows: Monitor: Action: Run a PowerShell based monitor to test the connection with the device BAD: Device is down => Run recovery task to remediate GOOD: Device is up again => Run recovery task to restart service (note: Always do this small matrix of a monitor design to exactly know what the customer wants) I don’t have the device to simulate but came up with a small example in my lab to show you how to get this working with just 1 monitor. The situation in my lab is very simple. I want to turn on my...
Read More

SCOM: Monitor the monitor part 1: PowerShell

Recently I got a question of an engineer during a community event why SCOM didn’t notify him when SCOM was down. My first response was very similar to the response of my favorite captain below: But this got me thinking actually because the engineer made a good point. That to have a full monitoring you should have another mechanism in place to monitor the monitoring system. Most companies still have a legacy monitoring system in place that can be leveraged to monitor the servers of SCOM but let’s face it: keeping another monitoring system alive just to monitor the SCOM servers only adds complexity to your environment for a small benefit. That’s why I started building a small independent check with PowerShell. In part 1 of this series I’ll go over how to monitor whether your management servers are still up and running. To do this we need to make sure that we have a watcher node which is able to ping the...
Read More

SCOM: PowerShell tip: Set Resource Pool Automatic members

  Today I ran into a situation where I had to test an advanced notification setup to send alerts to another helpdesk system. The notification channel activated a PowerShell script with parameters out of the alert to send data to the other system. After creating the notification channel there was no way to check whether the server I already configured was functioning correctly. My 2 management servers were automatically part of the Notifications resource pool thus making it not possible to force my testing through my configured management server. These are the steps to troubleshoot the notifications on 1 management server and rectifying the situation again after testing and configuring both management servers: These are my resource pool: Notice the difference in Icon for an automatic and manually populated resource pool. Right click the notifications Resource Pool and select manual membership. An automatic properties dialog will pop up...
Read More

SCOM: Connect management groups between on-prem and Azure

  During a recent project I explored the benefits on hosting a 2 legged SCOM environment for both on-prem and cloud services. Although this is possible with just one management group and site to site VPN to the cloud they opted for a 2 management group approach to keep a certain sort of divider between the on-prem and the cloud. In this blog post (who knows it could become a series) I’ll show you how to connect the management groups to each other so they can exchange alerts and use 1 console but benefit from presence of a management group on both platforms. In this scenario I’m going to use connected management groups. As explained here http://technet.microsoft.com/en-us/library/hh230698.aspx Connecting management groups in SCOM 2012 gives you a couple of benefits. The biggest one in my opinion is the fact you can have multiple management groups with different settings but use 1 console to get all...
Read More