Tag Archives: Update Rollups

Update Rollup 9 for SCOM 2012 R2 now available

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.

Important

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.

DPM 2012 R2 UR7 Re-released

It’s been a while since my last blog post. I’m working on a DPM 2012 R2 test lab these days which I’ve planned to update to the latest UR version. When I checked for the latest UR7 got to know that the bits have been re-released.

As for the DPM team there is an issue in DPM 2012 R2 UR7 released on 28.07.2015 which causes expired recovery points on the disk were not getting cleaned up, resulting an increase in DPM recovery point volume after installing UR7. This re-release has addressed this concern and you can download the upadted bits via DPM 2012 R2 UR7 KB or Microsoft Update Catalog as of today.

OK I have updated to UR7 before 21.08.2015. Now what?

For those who are facing this dilemma should know that the re-released UR7 is not pushed via Microsoft Update and advised to manually install the new package  on the DPM Servers with older UR7 package installed. The installation process will automatically execute pruneshadowcopiesDpm2010.ps1 PowerShell script which contains the fix.

Post-deployment Tips

There is no change in the DPM version (4.2.1338.0) in this re-release and it will remain same after the update. Also you will have to update the Azure Backup Agent to latest version (2.0.8719.0) prior installing DPM UR7 to ensure the integrity of your cloud backups after this release.

For those who like me updating to UR7 the old fashion way (wait for a month or two, lookout for bugs and then update) you’ve got nothing to worry.

What’s new in Update Rollup 6 for SCOM 2012 R2

Last week Microsoft has announced the availability of System Center 2012 R2 Update Rollup 6. This update rollup contains many improvements plus new functionality for most of the products in the suite. Let’s see what’s in the box for SCOM admins with this release. I got to admit that rather than new features, this UR is more focused on fixing some existing issues in SCOM 2012 R2.

Top Issue Fixes

  • The “Remove-DisabledClassInstance” Windows PowerShell command times out without completing – In large SCOM deployments this cmdlets sometimes times out without completing. This release addresses same by optimizing the underlying query.
  • Duplicate closed alerts – Due to an update issue in the grid, Find option in a message view duplicates results with a previous search and it is fixed to display only the current search results.
  • Topology widget objects lose location when they are opened in a console that has a different locale and decimal format – In this release users can create widgets in different locale where in previous releases it will display incorrect loacle settings in the original local is different.
  • WebConsole Details widget does not display anything – This issue is fixed by fixing the XAML page of the details widget. The XAML page was preventing the data from being displayed on the page.
  • Top 10 Performance widgets (WebConsole) are sometimes empty – Due to an performance issue the Top 10 Performance Widgets in Web Console are empty sometimes. In UR3 we had to manually import a mpb file to fix this. This release has the fix integrated.
  • Problem with decoding SCOM trace log files – SCOM trace logs do not decode but generate the error “Unknown(X ): GUID=XXX (No Format Information found).” when the latest TMF files that contain formatting information for the related traces are missing. In this version All TMF files are updated.

Following issues have been addresses in Unix/Linux MP.

  • JEE: WebLogic 12.1.3 servers on Linux or Solaris are not discovered – In order to solve this issue you need to update the SCOM Agent in target Unix/Linux Servers after updating to the latest Unix/Linux MP.
  • In rare cases, lots of omiagent processes may be observed on a UNIX or Linux computer – Requires the Management Pack Update as above.
  • The SSLv3 protocol cannot be disabled in OpenSSL as used by the UNIX and Linux agents – By modifying the NoSSLv3=<true|false> in omiserver.conf (/etc/opt/microsoft/scx/conf) you can disable SSL v3 in Unix/Linux Monitoring agents. By default ISSLv3 is enabled and will be used only if TLS encryption cannot be negotiated. Otherwise the  agent rejects connections that cannot be negotiated by using TLS encryption.

Installation Procedure

If you have past experience in installing an Update Rollup for SCOM 2012 R2 the procedure is same. You can refer my previous post as a reference. You can download the binaries for a manual installation which I strongly recommend from here.

However for Unix/Linux servers after updating to UR6 make sure you import the latest MP for each version of Unix/Linux OS. You can download the latest Management Pack from here. Finally you have to update the the monitoring agent in those *nix servers.

DPM 2012 R2 UR5 Console Crashing Issue

A known issue has been identified in the latest Update Rollup for Data Protection Manager 2012 R2. Let’s see what is this issue and how to rectify same in this article.

Issue

When you are working in local DPM server or an attached secondary DPM server you may notice that the console crashes basically when you are searching through something or navigating from one section. Int his case even if you resatrt the console it becomes unresponsive and also cmdlets also enter the same state

