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.
Earlier this year, Microsoft announced a coming big change for the System Center suite. Instead of launching new versions every fourth or fifth year as before, they will now release continuous updates. This means they will launch two new versions per year to fasten up the release cycles and to really keep the products up to date.
This isn´t anything new, it´s been done for Configuration Manager ever since Windows 10 launched about two years ago. This schedule, called “semiannual channel release” will now also include the other parts of the System Center suite. Except for System Center, this goes for Windows Server as well. Besides from Windows Server 2016, you can now download and install Windows Server 1709 (YY/MM).
The first release I will be looking at is the one that in the end will be named 1801. Last week Microsoft launched a Technical Preview of System Center 1711, a preview that will later become 1801 which is meant to be released in January.
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.
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