SCOM (Anglais)

Global Service Monitor to Retire in November 2018

Microsoft Operations Manager and OMS -

System Center Operations Manager continues to be the tool relied upon by enterprise customers for IT operations and monitoring. Global Service Monitor in SCOM provides the ability to monitor the availability of external web-based applications from multiple locations across the globe. As of November 07, 2018, we will retire the Global Service Monitor and recommend that customers transition Global Service Monitor users to next generation web application monitoring capabilities allowing them to take advantage of our Azure hosted services for these capabilities, powered by Azure Application Insights.

Application Insights is an extensible Application Performance Management (APM) service for monitoring applications on multiple platforms. It offers greater control, and richer alerting, diagnostics, dashboarding and reporting capabilities over an interactive data analytics platform. With the transition to Azure Application Insights, customers stand to benefit in the long term from Azure monitoring investments including improvements in reliability and performance.

GSM Customers will be notified of the retirement through an alert in the SCOM console sent down from the GSM. If you are a GSM customer, during your transition, you do not need to change your tests; Application Insights supports the tests GSM supported (single URL ping and multi-step web tests), the frequency of the tests and locations supported are the same as well. The migration script (Link to Migration Script) will provision your tests with the same configuration in Application Insights. The migration script will also provision alert rules based on what you are currently using in SCOM . Please use the migration script to migrate your GSM tests to Application insights by the end of October 2018. Post migration, SCOM customers can use the Azure Management Pack (CTP version) (Link to Azure MP) to integrate with Application Insights and view the alerts from their tests in Application Insights in the SCOM console.

We thank the SCOM customers for their usage of the GSM service. This transition provides yet another value to System Center customers as they continue to be able to take advantage of Azure management offerings. Should you have any questions, please contact your account team or Microsoft Support.

FAQ

  1. What is GSM?

System Center Global Service Monitor is a cloud service that provides a simplified way to monitor the availability of external-web-based applications from multiple locations around the world. See https://technet.microsoft.com/library/jj860368(v=sc.12).aspx.

  1. What is Azure Application Insights?

Application Insights is an extensible application performance monitoring service in Azure, supporting applications on a variety of platforms. See https://azure.microsoft.com/services/application-insights/

  1. Does my price increase because of this transition?

GSM was provided as a software assurance benefit of your System Center purchase. When you migrate to Azure Application Insights, Microsoft will transition migrated tests and alert rules at no additional charge

  1. Do I get any other Azure benefits as part of this transition?

No. Only the migrated tests, and the alert rules associated with them will be provided at no additional charge. All other Azure consumption will be subject to applicable pricing.

  1. So, if I add more availability tests or use Application Insights for server-side monitoring, I will be charged?

Yes, that is correct. Only the migrated tests are provided at no additional charge. All other use is subject to applicable pricing.

  1. What happens if I don’t migrate the tests?

Existing GSM tests will stop working after 11/07/2018. We strongly encourage you to migrate the tests and validate the alert rules in Azure well before that date.

  1. What happens if I don’t migrate tests using the migration script provided by Microsoft?

Only the tests which are migrated using the script, would be provided at no additional charge in Azure Application Insights.

Microsoft System Center Operations Manager Management Pack to configure Operations Management Suite

Microsoft Operations Manager and OMS -

We have updated Operations Management Suite connection onboarding wizard in System Center Operations Manager to communicate with the new APIs.

For configuring new connections to Operations Management Suite with System center Operations Manager, you need to import the product version specific management packs (links given below). If you have already configured connection to OMS with SCOM then you do not need to import these management packs, however if you reconfigure your existing connection then you need to import this management pack.

New Operations Management Suite onboarding wizard in System center Operations Manager:

Download links:

  • For System Center Operations Manager 1801, download the management pack from here.
  • For System Center 2016 Operations Manager, download the management pack from here.
  • For System center 2012 R2 Operations Manager, download the management packs from here.

System Center Operations Manager 1807 is released!!

Microsoft Operations Manager and OMS -

System Center Operations Manager 1807 overview

System Center 1807 announcement is available here.

What’s new in System Center Operations Manager 1807 is available here.

How to Upgrade to System Center Operations Manager 1807 is available here.

The content in this blog describes the features and scenarios enabled in System Center Operations Manager 1807

HTML5 dashboards

Users can create and manage PowerShell Widgets in their HTML5 dashboards. While authoring the PowerShell widget, user needs to provide the PowerShell script which would be executed and visualized in the widget. This widget enables users to leverage PowerShell scripting to retrieve and visualize custom data (more details on PowerShell widget is available here).

Users can visualize effective configuration for a server/object in the objects drill down page. This allows users to view the configuration of a rule/monitor with respect to a server or an object.

