SCOM (Anglais)

Unlocking the full potential of System Center Operations Manager: introducing the free Squared Up Community Edition license

Microsoft Operations Manager and OMS -

This is a special guest blog from Squared Up

Since founding Squared Up in 2011, we’ve been on a mission to transform the way enterprises interact with their monitoring data and, in doing so, have enabled hundreds of clients worldwide to unlock the full potential of System Center Operations Manager (SCOM).

 “Together with SCOM, Squared Up is a key component in our strategy to deliver end-to-end monitoring for our entire set of enterprise applications – Shawn Williams, Systems Engineer, ITaP, Purdue University.”

We’ve always believed that no other enterprise-class monitoring tool offers the same power, flexibility and sheer breadth and depth of cross-platform monitoring capabilities as SCOM. Because of this, we believed that by building on top of SCOM we could take on the huge challenges of application monitoring in the enterprise environment.

“Blackboard is one of our key-line-of-business applications and SCOM, together with third party Management Packs, is able to provide us with detailed insights across the entire stack, from our F5s at the front-end, all the way through to the virtualization at the backend, and all of that data is then surfaced via Squared Up – Shawn Williams, Systems Engineer, ITaP, Purdue University.”

First up, we delivered a blazingly-fast, multi-platform HTML5 web console, which we then enhanced with powerful new features like interactive performance reporting from the Data Warehouse, export to Excel, seamless Visio integration and, above all, the ability to easily build and publish custom dashboards.

 

“One of the first things Squared Up allowed us to do was much more easily expose availability and uptime reporting to the wider business, both at a managerial level and for our Service Desk –  Shawn Williams, Systems Engineer, ITaP, Purdue University.”

With the simultaneous release of SCOM 2016 and Squared Up Version 3.1, we’ve now taken things to the next level.

Working in close conjunction with the SCOM Engineering Team and leveraging the significant performance enhancements introduced in SCOM 2016, Squared Up is now faster and more powerful than ever.

Taking full advantage of SCOM’s extremely powerful capabilities, Squared Up goes far beyond just enabling HTML5 access, allowing you to:

–  Dynamically map your applications and view live health states across the full stack, irrespective of the underlying technologies, all powered by your existing SCOM Agent.

 

 

“VADA is a tremendously powerful tool, allowing us to get a definitive handle on the exact topology and dependencies of all of our applications, of which there are several hundred – Shawn Williams, Systems Engineer, ITaP, Purdue University.”

– Integrate OMS and unify SCOM and OMS data behind a single-pane-of-glass User Interface

“As our monitoring strategy evolves, OMS is now starting to supplement our SCOM data with things like Security & Audit and Change Tracking, which will provide us with value-add insights on top of our existing SCOM data. The key to realizing that value is being able to deliver the data to our users in a single-pane-of-glass UI thanks to Squared Up – Shawn Williams, Systems Engineer, ITaP, Purdue University.”

– Provide top-to-bottom, full-stack visibility via technology-specific, customised drilldowns

 

 

“The speed, ease of use and vendor-neutral nature of Squared Up means we’ve been able to successfully bring non-Microsoft engineering teams – such as our Linux teams – into our SCOM-centric monitoring strategy, with a common portal through which all of our cross-platform monitoring data is consumed. That really helps in our efforts to break down siloed thinking and “Us versus Them” mentality within the organization – Shawn Williams, Systems Engineer, ITaP, Purdue University.”

We’re now five years into our mission to radically change the landscape of enterprise monitoring and, together with the release of SCOM 2016 & Squared Up Version 3.1, we believe this marks the perfect moment to unlock the potential of SCOM for literally every customer worldwide.

So, together with the support of Microsoft, we’re delighted to unveil our new, completely free, Community Edition license, which supports both SCOM 2012 and SCOM 2016, and allows you to deliver;

– Full HTML5 Web Console for SCOM

– Unlimited custom dashboards

– Interactive Performance Reporting from the Data Warehouse

– Visio Integration

– Data on Demand

– Total Dashboard Architecture

– Mobile & Tablet Access

– and lots, lots more

You can read more about our Community Edition license and request one for yourself via our website.

We’re looking forward to welcoming you into our Community and to helping you solve the challenges of Enterprise Application Monitoring.

APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime

Microsoft Operations Manager and OMS -

Summary

APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime.

Cause

Several callbacks within APM code of SCOM 2016 Agent utilize memory allocation that’s incompatible with .NET 2.0 runtime and may cause an issue if this memory is later accessed in a certain way. Those particular modifications were added in SCOM 2016 Agent and are not present in SCOM 2012 R2 Agent.

Resolution

The fix for this issue is to be provided with SC 2016 OM Update Rollup 3. The aforementioned code paths will not be executed if the Application Pool is running under .NET 2.0 Runtime. We are also evaluating to release a hotfix for this issue.

Workaround

There are several workarounds for this issue:

  • Application pool can be migrated to .NET 4.0 Runtime;
  • SCOM 2016 Agent can be replaced with SCOM 2012 R2 Agent, it’s forward-compatible with SCOM 2016 Server and APM feature will continue to work with the older bits;
  • SCOM 2016 Agent can be reinstalled with NOAPM=1 switch in msiexec.exe setup command line, APM feature will be excluded from setup;

Deprecating SHA1 Certificates in System Center Operations Manager for UNIX/Linux Monitoring

Microsoft Operations Manager and OMS -

 

