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.
Recently Altaro VM Backup was released in a new version, 7.6. This VM backup solution works for Hyper-V and VMware and this version introduces a bunch of new features. In my lab environment I´m using their backup solution to back up my servers. I have written about this once before a couple of years back but since a lot has happened during the years, it´s time to write a new review.
The new stuff in this version are the following;
Continuous Data Protection (CDP)
When CDP is enabled, VMs can be backed up as frequently as every 5 minutes or the maximum frequency permitted by the backup location and environment. This ensures that in a data loss scenario only a few minutes of data would be lost.
Grandfather-Father-Son (GFS) Archiving
GFS enables users to choose to archive the backup versions over and above their continuous and daily backups instead of deleting them (local backups only).
Now you can easily set up separate backup cycles to store a new backup version every week, every month and every year.
And then a couple of bug fixes. Read more about the news and bug fixes here.
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!
In about a week from now (April 12th), my employer Approved is running a webcast together with OpsLogix about our analytics solution for SCOM.
You will get to know more about “IT Service Analytics” and what it can do for you and your organization. I have previously mentioned “IT Service Analytics” in my blog, and if you want to know more right away you can do so here at SCOM Reporting made easy and intuitive and here at Creating dynamic distributed applications in SCOM.
Also check out Kevin Greene´s post here; Scandinavian SCOM solutions with global reach.
“IT Service Analytics is a free plug ´n play business intelligence and process support platform for Microsoft System Center. IT Service Analytics enables your IT organization(s) to make qualified decisions based on intelligent and accurate information gathered throughout your IT landscape.”
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
A couple of months back, Microsoft made Service Map available as a part of OMS. It all began about 18 months ago when Microsoft acquired Bluestripe and their product FactFinder. FactFinder helped SCOM users to visualize connections and let them see what relationships there were between different components in their environment.
Soon it became clear that this was about to be rebuilt and launched as a part of OMS. About a month or so ago, Service Map were made available as a public preview in the Azure region West Europe as well. This meant that I could add this solution to my Log Analytics workspace, and now here we are! 🙂
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.
So, the year has changed one more time and 2016 has now switched over to 2017. For me 2016 was a good year, I switched positions twice and have now landed in my new role at Approved Consulting. As I usually do around this time of the year (along with most bloggers I suppose) I´ll summarize the blog year below.
Views and visitors
I saw early in the year that I would break 2015 years’ numbers pretty fast. Looking back at 2016, that’s exactly what happened and the numbers for 2016 ended at a total of 36 079 views and 24 237 unique visitors.
The numbers of 2015 were 24 863 views and 15 353 unique visitors so a lot better thanks to all of you reading my blog posts. The most popular day was January 14th with a total of 362 views.
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