Most enterprises now have either moved to cloud, or are moving towards it. And why not? Running your workloads on cloud services such as Azure frees you up from a lot of maintenance and administrative overheads, and you can use this time to do something better. Here are some major benefits to moving to cloud:
Having worked with both SCOM and Azure Monitor, recently I was asked to compare them both and suggest the right choice. First off, I have a disclaimer to make – Azure Monitor is great, but it can not replace SCOM entirely, not just yet. SCOM 2019 was recently released and it came loaded with some
A few days ago I was in need to export all my SCOM subscriptions and be able to analyze them thoroughly. So I researched for a script/solution online but didn’t find anything particularly useful to my exact requirement. So I decided to write one myself! I wrote a quick version of the script to get
The company that I am working for Savision always looking for an opportunity to contribute to the community; therefore, I found time at Savision to work on the old OleDB query monitoring project. Now I am happy to announce that I fixed bugs and add more features, here is a list of key features: Easy
This time, we are meeting Leon, who is a very passionate about sharing his knowledge with the community and help others! He is definitely one of those guys that you go to to get your stuff done! Let’s get to know him better: Q: Please tell us a little about yourself and your background. A: My
This is one widely known “inconvenience” with working with Powershell to manage your subscriptions in a big SCOM environment. Consider the following widely common scenario: You have a SCOM environment with a fairly large number of subscriptions. You have a planned maintenance scheduled, and so you plan to disable all your subscriptions so that the
This is a question that I often get asked by the customers I work with and apparently a lot of others as evident by the related questions on the forums. One way of doing it is to author your own service monitor, but that involves considerable amount of knowledge and experience of management packs and
Ruben is back with another awesome blog post, and I have no doubt this one is going to help a lot of people! We all know the hassles of migrating your SCOM from one version to another, and it involves a lot of manual efforts. And especially so when you choose the side-by-side upgrade path.
We discussed about the common misconceptions regarding failover for Windows agents in SCOM in the previous post (part 1). In this part, as promised, Stoyan Chalakov is going to be discussing about the failover for Linux machines monitored by SCOM. Here goes: Linux/UNIX agent failover and Resource Pools – debunking the myth – Part 2
This is another of the hot topics I find with differences in opinion among the experts. The other one we discussed was Windows Agents and Failover – Debunking the Myth! Should you enable autogrowth on SCOM Operational Database? I did some some research online and consulted some of the best SCOM experts I know and put
You must be logged in to post a comment.