Tag Archives: #2016

SCOM 2016: Updated MP for Microsoft Azure Stack v1.0.1.0

An updated management pack has been released for Microsoft Azure Stack, version 1.0.1.0 is available here.

Azure Stack is an extension of Azure, bringing the agility and fast-paced innovation of cloud computing to on-premises environments. Only Azure Stack lets you deliver Azure services from your organization’s datacenter, while balancing the right amount of flexibility and control—for truly-consistent hybrid cloud deployments.

New in this version:

  • Implemented “Edit Deployment” wizard.
  • Improved the authentication by means of Azure Active Directory (UPN authentication) and Active Directory Federation Services (UPN and AD FS SPN authentication).
  • Implemented UI improvements in “Add Deployment” wizard.
  • Implemented the Capacity Dashboard.
  • Implemented Auto Maintenance Mode Monitoring Rule that checks if any updates are run on Azure Stack regions and switches regions that are being updated to maintenance mode in Operations Manager. Implemented Turn Off Auto Maintenance Mode and Turn On Auto Maintenance Mode tasks to manually disable and enable the Auto Maintenance Mode.
  • Implemented improvements to reflect changes in the API.
  • Updated the display strings.
  • Added a workaround to support Alert names and descriptions to be displayed in the Operations Manager Reports as a plain text.

SCOM 2016: Don’t forget those Antivirus Exclusions!

Something that I find is often missed with a SCOM deployment is putting in place the recommended AV exclusions. Not having these in place can cause issues in your environment.

Note: Paths are examples, amend drive letter as required for your environment.

Processes
Monitoringhost.exe

Directories
The following directory-specific exclusions for Operations Manager include real-time scans, scheduled scans and local scans. The directories that are listed here are default application directories so you may have to modify these paths based on your specific environment. Only the following Operations Manager related directories should be excluded.

Important When a directory that is to be excluded has a directory name greater than 8 characters long, add both the short and long directory names of the directory to the exclusion list. These names are required by some AV programs to traverse the subdirectories.

SCOM Management Servers
C:\Program Files\Microsoft System Center 2016\Operations Manager\Server\Health Service State

 Agent machines
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State

SCOM SQL Servers
These will include the locations for your SCOM databases and log files as well as you SQL master and tempdb
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
C:\MSSQL\DATA
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Log

File Extensions 
SCOM Management Servers / Agent machines
EDB
CHK
Log

SCOM SQL Servers
MDF
LDF

SCOM 2016: Update Rollup 3 Released

UR 3 for SCOM 2016 is out  you can get it through windows update or in the Catalogue here.

As always test in your labs before deploying to production systems.

Fixes in this update:

  • When you run System Center 2016 Operations Manager in an all-French locale (FRA) environment, the Date column in the Custom Event report appears blank.
  • The Enable deep monitoring using HTTP task in the System Center Operations Manager console doesn’t enable WebSphere deep monitoring on Linux systems.
  • When overriding multiple properties on rules that are created by the Azure Management Pack, duplicate override names are created. This causes overrides to be lost.
  • When the heartbeat failure monitor is triggered, a “Computer Not Reachable” message is displayed even when the computer is not down.
  • The Get-SCOMOverrideResult PowerShell cmdlet doesn’t return the correct list of effective overrides.
  • When creating a management pack (MP) on a client that contains a Service Level (SLA) dashboard and Service Level Objects (SLO), the localized names of objects aren’t displayed properly if the client’s CurrentCulture settings don’t match the CurrentUICulture settings. In cases where the localized settings are English English, ENG, or Australian English, ENA, there’s an issue when the objects are renamed.
  • The Event ID: 26373 error, which may cause high memory consumption and affect server performance, has been changed from a “Critical” message to an “Informational” message.
  • The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that’s running under the .NET Framework 2.0 runtime. Microsoft Monitoring Agent should be updated on all servers that use .NET 2.0 application pools for APM binaries update to take effect. Restart of the server might be required if APM libraries were being used at the time of the update.
  • The UseMIAPI registry subkey prevents collection of processor performance data for RedHat Linux system. Also, custom performance collection rules are also impacted by the UseMIAPI setting.
  • Organizational Unit (OU) properties for Active Directory systems are not being discovered or populated.
  • The Microsoft.SystemCenter.Agent.RestartHealthService.HealthServicePerfCounterThreshold recovery task fails to restart the agent, and you receive the following error message:
    LaunchRestartHealthService.ps1 cannot be loaded because the execution of scripts is disabled on this system.

    This issue has been resolved to make the recovery task work whenever the agent is consuming too much resources. 

  • The DiscoverAgentPatches.ps1 script in Microsoft.SystemCenter.Internal.xml fails and you experience the following exception:
    Exception:
    Method invocation failed because [System.Object[]] does not contain a method named ‘op_Subtraction’.
    At C:\bin\scripts\patch.ps1:37 char:35
    +                   for($count = 0; ($productList.Count-1); $count++)
    +                                   ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (op_Subtraction:String) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound 

  • An execution policy has been added as unrestricted to PowerShell scripts in Inbox management packs.
  • SQL Agent jobs for maintenance schedule use the default database. If the database name is not the default, the job fails.
  • This update adds support for OpenSSL1.0.x on AIX computers. With this change, System Center Operations Manager uses OpenSSL 1.0.x as the default minimum version supported on AIX, and OpenSSL 0.9.x is no longer supported.

SCOM: Updated NiCE DB2 MP 4.20

Another updated MP released over at NiCE this time for IBM DB2 get more info here.

New with this release

  • Feature: Support of DB2 BLU Acceleration
  • Feature: Monitoring of InDoubt Transactions
  • Security: Support of DB2 restrictive databases
  • Security: Support of non-root setup and operation
  • Security: DB2 Instance attach extensions for user and password options
  • Platform: New platform support for IBM AIX 7.2
  • Platform: Support of non-standard paths for both installation path and instance user home directory

SCOM: Updated NiCE PowerHA MP 1.20

Our friends at NiCE have released an updated MP for PowerHA go here for more info.

What´s new with this release

  • Logical Disk Monitoring for Cluster File Systems
  • No False Files Systems Alarms from Microsoft® AIX Management Pack anymore!
  • Cluster-aligned Service Model
  • Improved Discovery for Cluster Resources
  • Updated Product Knowledge

SCOM: New MP for Office 365 v7.1.5138.0

An updated management pack is available for Office 365 you can get it here.

Updates and Fixes

  • Automatically created SPN is never expired.
  • Fixed issue: no alerts were generated for identical feature names related to different services.
  • Improved discovery logic according to the latest version of Office 365 (support for services with similar display names).
  • Updated “Office 365 Incidents and Messages” section.
  • Updated “Import the Management Pack” section.
  • Updated “Specify permissions your app requires to access Office 365 Management APIs” section.
  • Updated “Appendix: Known issues and troubleshooting” section.

SCOM and Deprecating SHA1 Certificates what you need to know!

With the recent deprivation of SHA1 certificates in favour of the more secure SHA2 it’s important to know that SCOM uses  SHA1 to manage workloads for cross platform monitoring (Unix / Linux).

Have no fear the MS SCOM team have released an article on how to replace your existsing SHA-1 certificates with the newer SHA256 certificates.

It is important to note that you will need to update your 2012 R2 environments to UR 12 and your 2016 environments to UR2 respectivly in order to use the new SHA256 certificates by default.

The article is available here