The Hotfix

Microsoft has released a hotfix package KB3040326 which address the above issue. Note that before you apply this hotfix you’ll have to backup the DPMDB database and after installing the hotfix you need to reboot the DPM server/s.

In my personal experience I would recommend you to wait a while before you apply UR5 in production systems until UR6 is released. But since UR5 has lot of improvements in new workload backups you may want to reconsider that option. For a list of new features in UR5 you can refer DPM Team’s announcement.

MOM Agent Update Rollup KB 3032946 released

Few days ago Operations Manager Engineering team has announced the availability of a new update rollup for MOM agent. This update rollup fix below mentioned issues that are present in the current version.

  • Proxy settings are now in Agent setup wizard. Earlier users had to manually enable the agent proxy in each agent after installation but in this update you can enable it while pushing agents.
  • Account Validation steps are added. Once a user enters the Azure Operational Insights credentials to connect, credentials are validated before proceeding.
  • Connection Status in Control Panel. Now you can see the connection status of an agent in the Control Panel settings of the MOM Agent.

You can manually download the KB 3032946 from Microsoft Update catalog by visiting here or you can obtain it via Microsoft Update (Optional Updates) if your update service is configured to receive updates for other Microsoft software.

 

Tips from field for SCOM 2012 R2 Update Rollup Installation

Every software needs to be up-to-date in order for their proper functionality. SCOM is no different in this case. Let’s see how applying an Update Rollup can be done in the proper way for SCOM 2012 R2.

I have explained this scenario based on SCOM 2012 R2 UR4 but the process is much similar for UR5 as well.

Performing the Update Rollup Installation

Below is the list of steps that you need to follow when performing a UR installation.

Apply MSPs to relevant server roles

First of all you have download the relevant update packages for the particular UR. If your SCOM servers are configured to receive updates directly from Microsoft Update (WSUS or Internet) for System Center Products you can go ahead and approve the relevant update packages. Here I’m referring the manual method of update installation as most servers are configured with strict update policy.

You can download UR4 update package from here. In UR4 there are 5 updates but based on your deployment you’ll have to apply the updates. As an example no need to apply Web Console update if you haven’t deployed that component in your SCOM environment. After you have downloaded the packages extract them to a central location.

Before you proceed with applying the MSPs perform below tasks.

    • Make sure all servers are up-to-date with latest patch updates.
    • Close SCOM Console if it is running in all servers.
    • In some cases you will have to stop System Center Data Access Service and System Center Management Configuration service on all management servers. But it wasn’t necessary in my case.

To apply the MSPs follow below procedure.

    • Open a Command Prompt with Elevated Rights (as Administrator)
    • Browse to the location where you have extracted the MSPs.
    • Install the MSP from command prompt. There won’t be any notification once it is installed other than it returning a blank cursor. But you can notice file version changes when you install each MSP as described in Kevin Holman’s Blog. Kevin’s post was focused on UR4 but the idea is same. Build numbers for SCOM 2012 R2 as follow and you can see same when you check the file versions as described in Kevin’s blog.
Build Number KB Release Date Description
7.1.10226.0 SCOM 2012 R2 RTM
7.1.10226.1011 KB2904678 2014, January 27 SCOM 2012 R2 Update Rollup 1
7.1.10226.1015 KB2929891 2014, April 23 SCOM 2012 R2 Update Rollup 2
7.1.10226.1037 KB2965445 2014, July 29 SCOM 2012 R2 Update Rollup 3
7.1.10226.1046 KB2992020 2014, October 28 SCOM 2012 R2 Update Rollup 4
7.1.10226.1052 KB3023138 2015, February 10 SCOM 2012 R2 Update Rollup 5

Install the MSPs in below order (Yes the order matters)

  • Management server or servers
  • Gateway servers
  • Web console server role computers
  • Operations console role computers

021715_0624_Tipsfromfie2.pngCheck whether Particular UR has been installed successfully

Once you have installed the MSPs it’s critical that we check whether the installation was successful as intended. There is an excellent PowerShell script written by Jure Labrovic which can be found in TechNet Gallery which will help you to achieve this. Note that this script is validating against UR4 bust it’s just a matter of tweaking the script to make it work for UR5. I did not use Operations Manager Shell but I did use regular PowerShell with administrator elevation. (You may need to Set-ExecutionPolicy to Unrestricted if you already haven’t done that.)

Here is my result when I run this script in one of my management servers.

Execute SQL scripts on SCOM databases