More details on viewing effective configuration of a monitored object is available here.

Operators can create/manage HTML5 dashboards in MyWorkspace. This feature allows operators to create and visualize dashboards (only with the data they have access to) in the form they like (more details on creating dashboards in My Workspace is available here).

User can Visualize Network Node dashboard and Network Interface dashboard for Network Node/interface from the Objects drill down page. This allows users to consume more relevant data while trouble shooting a network node or interface.

User can navigate to the objects drill down page of the alert and change the resolution of an alert from within the alert down page. This allows users to act on an alert while troubleshooting the same.

More details on the changes to alerts drill down page is available here.

User can select/change the size of the icon in topology widget, allowing flexibility to have bigger icons for NOC view scenarios.

More details on changes to topology widget is available here.

Schedule Maintenance Mode view in Web Console

This feature enables users to create and manage schedule maintenance mode from within the web console.

More details on creating/managing schedule maintenance from web console is available here.

User can choose to enable/disable APM component while installing agent

This feature allows more flexibility to the users by providing an option to enable/disable APM component in the agent.

User can enable/disable APM component while installing agent through Discovery wizard (more details are available here).

User can enable/disable APM component through the agent repair wizard (more details are available here).

User can enable/disable APM component through the new parameter added for the below cmdlets:

Install-ScomAgent

Example:

  • Without APM: Install-SCOMAgent -DNSHostName “NEB-OM-1536628.smx.net” -PrimaryManagementServer $PrimaryMS -NoAPM
  • With APM:       Install-SCOMAgent -DNSHostName “NEB-OM-1536628.smx.net” -PrimaryManagementServer $PrimaryMS)

Repair-ScomAgent

Example:

  • Without APM: Get-SCOMAgent -DNSHostName “NEB-OM-1536628.smx.net” | Repair-SCOMAgent -NoAPM
  • With APM:       Get-SCOMAgent -DNSHostName “NEB-OM-1536628.smx.net” | Repair-SCOMAgent)
Support for SQL 2017 with SCOM 1807

With SCOM 1807, SQL 2017 is supported if it is upgraded from SQL 2016. Fresh installation of SQL 2017 with SCOM 1807 is not supported with SCOM 1807.

More details on upgrading Operations Manager 1807 database to SQL Server 2017 is available here.

XPlat log rotate

Under error scenarios, the SCX log fills up quickly, which eventually consumes all available free space on the system disk. As a result, the system becomes unresponsive unless the logs are cleaned up manually. To address this issue, we have introduced log rotate feature for SCX agent. This will help to rotate old logs of SCX agent and save disk space.

More details on Log rotation for Linux agent is available here.

MP Author Version 8.2

Microsoft Operations Manager and OMS -

The following is a special guest blog from Silect

We are pleased to announce the General Availability of MP Author version 8.2. We’ve made lots of updates and improvements to our family of products for SCOM. Here’s a summary of the changes to MP Author:

  • Support for SCOM 1801
  • When sealing and deploying and MP, deploy the sealed MP, not the unsealed.
  • Remember the last SCOM version used when creating an MP, as it should be the default next time. Improve display and logging of the versions of reference MP that are loaded.
  • Groups can now be created without dynamic membership rules.
  • Improved impersonation when browsing remote registries.
  • When parsing scripts for class names, parameters, etc. allow both single and double quotes.
  • When displaying lists of targets, ensure the list shows abstract and singletons if needed.
  • Several dialogs and message boxes now allow you to not show them again (once you know what they are telling you, you can select a “Don’t Show This Again” check box.)
  • Discoveries can now be enabled for a group from within the wizard.
  • Alert, Event, Performance and State views can now be filtered by a group.
  • Editing event, performance, service or process rules/monitors will work correctly even if the machine being browsed doesn’t have the items previously selected.
  • Performance monitors now support two and three-state monitors using simple values, average values, delta values, or consecutive samples.
  • Script monitors and rules allowed overrides on the parameter values but did not use the override value. This has been corrected.
  • Setting a description for an element which does not have a display name failed. The new behaviour is to set the missing display name (to the actual name) at the same time.
  • Do not require hosted classes with no key properties to be singletons because the hosting class may have key properties.
  • Improve handling of reference MPs which don’t exist or are the wrong version.
  • Allow registry and WMI queries to work if they contain characters which are significant in XML (like < or >).
  • The script class wizard will no longer allow users to change the class name, if the class name was determined from the script (if they don’t match, the discovery will fail).
  • Numerous bug fixes, UI and performance improvements
S'abonner à Philippe BARTH agrégateur - SCOM (Anglais)