on January 15th was the last day of the OMS portal before its
retirement. It has now completely moved to the Azure portal instead.
Since Operations Management Suite (OMS) have been retired for a few months and is no longer available for new customers, the portal had served its purpose and have now been retired. Nowadays administration of the included services is handled through the Azure portal instead.
A few weeks ago, we (Approved) held our annual event called SCOM Day in Gothenburg with about 80 attendees. This year we focused on hybrid monitoring using SCOM 2019/1901 and Azure. It was a full day of sessions where we had Thomas Maurer talking about Azure Stack, Martin Ehrnst who was talking about API integrations in SCOM. And lastly, we had Marcel Zehner who showed us how he monitors and interacts with his Tesla using Azure.
I also held a session along with my colleague Jonas Lenntun about the news in SCOM 2019 and 1901 where we focused on the parts that we think makes most sense and will most likely come to use for most users. The news was announced during Microsoft Ignite that took place in Orlando in September. But to those of you who didn’t attend any of these events, the news is still important to know about.
Lately I have been working a lot with monitoring VMware using SCOM for some of our largest customers and have gotten to think about this more and more. Even though cloud providers such as Amazon Web Services (AWS) and Microsoft Azure keeps on showing great numbers of growth (and profits for that matter), the absolute majority of customers IT are still on-prem. Since about ten years, virtualization has been about the coolest thing there is and the largest player in this area is still VMware.
Thinking about how large this area is and the importance for the organization, we need to monitor the VMware platform. Just as well as we need to keep track of what’s happening with our services, such as web shops or other business critical systems, we need to monitor the foundation it all relies on as well.
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.