This part is rather is but you need to do several important tasks that you need to perform before you do so.

    • Stop System Center Data Access Service and System Center Management Configuration service on all management servers.
    • Perform a full backup of both OpeartionsManager & OperationManagerDW databases. This is just in case if anything goes wrong.

Here is how you execute the SQL scripts.

    • You can find the scripts at %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\ in any management server that you have updated with MSPs.
    • There are two scripts that need to be executed. Execute Update_rollup_mom_db.sql in OperationsManagerDB and UR_Datawarehouse.sql in OperationsManagerDW.
    • If you get a warning about line endings, choose Yes to continue.021715_0624_Tipsfromfie4.png
    • If you get an error when you run any of the scripts do not continue. Try running same multiple time before you move into the other script. Usually this happen if you haven’t stopped the services in management servers which results in deadlocks in the databases.
    • You will see an output similar to below if everything went smoothly.021715_0624_Tipsfromfie5.png

Manually Import Management Packs

Now you have to manually import some management packs that were updated in the UR. These can be found at %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups. Here is the list of MPs that you need to import in UR4.

  • Microsoft.SystemCenter.TFSWISynchronization.mpb (There is a dependency Microsoft.SystemCenter.AlertAttachment.mpb for this MP. This can be found in Installation media for SCOM 2012 R2)
  • Microsoft.SystemCenter.Visualization.Library.mpb
  • Microsoft.SystemCenter.Visualization.Component.Library.mpb
  • Microsoft.SystemCenter.Advisor.mpb
  • Microsoft.SystemCenter.Advisor.Internal.mpb
  • Microsoft.SystemCenter.2007.mp

Apply agent update to manually deployed agents

For agents that you have previously installed via push installation, you will notice that they are under Pending Management view now. You can approve them to update the MOM agent. For manually installed agents you will have to install the updated agent which can be found in SCOM installation path of any management servers.

Update Linux/Unix MP and update *nix agents (Optional)

This is an optional step if you have deployed *nix agents. More information can be found in this KB article.

And that’s how we deploy a UR for SCOM 2012 R2.

System Center 2012 R2 Update Rollup 4 is now available

During the breakout of TechED Europe 2014 we got some fantastic news on Microsoft technologies and the announcement for System Center 2012 R2 UR4. It seems every product except Orchestrator and Configuration Manager got something new. I thought giving you all little insight on what this means for two products that I’ve been working on.

Virtual Machine Manager

VMM now officially supports 64 bit versions of below Linux distributions to run as guest OS.

  • Red Hat Enterprise Linux 7
  • Oracle Linux 7
  • CentOS Linux 7

Also there is number of bug fixes that has been done with this version. You can find all the details from here.

Data Protection Manager

  • SQL 2014 workload protection is now available. But SQL 2014 is not supported as the backed database for DPM.
  • Both workload protection and to use it as DPM configuration database for SQL 2012 SP2 is available.
  • Simplified process to register a DPM server with a Azure Backup Vault.

It’s always better to wait a few days to apply this UR, I would do it in a test lab first to see for any issue. You can download the documentation and relevant update packages from here.

System Center 2012 R2 Update Rollup 3 | New Features

Two weeks ago, Microsoft has released UR3 for System Center 2012 R2. This was a much awaited update as it fixed number of issues with related to system center products. Update Rollups are set of cumulative fixes targeted at specific product which fix the bugs and add new features/functionality to the products. Lets see what are the new features that came up with UR3.

Brand new Office 365 Management Pack

This is  a life saver. Previously admins had to log in to Office 365 management portal to view the tenant health, any ongoing issues or service outages. With the release of Office 365 Management pack they can leverage SCOM to do the monitoring on behalf of the Office 365 tenant. Individual services like Exchange Online, Lync Online, SharePoint Online can be thoroughly monitored with any active incidents occurred on same. Also you can view details related to service health, service interruption corresponding to the Office 365 services along with important service messages from Microsoft. In simple words, your Office 365 dashboard can now reside in SCOM. We are going to discuss how we can import and configure this MP in a later post.

Office 365 MP Dashboard in SCOM 2012 R2

Resource Visualization dashboards for VMM

We have two new dashboards that can display resource utilization of your Virtualization Hosts & VMs . You can view the health of the list of Hosts and their performance counters. This can also provide overall health status of a VM (Red, Green, Amber colour code). We will discuss how to install and configure the Resource Visualization Pack for VMM in a later post.

VMM Resource Visualization Dashboard
VM health view

Resources

  1. Office 365 Management Pack for SCOM 2012
  2. VMM Resource Visualization Pack