The communication between System Center Operations Manager Management Server and the UNIX/Linux agents are secured with TLS/SSL. UNIX and Linux agents employ Server Authentication certificates (i.e. “agent certificates”) for the TLS/SSL channel and these certificates are signed by an Operations Manager Management Server’s “signing certificate.” As of System Center 2016 RTM, both agent certificates and signing certificates are generated with the sha1WithRSAEncryption signing algorithm. With System Center 2012 R2 Operations Manager UR12 and System Center 2016 Operations Manager UR2, use of SHA1 certificate would be deprecated with a default preference for SHA 256 certificate. Customers can now update and sign their certificates on currently deployed agents by following the below procedure.

  1. Install SCOM 2012 R2 UR12 – https://support.microsoft.com/en-us/help/3209587/system-center-2012-r2-om-ur12 (or) SCOM 2016 UR2 – https://support.microsoft.com/en-us/help/3209591/update-rollup-2-for-system-center-2016-operations-manager
  2. Import the UNIX/Linux Management packs for SCOM 2012 R2/SCOM 2016 UR2 – https://www.microsoft.com/en-in/download/details.aspx?id=29696
  3. Certificate can be updated from SHA1 to SHA 256 in one of the following ways

Option1:

Use the powershell script UpdateXplatCertificates.ps1. This when used without any parameters will update the certificate for all the agents.

.\UpdateXplatCertificates.ps1

This script can be downloaded from here.

Option2:

To update the certificate for specific agents use the below command

.\UpdateXplatCertificates.ps1 -AgentsDisplayName “<Agent1>“,”<Agent2>”

Option 3:

Certificate can be updated through SCOM Console –

Console –> Monitoring –> UNIX/Linux Computers –> select the server.

 

On the right task pane under UNIX/Linux Computer Tasks there are two tasks that could be performed.

 

  1. Verify Certificate Signature – This task is used to verify the Signature algorithm of the agent’s signed certificate. This can be helpful in identifying SHA1 certificates that requires an update.On clicking Verify Certificate Signature you would get the below screen and the results.

         2. UNIX/Linux Update Certificate Task – This task updates the certificate from SHA1 to SHA 256.Click the server you wish to update the certificate and click UNIX/Linux Update    Certificate Task in the task pane.     

 

 

Please note:

 Already existing certificate will not be invalidated or deleted. Once the customer updates the certificate for all their monitored servers, the old certificates should be manually deleted.

 Once SCOM 2012 UR12 or SCOM 2016 UR2 is installed, the SHA 256 certificate will be used by default for newly discovered servers.

 User would need to update the certificate the same way for high availably configuration too.

Engyro Product Connector support ending this year

Microsoft Operations Manager and OMS -

The Engyro Product Connector for Microsoft System Center Operations Manager 2007 will no longer be supported after July 11, 2017.  If you are using this product connector, please upgrade to System Center 2016 Operations Manager and integrate with a third-party connector as needed. Alternatively, you can use System Center Orchestrator and custom runbooks to integrate with third-party enterprise ITSM/monitoring systems using an integration pack from Microsoft or our partner Kelverion.  For more information about Engyro, please see the Engyro Support Bulletin from 2010.

Review these instructions for upgrading to System Center 2016 Operations Manager. If you are using Operations Manager 2007, this requires the following upgrade process: upgrade to Operations Manager 2007 R2, to System Center 2012 Operations Manager, to System Center 2012 R2 Operations Manager, then to System Center 2016 Operations Manager.

Microsoft System Center 2016 Operations Manager Integration packs

Kelverion Integration packs

Have questions about supported products? Visit Microsoft Support Lifecycle to view a list of supported products and related policies.

Update Rollup 8.0.11030.0 for the Microsoft Monitoring Agent is now available

Microsoft Operations Manager and OMS -

Update rollup version 8.0.11030.0 for Microsoft Monitoring Agent is now available. The article below describes the issues that are fixed and also contains installation instructions. For complete details please see the following:

3206063Update rollup 8.0.11030.0 for Microsoft Monitoring Agent (KB3206063) (https://support.microsoft.com/en-us/kb/3206063)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

OpsMgr 2012 R2

How to revert to a previous version of a Microsoft Operations Manager Management Pack

Microsoft Operations Manager and OMS -

~ Chandra Bose | Senior Software Engineer

There are times when you may want to revert back to older version of a Management Pack (MP) for a given workload. Currently, the Operations Manager UI allows you to delete and re-import Management Packs from the “Installed Management Packs” screen, however there can be issues when there are multiple and multi-level dependencies on the MP that you are trying to delete.

To mitigate these potential issues, we have a new script available that will help you to revert Management Packs with ease.

Note that this script is an enhanced version  of an earlier script provided by its original author here (thanks to Microsoft’s own Christopher Crammond!)

Here’s how to use the script:

1. Open the Operations Manager Command Shell prompt in Administrator mode.

2. Download the script to remove a management pack with dependencies from here.

3. Run the script using the name of the Management Pack you want to remove. For example:

(Example 1) –> .\RecursiveRemove.ps1 <ID or System Name of the MP>

(Example 2) –> .\RecursiveRemove.ps1 Microsoft.SQLServer.2014.Discovery

You can see the ID or System Name of the MP that you want to uninstall by selecting it in the Installed Management Packs view by clicking Properties in the Actions pane. Simply copy the content in the “ID :” text box in the General tab.

Chandra Bose | Senior Software Engineer | Microsoft

OpsMgr 2012 R2 OpsMgr 2007 OpsMgr 2016

S'abonner à Philippe BARTH agrégateur - SCOM (Anglais)