Back in January this year I wrote a post about how you can install the OMS agent using PowerShell. Now the time has come to include the Service Map agent in the equation as well since this is a feature that recently got Generally Available. You can find the original post about installing the OMS agent here. What´s new in this script is that I have added a section for downloading and installing the Service Map agent as well. Enough talking, let´s get to it!
One of the things I work with in my role as a product manager for Operations Management Suite (OMS) is the automation part of the suite. In this case, it means Azure Automation that can do a lot for us in terms of automating our recurring tasks. This post will be the first post about what you can do with Desired State Configuration (DSC) as a part of Azure Automation.
Before we get started there are some things worth knowing. As a part of OMS, the licensing for DSC is based on per-node and the listing price is at $10 per node/month. This means that each server you want to configure using DSC is assigned this license.
Before we get started there is one prerequisite you need to take care of; the latest version of WMF 5 (Windows Management Framework) needs to be installed on the server about to be configured as a DSC node. This makes is possible for the node to communicate with Azure Automation. You can find WMF 5 here. This isn´t necessary if you’re running Windows Server 2016 as I will be doing for this post.
The first thing we need to do is to create a file stating what to communicate with and what to do. This is called a MOF file and is what makes is possible to retrieve configuration, but also to register the server as a node to Azure Automation DSC.
A while back I wrote a post where I went through the basics and how to get started with the new feature Service Map, which is a part of OMS nowadays. Read the post here. That post only showed how to get started and what kind of information you will get from the solution, but it didn´t say anything about troubleshooting. And at last, it did just explain how to get started with your Windows servers (or clients for that matter).
Today I will go through how to get up and running with Linux servers as well, as well as some troubleshooting.
When considering the Service Map agent, the following Windows operating systems are supported.
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 SP1
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
Operations Management Suite (OMS) is a great thing and easy (and fast) to getting started with just installing an agent on a server. However, installing OMS agent would be nice to get automated and instead of doing it with the command line it could be done with PowerShell, compared to doing it manually which would take s significant amount of time. Keep reading to find out how to install OMS agent with PowerShell.
I have checked the command line installation option and that isn´t as good and fancy as doing it with PowerShell, hence this post. I have put together a PowerShell Script that will download the agent, install it and remove the installation files. All you need is the Workspace ID and Workspace Primary Key.
One of the better releases in a while has been the ability to monitor VMware with OMS. Earlier this year a new solution was released for OMS Log Analytics for monitoring VMware for you from your environment. This is something that we have done for years now with SCOM but now the time and capabilities have come to OMS as well. The first problem I ran into with this blog post was the fact that all my VM´s are running on Hyper-V and therefore, I had no VMware host to run the test on.
Okay, that’s a pretty small problem since all I had to do was to fire up a computer that I had lying around at home and install VMware ESXi to it. I did run into some problems during the installation with the network drivers, but nothing that my Google skills couldn´t handle.
While working with this solution, I have run into pretty much every known error there is getting this solution to work properly. That´s why I have made such a massive post out of this to give you a smoother on-boarding process
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.
This time I´m going to leave the box a little for what I use to write about in my blog. This time I´m going to talk about a product which lets us back up VM´s in an easy, fast and effective way. I came in contact with Altaro a few weeks back and that´s when I started looking into their solution ”VM Backup”. With VM backup you can back your Hyper-V servers but also your VMware servers. In this blog I will go through how to set it up, how to take backups of your Hyper-V servers, restoring a server and some other good stuff.
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.
So it´s that wonderful time again. The sun is shining, it´s almost spring here in (the southern parts of) Sweden and I´m getting into a new role in a new company, read the blog post about that here. Wouldn´t this be a great time to write a blog post? Yeah, I thought so to and here we are.
Near real time performance monitoring and visualization in Operations Management Suite
Earlier, in October last year to be precise I wrote a blog post on how to get started with the Near real time performance monitoring in OMS. I will not show how to set it up in this post, to find out more about that (easy) part check out the blog post about it here.
A new functionality has been released and is available now as I write this post. With this new functionality you will be able to put multiple instances like computers and disks etc. against each other to help you get an overview of your environment. To demonstrate this, I have put together some queries you can execute to get data about CPU, Memory and Disk on your servers. It´s really easy and all you have to do is to paste the query into the log search field.