SCOM is the best monitoring system on this planet but there are also other systems around. You might find yourself in a situation where you need to get some information from the other monitoring system into SCOM. Because there is probably not a supported connector for SCOM available we have to find a way to talk to these systems.
One thing we would have to check if there is an API implemented and how we could probably interact with it. One possible API you will find is JSON-RPC. JSON-RPC is a lightweight remote procedure call protocol which is pretty simple. The general mechanism consists of two peers establishing a data connection. During the lifetime of a connection, peers may invoke methods provided by the other peer. To invoke a remote method, a request is sent. Unless the request is a notification it must be replied to with a response. If you would like to read more about the specification you can find it here.
One monitoring system which has such an API implemented is Zabbix. Zabbix runs on a Linux operating system and can monitor systems like *nix and Windows. For my tests I have downloaded the VHD Zabbix appliance and installed it into a VM on Hyper-V 3.0 which starts immediately. If you need some help and the passwords you will find it here.
If you followed the community lately, you see some are writing blog posts about reporting in System Center. It is funny as I also have been playing around with Report Builder 3.0 lately and it seems that I am following this trend.
Building custom reports is not that difficult if you have some sort of reporting background using tools like Crystal Reports or Access reports . The most important point is to have the appropriate SQL query which delivers the actual data you need. Luckily there are great posts in the community which help you getting over this. One post I highly recommend is Kevin Holman useful SQL query post. Although this post contains queries for SCOM 2007 I suppose most of them are also valid for SCOM 2012. In my case I wanted to build some reports for Agentless Exception Monitoring (AEM). In Kevin’s post there was exactly what I needed. AEM Queries to get Agentless Exception Monitoring information out of the SCOM data warehouse. I used this query here…
Have you ever heard of the famous System Center Universe (SCU) hosted by Catapult Systems? If not then it’s about time to visit http://www.systemcenteruniverse.com and check out the excellent content.
After talking to Catapult Systems we decided to bring this great event to Europe. We are now in the planning phase, talking to partners, speakers, sponsors etc. that are interested to partner with us and help making this event coming true.
We are happy to announce that the dates and location are fixed!
September 16th/17th 2013 – Bern/Switzerland
I just put a small FAQ together:
Today I ran in an unexpected problem at a customer. My mission was to install a SCOM 2012 SP1 Proof-of-Concept to show the customer what is possible and what information he can get out of SCOM. My last couple of installation were of course on Windows Server 2012. This customer was using Windows Server 2008 R2 SP1 and more or less on the latest patch level. So I started my mission installing SCOM 2012 SP1 therefore I checked all the necessary prerequisites for SCOM on the TechNet page, although I installed SCOM many times before it is just a habit of mine.
All prerequisites were installed and the wizard ran without any issue until the end and the installation started successfully. Right at the point where the wizard wanted to install the management server the installation ended with this error…
Today I had some conceptual work to do and as this always involves some fancy Visio diagrams, I ran into a problem which might also could happen to you.
Microsoft has released great Windows Server 2012 / Office 365 stencils for Visio 2013. You can find them here. As soon you start Visio and import the the stencils and drag your first shape onto your drawing you will see something like this…
About a year ago I wrote a blog post about an excellent management pack from Veeam to monitor a VMware ESX infrastructure. Veeam also released this year their new version of the management pack it is now officially called Veeam Management Pack v6 for VMware. In this post I would like to show a walkthrough in upgrading the old version 5.7 to the new version 6.0 and also introduce you to some of the new features in an upcoming post.
The basic architecture is the same as in version 5.7. You have one or more dedicated collector server which manage the connection between your SCOM infrastructure and your VMware infrastructure. The collector server needs to have a SCOM agent (proxy enabled) installed which sends the data collected from the collector server to the SCOM management server. To administer the connections to VMware you need to install Veeam Virtualization Extensions UI which connects to the Veeam Virtualization Extensions Service which handles the connections to the VMware infrastructure. New in the version 6.0 you have a PowerShell integration the Veeam Virtualization Extensions Shell. These extensions are a bundle of specific cmdlets which come in a PowerShell module to automate or querying deep information about the Veeam collected data/infrastructure.
Last year I published a PowerShell script to download the MMS sessions. It has been such a great success that I got a lot of nice responses. Therefore I made just small changes and it will work for the MMS 2013 also since they are published on channel 9.
But as we are used to in IT there are always enhancements included. Stefan Stranger has a great PowerShell script created to download the session catalog into Excel. You can find his blog post here. Because I wanted to create the session file, which contains the sessions to download dynamically, I created another script. I adapted the script from Stefan Stranger script to generate the sessions.txt file which is used by the downloader script as input file for actually downloading the session files. This way you can create the file over and over again in case the sessions change or whatsoever.
Ok, lets see how it works. There are two scripts…
- Create-MMS2013SessionFile.ps1 –> This file creates the sessions.txt file
- MMS2013_Downloader.ps1 –> This file downloads the sessions