Tag Archives: #2012 R2

SCOM: Update OpsLogix Swift Management Pack V2.5.1.57

OpsLogix has announced an update to their Swift Management Pack V2.5.1.57 it is available in their customer download area

Changes in this version:

  • System Center Operations Manager 2012 contains a bug that prevents alert subscriptions form filtering variable text fields. This release of the Swift management pack offers a workaround by adding the description to “Custom Field1″ of the alert so that it can be filtered in the alert subscriptions.

Loading

SCOM 2012 R2: Update rollup 8 has been released

Microsoft has released update rollup 8 for SCOM 2012 R2. As usual the update can be obtained through Windows update for the update catalog.  The update gives additional certification for network devices as well as several bug and performance fixes.

Issues that are fixed in this version

  • Slow load of alert view when it is opened by an operator
    Sometimes when the operators change between alert views, the views take up to two minutes to load. After this update rollup is installed, the reported performance issue is eradicated. The Alert View Load for the Operator role is now almost same as that for the Admin role user.
  • SCOMpercentageCPUTimeCounter.vbs causes enterprise wide performance issue
    Health Service encountered slow performance every five to six (5-6) minutes in a cyclical manner. This update rollup resolves this issue.
  • System Center Operations Manager Event ID 33333 Message: The statement has been terminated.
    This change filters out “statement has been terminated” warnings that SQL Server throws. These warning messages cannot be acted on. Therefore, they are removed.
  • System Center 2012 R2 Operations Manager: Report event 21404 occurs with error ‘0x80070057’ after Update Rollup 3 or Update Rollup 4 is applied.
    In Update Rollup 3, a design change was made in the agent code that regressed and caused SCOM agent to report error ‘0x80070057’ and MonitoringHost.exe to stop responding/crash in some scenarios. This update rollup rolls back that UR3 change.
  • SDK service crashes because of Callback exceptions from event handlers being NULL
    In a connected management group environment in certain race condition scenarios, the SDK of the local management group crashes if there are issues during the connection to the different management groups. After this update rollup is installed, the SDK of the local management group should no longer crash.
  • Run As Account(s) Expiring Soon — Alert does not raise early enough
    The 14-day warning for the RunAs account expiration was not visible in the SCOM console. Customers received only an Error event in the console three days before the account expiration. After this update rollup is installed, customers will receive a warning in their SCOM console 14 days before the RunAs account expiration, and receive an Error event three (3) days before the RunAs account expiration.
  • Network Device Certification
    As part of Network device certification, we have certified the following additional devices in Operations Manager to make extended monitoring available for them:

    • Cisco ASA5515
    • Cisco ASA5525
    • Cisco ASA5545
    • Cisco IPS 4345
    • Cisco Nexus 3172PQ
    • Cisco ASA5515-IPS
    • Cisco ASA5545-IPS
    • F5 Networks BIG-IP 2000
    • Dell S4048
    • Dell S3048
    • Cisco ASA5515sc
    • Cisco ASA5545sc
  • French translation of APM abbreviation is misleading
    The French translation of “System Center Management APM service” is misleading. APM abbreviation is translated incorrectly in the French version of Microsoft System Center 2012 R2 Operations Manager. APM means “Application Performance Monitoring” but is translated as “Advanced Power Management.” This fix corrects the translation.
  • p_HealthServiceRouteForTaskByManagedEntityId does not account for deleted resource pool members in System Center 2012 R2 Operations Manager
    If customers use Resource Pools and take some servers out of the pool, discovery tasks start failing in some scenarios. After this update rollup is installed, these issues are resolved.
  • Exception in the ‘Managed Computer’ view when you select Properties of a managed server in Operations Manager Console
    In the Operations Manager Server “Managed Computer” view on the Administrator tab, clicking the “Properties” button of a management server causes an error. After this update rollup is installed, a dialog box that contains a “Heart Beat” tab is displayed.
  • Duplicate entries for devices when network discovery runs
    When customers run discovery tasks to discover network devices, duplicate network devices that have alternative MAC addresses are discovered in some scenarios. After this update rollup is installed, customers will not receive any duplicate devices discovered in their environments.
  • Preferred Partner Program in Administration Pane
    This update lets customers view certified System Center Operations Manager partner solutions directly from the console. Customers can obtain an overview of the partner solutions and visit the partner websites to download and install the solutions.

Loading

SCOM: Updated SharePoint 2010 Products Management Pack 14.0.7137.5000

The MP for SharePoint 2010 Products  14.0.7137.5000 was updated to fix a bug in the service discovery it is available for download here

This update contains a bug fix:

  • SharePoint 2010 MP had a PS1 file with syntax error causing the shared service discovery to fail. With this fix the PS1 file syntax error is resolved and the discoveries will be made.

Loading

SCOM: SQL Server MP updates v6.6.2.0

Microsoft has just released version 6.6.2.0 of the SQL management packs listed below. This updated contains fixes to many of the issues plaguing the previous version, of course test before using in your production environments.

SQL Server 2014 Replicationdownload here
SQL Server 2012 Replicationdownload here
SQL Server 2008 Replication download here
SQL Server 2014download here
SQL Server 2012/2008/2003download here

Updates and Fixes in this version:

