Microsoft Operations Management Suite alerting has moved from preview mode to generally available status.

Personally, I am getting rather tired of the dismissive tone adopted by virtualization and cloud vendors when you raise the issue of disaster recovery.  We previously discussed the limited scope of virtual systems clustering and failover:  active-passive and active-active server clusters with data mirroring is generally inadequate for recovery from interruption events that have a footprint larger than a given equipment rack or subnetwork.  Extending mirroring and cluster failover over distances greater than 80 kilometers is a dicey strategy, especially given the impact of latency and jitter on data transport over WAN links, which can create data deltas that can prevent successful application or database recovery altogether.

In part three of this multi-part blog series, we covered how to configure OMS to collect data through integration with System Center Operations Manager (SCOM), and through direct connections to individual servers. We also covered how Microsoft Operations Management Suite uses Solutions to deliver insights into your log data by providing a cost-effective, all-in-one cloud management solution so you can better protect guest workloads in Azure, AWS, Windows Server, Linux, VMWare, and Open Stack.

In part two of this multi part blog series, we covered how to configure OMS to collect data through integration with System Center Operations Manager (SCOM), and through direct connections to individual servers. We also covered how Microsoft Operations Management Suite uses Solutions to deliver insights into your log data by providing a cost-effective, all-in-one cloud management solution so you can better protect guest workloads in Azure, AWS, Windows Server, Linux, VMWare, and Open Stack

In part one of this multi-part blog series, we covered how to establish a Microsoft Operations Management Suite environment; in the second part, Part II, we will discuss how to get started with Microsoft Operations Management Suite and we will introduce OMS solutions. If you missed Part I, please make sure to check it here before you move on to Part II.

At the end of March, an event little known outside of a small community of vendors, will happen:  World Backup Day.  Expect a flurry of blogs and tweets and posts and all of the other stuff that goes along with such marketing events.  Then, expect the discussion to go silent for another year…unless a newsworthy data disaster occurs.

In this series of blog posts, we will show you how to get started with Microsoft Operations Management Suite (OMS) so that you can protect your heterogeneous environments, respond proactively to changing business needs and simplify IT management – all from a single portal with no infrastructure to maintain. This post will also show you how Microsoft Operations Management Suite delivers immediate, actionable insights into your log data by providing a cost-effective, all-in-one cloud management solution so you can better protect guest workloads in Microsoft Azure, AWS, Windows Server, Linux, VMWare, and Open Stack.

Server Management Tools has been released last week in the preview build. This tool is available in Microsoft Azure to manage servers from a Web-Based GUI and command line. It is able to manage Windows Server 2016 Technical preview running on servers located On-Premises or in Azure as well.

A new low-cost attack that decrypts sensitive communications in neglectable time has been discovered recently. The attack works against TLS-protected communications using RSA cryptosystem which expose the key through SSLv2, which was retired two decades ago due to vulnerabilities, but still may be supported by some service due to legacy compatibility reasons or misconfigured TLS implementations.

I will explain to you today how to execute an Azure Automation Runbook through an ASP.NET website who is stored on a free Azure WebApp.

To do this, I will use Webhook from the Azure Automation Runbook. I used this article to understand how it works.