Microsoft has unveiled a new update rollup 8.0.11030.0 for the Microsoft Monitoring Agent (MMA) that has fixed issues in the previous version of MMA. The fixes in this version includes below.
- Improved logging for HTTP connection issues
- Fix for high CPU utilization when you’re reading a Windows event that has an invalid message description
- Support for Azure US Government cloud
How to get update rollup version 8.0.11030.0 for Microsoft Monitoring Agent (KB3206063)?
This package is available as a manual download in the Microsoft Update Catalog. You can search for Microsoft Monitoring Agent and list down the available updates will appear in the search results.
In Operations Manager sometimes you may need to revert back to an older version of a Management Pack for a particular workload. The Operations Manager UI allows to delete and re-import MPs from the “Installed Management Packs” screen. The problem happenes when there are multiple and multi-level dependencies on the MP that you are trying to delete.
However now there is an enhanced version of a script available at TechNet (developed by MSFT employee Christopher Crammond) that will help you to revert Management Packs with a single command.
Using the Script
- Open the Operations Manager Command Shell prompt as an Administrator.
- Download the script to remove a management pack with dependencies from here.
- Execute the script as below.
.\RecursiveRemove.ps1 <ID or System Name of the MP>
- For an example if you want to remove the SQL 2014 Disocvery MP run the script as below.
How to get the the ID or System Name of an MP?
- Selecting the MP that you want to delete in the Installed Management Packs view by clicking Properties in the Actions pane.
- Copy the content in the “ID :” text box in the General tab.
In my last post I’ve shared the console crashing issue you face after installing the security updates in MS16-118 and MS16-126. Now Microsoft has published a new KBs to fix the console crashing issue in SCOM after applying these updates.
Individual hot fixes are available for the following list of Operating systems which you can download from here.
- Windows Vista
- Windows 7
- Windows 8.1
- Windows Server 2008
- Windows Server 2008R2
- Windows Server 2012
- Windows Server 2012 R2
For Windows 10 and Server 2016, the fix was applied to the latest cumulative updates.
It seems like the October 2016 cumulative Windows updates (KB3194798, KB3192392, KB3185330 &KB3185331) cause the SCOM consoles 2012/2016 in all Windows versions from Windows Server 2008 R2 up to 2016 and Windows 7 up to 10 Windows 10 to regularly crash without any doubt.
According to Microsoft Germany’s SCOM PFE Dirk Brinkmann who has blogged about this issue here, the SCOM team is working on a fix for this as of now and no ETA for an resolution has been provided yet.
Once a fix is available you will be able to see it via SCOM team blog.
A lot of companies are used to waiting for a disaster to happen in order to react. Only until there’s a service outage within their IT department do they take action instead of being more proactive and in control of their IT. The problem is that they don’t know where or how to get started in having a proactive approach to monitoring, even more so when they have a lot of infrastructure that needs to be monitored.
As a first step, IT needs to understand the business: all good designs come from understanding your IT services data dependencies and knowing how they relate to one another. Then they need to find out what are the best tools available today.
Microsoft System Center Operations Manager (SCOM) is a great platform to monitor components, and which a lot of people in the industry are already familiar with. There’s a lot of useful information within SCOM that can be used by the different personas in the company, however, the presentation layer and the way it is organized within SCOM is not the way those other personas look at IT. SCOM is still pretty technical and is all about components.
Looking at the personas in the IT service delivery organization, you will see that engineers definitely can work with SCOM. However, it usually takes them a while to figure out how they can easily get to the root-cause of a service outage, and what the business impact is of this outage will be.
Savision’s new whitepaper: “Business Service Management with System Center”, shows how to stay in control of your business services and make the most out of SCOM. Click here to download the whitepaper. The whitepaper is written by three experts: Microsoft MVP Robert Hedblom, Savision’s Co-Founder & VP of Product Management Dennis Rietvink, and Approved Consulting’s CEO & Solution Architect Jonas Lenntun.
It’s not like everyday you might want to remove certain management packs from your SCOM management group. The most painful task is removing the dependent MPs as you need to manually track all of those and delete them first in order to successfully remove the parent management pack.
Microsoft Senior Software Engineer Chandra Bose has written a PowerShell script that can identify and remove all of the dependent management packs automatically in such situations. Lets explore that script a little in this post.
How to get started?
First of all you need to run the Operations Manager Command shell as an administrator, which should be a member of the Operations Manager Administrators group as well.
When you execute the script you can either provide the ID or the System Name of the parent management pack as below. You can find the MP ID by visiting Administration > Management Packs > Right click the desired MP and select properties > Look for the ID field in the General tab which shows the MP ID. The System Name is the unique name of the MP (i.e Microsoft.SQLServer.2012.Discovery)
.\RecursiveRemove.ps1 <ID or System Name of the MP>
You can download the RecursiveRemove.ps1 script from here.
Microsoft has published the update rollup 9 for System Center Operations Manager 2012 R2 yesterday. Overall this update rollup focuses on significant fixes to Application Performance Monitoring in SCOM.
Fixes for following issues are included in this update.
- SharePoint workflows fail with an access violation under APM
- Application Pool worker process crashes under APM with heap corruption
- Some Application Pool worker processes become unresponsive if many applications are started under APM at the same time
- MOMAgent cannot validate RunAs Account if only RODC is available
- Missing event monitor does not warn within the specified time range in SCOM 2012 R2 the first time after restart
- SCOM cannot verify the User Account / Password expiration date if it is set by using Password Setting object
- SLO Detail report displays histogram incorrectly
- APM Agent Modules workflow fail during workflow shutdown with Null Reference Exception
- AEM Data fills up SCOM Operational database and is never groomed out
- The DownTime report from the Availability report does not handle the Business Hours settings
- Adding a decimal sign in an SLT Collection Rule SLO in the ENU Console on a non-ENU OS does not work
- SCOM Agent issue while logging Operations Management Suite (OMS) communication failure
This update rollup introduces the APM support for IIS 10 and Windows Server 2016. This requires an additional management pack Microsoft.SystemCenter.Apm.Web.IIS10.mp which can be found in “%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups” with its dependencies once you install the update rollup.
The Microsoft.Windows.InternetInformationServices.2016.mp which is a dependency, is not included in the UR9 package so you should download and install that separately before you enable APM for IIS 10 & Windows Server 2016.
You can download the binaries from here.
I have recently authored a whitepaper titled “Born in the Cloud: Monitoring Linux workloads with OMS” published by Savision. This whitepaper focuses on Linux workload monitoring capabilities of Microsoft OMS born-in-the-cloud management suite which is capable of managing and protecting heterogeneous on-premises, cloud and hybrid data centers.
Following are the key areas of discussion in my whitepaper.
- What Microsoft Operations Management Suite is and how it can simplify data center management.
- Leveraging OMS Log Analytics to analyze, predict and protect your Linux workloads.
- Integrating System Center Operations Manager with OMS for extended monitoring.
- Harnessing the power of Business Service Monitoring of Savision Live Maps Unity in Microsoft OMS.
You can download this FREE whitepaper from here.
Savision is the market leader in business service and cloud management solutions for Microsoft System Center. Savision’s monitoring and visualizing capabilities bridge the gap between IT and business by transforming IT data into predictive, actionable and relevant information about the entire cloud and datacenter infrastructure. You can visit www.savision.com for more information about their product portfolio.
Alas the long wait is over. Microsoft has released VASE for Visual Studio 2015 recently. VASE new version supports both Community and Enterprise editions of Visual Studio 2015 and Microsoft has confirmed that hey will keep supporting older versions of Visual Studio 2012 & 2013 as well.
VASE is an an add-in for Visual Studio which provides Life cycle Management Tools to support Management Pack Authoring for SCOM. One important thing is that this version doesn’t contain any feature enhancements from the previous version.
You can download VSAE for VS 2015 from here.
With dawn of the year 2016 almost upon us, Microsoft has released another build for it’s upcoming Windows Server & System Center 2016 suite of products. This Technical Preview 4 contains much new advancements and fixes based on customer feedback on the product clearly making it’s way as the cloud OS for next generation of computing.
Nano Server gets a new touch
Nano server, a headless installation option like server core which is going to be one of the installation option for Windows Server 2016 has improved a lot since last preview. In this release IIS & DNS server roles can be installed in Nano server in addition to existing Hyper-V & Scale-out File Server features.
Introducing Hyper-V Containers
Providing additional layer of isolation for Windows Containers, Hyper-V containers can be now deployed as virtual sandboxes to host application workloads. This technology utilizes the nested virtualization capability introduced in Windows Server TP4. Also you can use both docker & PowerShell to create, deploy and manage Windows Containers.
System Center 2016 Improvements
Another milestone is the System Center 2016 TP4 release with some awesome features for private cloud management. Now you can use the SCOM agent to monitor your Nano Servers in TP4. SCCM 2016 TP4 has introduced some new functionality to improve Windows 10 deployment experience via SCCM.
Mobile Device management (MDM): enhanced feature parity with Intune standalone – Many of the MDM feature that are supported via Intune standalone (cloud only) are also enabled for Configuration Manager integrated with Intune (hybrid) in this release.
Integration with Windows Update for Business – Now you can view the list of devices that are controlled by Windows Update for Business.
Certificate provisioning for Windows 10 devices managed via on-premises mobile device management
You can download Windows Server 2016 Technical Preview 4 & System Center 2016 Technical Preview 4 evaluation bits from here.