First the dashboards which had many issues in the original release.

  • Improved performance
  • Objects with selected monitors are now displayed on the top of the tiles list while editing
  • If there are no child elements, Related Objects tile is not displayed in Instance View.
  • Added Dark, Light and Contrast themes.
  • Introduced an interface upgrade allowing to display the Dashboard errors
  • User rights are now considered in the Dashboard display: the user can see the groups according to his/her access level only; Read-Only mode is implemented, it provides basic functions only: navigation, changing of the personalization settings
  • Fixed some UI errors, UI design upgraded
  • Fixed synchronization errors of the personalization settings.
  • Introduced a Dashboard feature allowing to display data from any nesting level within the widgets

SQL Server 2012/2008/2003

  • Added a support for disabled TCP/IP protocol
  • Fixed performance metrics error that may occur on some localized versions of Windows
  • Fixed bugs in monitor tiles on SQL Server Summary Dashboard
  • Fixed incorrect performance of Transaction log free space monitor
  • Added new type of events from failed discoveries; added a new rule that collects such events
  • Added overrides to prevent various scripts timeout failure
  • Removed some 1X1 tiles from Summary Dashboards
  • Filestream filegroups are excluded from discovery for now
  • 2008/2012 Summary Dashboards tiles were reorganized

SQL Server 2014

  • Fixed performance
  • Added a support for disabled TCP/IP protocol
  • Fixed performance metrics error that may occur on some localized versions of Windows
  • Fixed incorrect performance of Transaction log free space monitor
  • Added new type of events from failed discoveries; added a new reporting rule that collects such events
  • Added overrides to prevent various scripts timeout failure
  • Removed some 1X1 tiles from Summary Dashboards
  • Filestream filegroups are excluded from discovery for now
  • 2008/2012 Summary Dashboards tiles were reorganized
  • Added KB for Microsoft.SQLServer.2014.Mirroring.MirroringCommonGroupDiscovery
  • Summary Dashboard: added monitor/performance tiles to class “SQL Server 2014 Mirroring Groups”
  • Some minor fixes

SQL Server Replication MPs

  • Preset dashboards are updated

Loading

SCOM: Updated MP for Windows Server 2012 DHCP v6.0.7295.0

We also have a new management pack for Windows Server 2012 DHCP being released this month, version 6.0.7295.0 can be found here

New features and updates:

  • The properties view of Failover Server Relationship does not display all the IP addresses, with this fix the properties view of Failover Server Relationship will display all IP addresses.

Loading

SCOM: Alerting on Exchange 2013 Database Failover

As it turns out the Exchange 2013 MP will not be able to alert you should your Exchange 2013 databases fail over, this is by design, as Microsoft does not consider this condition to be an issue.

There is a great article by Scott at flobee.net which addresses this issue for Exchange 2010, it is quite simple to apply the same thinking for use with Exchange 2013. The event is the same, the target just needs to be Exchange 2013 server.

Screenshot-FailoverAlert2

 

Loading

SCOM: The System Center Management service terminated with service-specific error %%-2130771964

Just a quick issue which bares being noted.

A colleague of mine had an issue where the health service on one of his management servers would not start. The error displayed was “The System Center Management service terminated with service-specific error %%-2130771964″

The resolution is simple, rename the Health Service State folder and then start the service.

This issue is caused by corruption in the health service cache which is preventing the service from starting,

Loading

SCOM: Error in SNMP GET response from IP Address: Status: noSuchInstance(129)

Today I was addressing this error in the Operations Manager event log at one of my customers:

Error in SNMP GET response from IP Address: Status: noSuchInstance(129)

According to What Gets Monitored with System Center Operations Manager 2012 Network Monitoring this can be caused by several things:

Possible Resolutions

  • Stale Discovery Data – Device has been reconfigured since the last discovery and Operations Manager is attempting to monitor a component that no longer exists on the device.
  • If the device doesn’t support the workflow, then a solution is to disable the workflows utilizing the value for the device. This will prevent these workflows loading and failing in the future.
  • Possibly a device issue, try updating the Firmware and OS on the device
  • Possible a discovery issue where the instance is being discovered incorrectly.  For example Operations Manager is expecting to monitor a performance counter but this is a virtual interface and the counters are not present for the interface.  Try running a re-discovery for the device.

In my clients case the network devices in question did not respond to the information request of certain workflows.

I resolved the issue by creating a group and adding the ports which were not returning data to that group. Then I evaluated each of the event log errors for the name of the workflow that was executing the snmp get, see example below:

Log Name:      Operations Manager
Source:       Health Service Modules
Event ID:      11009
Error in SNMP GET response from IP Address: 10.11.11.1, Status: noSuchInstance(129).
One or more workflows were affected by this.
OID: .1.3.6.1.2.1.10.7.2.1.2.268
Workflow name: System.NetworkManagement.MIB2.NetworkAdapter.InputPacketBroadcastPct
Instance name: Port-37

There is a great reference at http://mpdb.azurewebsites.net which you can use to match up the workflow name to the corresponding rule or monitor. If I use the above example and search the page for System.NetworkManagement.MIB2.NetworkAdapter.InputPacketBroadcastPct I can see it correlates to a rule called Input Broadcast Packets Percentage (netcor) which I can override to turn off against the group I created earlier.

It can be a lengthy process and there are other causes which are easier to address so you will need to do some testing in each individual case.

 

Loading