Many customers frequently ask the question whether or not it is possible to fetch a report of up-time of a service being monitored with SCOM. Usually, the answer is – not out of the box. However, you can achieve this using a simple workaround.
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 the underlying coding. It usually takes a lot of time as well. Not everyone has the right knowledge or the time to spend on this so I thought I’d share a quick trick I do to measure uptime of a service and also be able to present it to the concerned parties in the form of a report.
You may be familiar with Microsoft Operations Management Suite (OMS) — a management system that works to simplify your IT processes. Troubleshooting, change tracking, and updates are just a few common IT tasks that OMS could handle. OMS components brought together backup services, site recovery, log analytics, and automation and are available for hybrid, multi-cloud, and on-premises environments.
Microsoft deprecated OMS as of January 2019, moving all functionality into the Azure portal. Learn more about why OMS and the new Azure portal are useful for your IT workflow and what has changed with the migration to Azure.
When you decide to move your Exchange environment to the cloud, you might be confused to discover that you still need to maintain an on-premises Exchange server. There are several reasons for this, stemming from the migration process and on to Identity Management.
If you’re moving from an active on-premises Exchange deployment, you’ll first configure an interim “Exchange Hybrid” environment which hosts mailboxes within Exchange Online and your local Exchange server. The two locations share namespace, address books, free-busy, calendars, really every Exchange functionality is synced between them. Mail flow and other functions appear to be internal, but might actually be processed and stored in the cloud environment.
Azure Stack enables you to run Azure workloads on-premises or even within a colocation facility, enabling stronger security and control over your data and applications with a single management platform for your public Azure cloud infrastructure and your Azure Stack deployment.
You can use many of the best Azure tools, processes, and features — including add-ons and open source solutions from the Azure Marketplace — in the cloud of your choice, helping to meet regulatory or technical challenges.
Before you get started with this intriguing hybrid and private cloud technology from Microsoft, there are a few things you’ll need to keep in mind, however. Here are some of the most important.
In a world where we have self-driving cars, cures for complex diseases, and where we’re building houses with 3D printers, some enterprise organizations still manually patch servers which run their mission-critical applications.
Enterprise data center management can fray the nerves of even the most experienced administrators. “To err is human”, as the saying goes, and errors can happen during patching, even with the powerful toolset in Microsoft System Center. A server admin could spend hours struggling with a single patch and cause productivity delays the next day for the systems which don’t get addressed.
There are effective ways of automating these tasks, which come with price tags both directly and indirectly related to patching itself.
Automated patching server application patching can alleviate a lot of work for IT management teams. It shifts the patching and updating process outside of business hours. In an ideal world, Microsoft’s System Center Configuration Manager (SCCM) would flawlessly execute server application patches.
However, there are some gaps in SCCM patching functionality, especially when it comes to orchestration, validation, and report logs. These can cause issues with QA and risk mitigation and can drive frustrations among your IT staff.
Microsoft Azure Active Directory (AAD) is a multi-tenant cloud-based directory and identity management service. It combines core directory services, access management, and identity protection in to a single solution. Azure Active Directory is not to be confused with Azure Active Directory Domain Services, which is a separate service and not the focus of this article.
For every organization that chooses to subscribe to Microsoft Online Services– Office 365, Dynamics 365, Intune, etc., choosing the correct identity model for AAD becomes an important task. In this article, we will have a look at the characteristics of each.
While there are no specific dependencies on the identity model of AAD for Microsoft Online Services to function, your organizational needs and other factors such as manageability, access control, auditing, and user experience determine which identity model should be deployed.
Microsoft’s products “SCCM” and “SCOM” sound like confusingly-named twins, but try to get past your first impression of them as a set in identical dresses posing for a portrait. It is true that they are in the same Microsoft system center family, but each has its own distinctive traits and roles.
As part of any monitoring strategy, we might need to automate some tasks to provide key information to evaluate the state of our infrastructure or apply a repetitive action to resolve specific issues.
We have several ways to implement this. One option is to use Microsoft’s Azure Automation toolset. Let’s explore what you can control with Azure Automation and how to get started using it for cloud server update management, configuration, and more.
Creating a new Management Pack is not complicated—all you need to do is first install Visual Studio Authoring Extensions.
This blog will walk you through how to create your first Management Pack in Systems Center Operations Manager, one that will discover apps by identifying their registry key.