A couple of weeks ago I started working for a new company which I wrote about here and I am now the product manager for OMS with a focus on Log Analytics and Azure Automation.
However, this does´nt mean I have given up on SCOM just to focus on OMS.
I am just as passionate about SCOM as I´ve been before and you will see some of that in this post. Since I started working for Approved Consulting I have had the opportunity to start digging into the analytic tool they have been developing during the last year.
Some of you may have seen some of it before in a copuple of postings made at ITServiceAnalytics (ITSA), but I will now start digging into the different parts of it to show what you can do with it.
In this first posting, I will do some performance reporting using SCOM reporting but I will also show how it´s done using ITSA to show the different ways to generate reports. For all of this to be nice and easy, we are using a Distributed Application for a sales platform with all of its components.
It´s been created using Savision Live Maps but still, a regular Distributed Application that we can use to generate reports. You don´t have to use a DA for this to work, but it sure makes it a lot easier as you can filter your data in a complete different way.
Yesterday Microsoft Ignite started with a big bang and during the keynote several cool things were shown, some for the first time and some that we´ve seen before. Sadly, I´m not at Ignite this year but I was able to stream the keynote from home instead.
One thing that got a lot of attention was the (OMS) Log Analytics where the VMware solution was shown among others (to be continued…) and the strength of the product was shown to the 22 000 attendees along with all of us that were watching remote.
If you are looking to improve your IT Monitoring with SCOM, then Savision has released a free E-Book that can help you. If you are getting overwhelmed with tons of alerts, if you are not getting the visibility you need from your IT environment or are finding it hard to get crucial information to the right teams, then you will should read this e-book.
Savision’s E-Book will show you how in 3 Simple Steps you can get the most out of your SCOM investment.
You can download the e-book here.
If you are planning to migrate to SCOM 2016, then you can’t miss out on Savision’s upcoming live session featuring 3 industry experts:
- Microsoft Product Manager – Mahesh Narayanan
- MVP John Joyner
- MVP Bob Cornelissen
During the session, the experts will cover what’s new in SCOM 2016 and best practices on how to migrate to SCOM 2016. It will feature live demos and a Q&A session where you can ask the experts anything you need to know about SCOM 2016.
To register for the session, click here.
It´s been a while since I wrote anything now (5 weeks approximately, which is not okay) and it´s time to monitor Nano Server again. Due to some really annoying issues with my lab environment I have had major problems installing the latest technical preview of Windows Server and SCOM. But I decided to have the last laugh and now both Windows Server 2016 and SCOM 2016 are running on TP5 level.
So what´s new in SCOM 2016 TP5?
- Monitor a broad range of network devices without requiring Operations Manager certification
- Monitor Nano Server deployments, including DNS and IIS roles
- Realize more than 2X scale improvement in monitoring UNIX/Linux servers
- Experience a more responsive application console, including the ability to navigate across different views and pivots without having to wait for the data to load
- Seamlessly discover, install and update required management packs right from the administration console
- Tune management packs, and alter the monitors and alerting rules – either at source level or group level – to reduce alert noise
- Plan and schedule maintenance windows for workloads without generating spurious alerts in Operations Manager console
- Utilize the Preferred Partner program to discover third-party management packs, authoring tools, dashboard utilities, etc., right from the Operations Manager console
The feature I´m going to dig into in this post is the “Monitor Nano Server deployments” part, which have been improved in TP5 and you´re now able to install the agent on to a Nano server through the discovery process in the SCOM console. If you have been reading my blog for a while you might know that I wrote a post some weeks ago about how to monitor Nano server using SCOM, but that was using SCOM 2016 TP4 so I will show the new and improved way here instead. Find that post here.
If you are using Azure and SCOM or multiple SCOM management groups, then you spend a lot of time trying to make sense of all the complex and technical data that they generate difficult. In addition, you must be getting storms of alerts. If you are getting dispersed data from these different monitoring systems but are unable to connect it, then you need to get the big picture of what’s happening in your IT landscape. If you are using SCOM and Azure and multiple monitoring systems and can’t put all this data in a business context, it’s time for you to take your IT to the next level and take your monitoring to another level.
If you just like me have been using OMS now for a while and collected a serious amount of data, collecting everything from a ton of events to the update status of my servers, you might now have a lot of information to work with. You can always use the search syntax in OMS to check out on your data in a nice way and it´s very simple. But what if you want to create reports out of the data? It´s possible to export data from OMS to watch in Excel for example, but what if you want to do some fancier reports using the data? Visualizing OMS data in Power BI is your answer and will help you create those fancy reports that you´ve been dreaming about!
A while back I wrote a blog post for the OMS team blog where I went deep on how to integrate OMS with Power BI and to export data from OMS to Power BI. If you haven´t read that post yet, you really should. Not only because it´s really nice to see how easy it is to get started, but also because I won´t show the integration part in this post. Instead, I will just show you some examples of what you can do with the information that you sent from OMS to Power BI in a couple of reports. You can find the blog post here on the OMS team blog.
This post is covering Windows Server 2016 and SCOM 2016 TP4. A new post covering Windows Server 2016 and SCOM 2016 TP5 can be found here.
So its time for some blogging again. With all that we have in front of us with a new generation of System Center but also Windows Server 2016, there´s plenty of fun stuff to write about. In my last post I showed how to get started with the Nano server which is a part of Windows Server 2016. If you havent already, find it below.
The topic for this post is to show you how to monitor your Nano server that you created in the previous blog post using System Center 2016 Operations Manager TP4. For this post I have created a brand new Nano server according to the steps of the previous post meaning I will set up a new IIS server once again. I did run into some trouble while preparing this post so thanks to the Nano server product team for helping me out with some issues.
When Windows Server 2016 is launched later this year, we will be able to choose from three versions to deploy, the full version including the complete user interface, the core edition which we´ve seen before and the new Nano edition which we haven´t seen before.
Nano server? What´s that?
Nano server is the version that´s been on an extreme diet which you will manage remotely and also install remotely. A few advantages that Microsoft has mentioned in marketing Nano server is:
- 93 percent lower VHD size
- 92 percent fewer critical bulletins
- 80 percent fewer reboots
Getting started with Nano server isn´t as easy as we´re used to, just mounting the media and installing it onto our virtual machine so that´s why I´ve written this guide on getting started with Nano Server. You can read more about Nano server here.
Creating the Nano server VHDX file
Copy “NanoServerImageGenerator.psm1” and “Convert-WindowsImage.ps1” from the \NanoServer folder in the Windows Server Technical Preview ISO to a folder on your hard drive. In this case I´m using E:\Media\NanoIIS as the path. The next thing is to define what we want our Nano server image to be like and what the server should be named. If your planning to run your Nano server on a physical machine, you should add this line into the script as well: “-OEMDrivers”. This will include storage and network drivers in the image.
FREE Whitepaper on OMS – Born in the Cloud: Monitoring Linux Workloads with OMS
Download the whitepaper here
IT Professionals are using a plethora of tools to build a complete monitoring solution in order to keep their datacenters healthy and operational. Powered by Microsoft’s Azure Cloud Platform, Operations Management Suite (OMS) provides more predictive & analytical capabilities to keep your data center healthy.
Savision’s newest whitepaper focuses on monitoring Linux workloads with OMS for analytics, proactive monitoring and resource utilization in your heterogeneous data center environment. The whitepaper is written by Microsoft MVP Janaka Rangama: ‘Born in the Cloud: Monitoring Linux Workloads with OMS‘, and provides insights on how organizations can combine the existing System Center Operations Manager (SCOM) environments with OMS to gain control over modern hybrid clouds. In addition, you will learn how you can extend OMS with business service management information to ensure you can directly know how all that detailed log data impacts your business and service levels.
With this whitepaper, you will learn:
- What Microsoft Operations Management Suite is and how it can simplify data center management.
- How to leverage OMS Log Analytics to analyze, predict and protect your Linux workloads.
- How to integrate System Center Operations Manager with OMS for extended monitoring.
- How to harness the power of Business Service Management with Savision’s Live Maps Unity using Microsoft OMS.
You can download the whitepaper here.