The first update for System Center Operations Manager has just been released, what do you need to know about SCOM 1807?
Updates work the same way as the Update Rollups you are used to you can use windows update or get the packages manually here
First what’s fixed?
Issues that are fixed and improvements that are included
- Fixes an issue that sometimes cause the Performance widget in the web console to throw an ArgumentExceptionmessage.
- Fixes an issue that prevented the Alert view URL in the notification channel from to pointing to the new drill-down Alert page.
- Fixes an issue that causes the web console to throw an ArgumentException message when the state widget is added to a dashboard or scoped to a specific group.
- Improvement to the web console so that is now supports nondefault ports.
- Fixes an issue that causes the pseudo file system to be enumerated.
- Fixes an issue that caused the DNS 2016 Management Pack to throw false alerts for “DNS unused Zone Detected.”
- Fixes an issue that caused the MySQL version to be listed as “for,” “on,” or NULL in Detail view for some platforms.
- Improvement that enables Monitoring Solaris 10 Agents (x86) to provide heartbeat alerts and configuration errors about the SSL certificate.
- Fixes an issue that prevented the Operations Manager console, the Service Manager console and PowerShell modules to coexist on the same server.Note Both Operations Manager and Service Manager must be upgraded to version 1807 to resolve this issue.
- Fixes an issue in which Active Directory Integration rules were not visible or editable in an upgraded 2016 Management Group. This issue prevented the ongoing management of Active Directory integration assignment in the upgraded Management Group.
- Fixes an issue that caused the system and MonitoredBy information to be displayed incorrectly in the Unix/Linux Computers view when the UNIX host name on the server is lowercase.
- Fixes an issue that caused Active Directory integrated agents not to display correct failover server information.
- Fixes an issue in Performance views in the web console that caused the selection of counters not to persist after a web console restart or refresh.
- Fixes an issue in which the PowerShell cmdlet Get-SCXAgent fails and returns a “This cmdlet requires PowerShell version 3.0 or greater” error.
- Fixes an issue in which a group name is changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
- Fixes an issue that causes error HTTP 500 to occur when you access Diagram view through the web console.
- Improvement in which the SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
- Fixes an issue that caused the MonitoringHost process to crash and throw the exception “System.OverflowException: Value was either too large or too small for an Int32.”
- Fixes an issue when company knowledge is edited by using the Japanese version of Microsoft Office through the Operations Manager console, you receive the following error (translated into English): “Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist.”
- Fixes an issue that causes Microsoft.SystemCenter.ManagementPack.Recommendations to log errors on instances of Microsoft SQL Server that have case-sensitive collations.
And then what’s new?
- Improvements to the HTML5 webconeole experience including:
- Addition of a Powershell widget
- Create HTML5 dashboards in MyWorkspace.
- View HTML5 Network Node and Network Interface dashboards.
- Create maintenance schedules from the HTML5 web console.
- You can now enable or disable APM when pushing the agent from the console.
- The Linux agent now supports Log rotation monitoring
- Support for SQL 2017, there is a catch however you will need to update your existing SCOM to 1807 before you can upgrade your SQL to 2017
Update Rollup 5 for SCOM 2016 has been released.
As usual you can get it from the catalog here or through windows update.
all in all this looks like a good update and solves a few persistent issues form previous versions.
Updates and Fixes
- SCOM console and Service Manager console for PowerShell modules can now coexist on the same server.Note Both SCOM Update Rollup 5 (this update) and Service Manager Update Rollup 5 (update KB 4093685) must be installed to resolve this issue.
- Active Directory Integration rules are not visible or editable in an upgraded 2016 Management Group. This prevents the ongoing management of Active Directory integration assignment in the upgraded Management Group.
- When the UNIX host name on the server is in lowercase, the OS and MonitoredBy information is displayed incorrectly in the Unix/Linux Computers view.
- Active Directory integrated agents do not display correct failover server information.
- Performance views in the web console do not persist the selection of counters after web console restart or refresh.
- The PowerShell cmdlet Get-SCXAgent fails with error “This cmdlet requires PowerShell version 3.0 or greater.”
- During the upgrade from SCOM 2016 to SCOM 1801, if the reporting server is installed on a server other than the management server, the upgrade fails. Additionally, you receive the error message, “The management server to which this component reports has not been upgraded.”
- If a group name has been changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
- Error HTTP 500 occurs when you access Diagram view through the web console.
- When you download a Linux management pack after you upgrade to SCOM 2016, the error “OpsMgr Management Configuration Service failed to process configuration request (Xml configuration file or management pack request)” occurs.
- The SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
- The MonitoringHost process crashes and returns the exception “System.OverflowException: Value was either too large or too small for an Int32.”
- When company knowledge is edited by using the Japanese version of Microsoft Office through the SCOM console, the error (translated in English) “Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist” occurs.
- Accessing Silverlight dashboards displays the “Web Console Configuration Required” message because of a certificate issue.
- Microsoft.SystemCenter.ManagementPack.Recommendations causes errors to be logged on instances of Microsoft SQL Server that have case-sensitive collations.
- Deep monitoring displays error “Discovery_Not_Found” if the installation of JBoss application server is customized.
- Adds support for the Lancer driver on IBM Power 8 Servers that use AIX.
- The ComputerOptInCompatibleMonitor monitor is disabled in the Microsoft.SystemCenter.Advisor.Internal management pack. This monitor is no longer valid.
Update Rollup 14 for SCOM 2012 R2 has been released get it here or through windows update.
NB: The same web console update issues from UR13 still exists in UR14 and should be handled the same way.
Updates and fixes
4055768 TLS 1.2 Protocol Support Deployment Guide for System Center 2012 R2
UR4 for SCOM 2016 is out you can get it here or through windows update.
As usual test before implementing in your production environment and take special note of the known issues.
- When a log file is being monitored by SCOM, Monagent locks the file and won’t allow it to be renamed.
- Adds support for TLS 1.2. For more information about how to set up, configure, and run your environment with TLS 1.2, see the following article in the Microsoft Knowledge Base:
4051111 TLS 1.2 Protocol Support Deployment Guide for System Center 2016
- Addresses an issue in which the APM AppDiagnostics console fails to create a Problem Management rule due to a FormatException. The appropriate string is now used for formatting, and the Problem Management wizard is able to run without issues.
- This update resolves an issue that causes a crash of IIS application pools that are running under CLR 2.0 when the APM feature is installed on the server as part of SCOM Agent. The code now uses appropriate memory instructions, based on the CLR version.
- Failure of GetOpsMgrDBWatcherDiscovery.ps1 script causes the Monitoring Host to crash.
- WMI Health monitor doesn’t work if WINRM is configured to use https only.
- SCOMpercentageCPUTimeCounter.ps1 script generates WMI errors that are caused by Service Principle Name (SPN) configuration issues.
- WMI Health monitor doesn’t work if SPN http://servername is set to a user account.
- Product knowledge of “Windows Cluster Service Discovery” includes an incorrect reference to “Windows NT.”
- After a network outage, the management server does not reconnect to the gateway server if the gateway server was installed with the /ManagementServerInitiatesConnection=True option.
- A configuration change to the network device triggers a rediscover of the device, and this process changes the SNMP agent address.
- The UseMIAPI registry subkey prevents collection of custom performance rules data for all Linux servers.
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:
Update rollup 2 for the remaining System Center products is out! Get it here or through the Windows Update.
As always test before deploying to your production environment!
New, Fixed and Improved
Exception type: Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException Message: ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c InnerException: StackTrace (generated): SP IP Function 000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385
- When a management server is removed from the All Management Servers Resource Pool, the monitoring host process does not update the TypeSpaceCache.
- When alerts are closed from the Alerts view after you run a Search, the closed Alerts still appear in the View when the Search is cleared.
- When you press Ctrl+C to copy an alert in Operations Manager Alert view and then press Ctrl+V to paste it to Notepad, the Created time is in UTC time, not local time.
- Groups disappear from Group view after they are added to a Distributed Application.
- IM notifications from Operating Manager to Skype fail when an incorrect exception causes NullReferenceException in the SipNotificationTransport.Send method.
- When the maintenance mode option for the dependency monitor is set to “Ignore,” and the group (consisting of the server to which this dependency monitor is targeted) is put in Maintenance mode, the state of the monitor changes to critical and does not ignore maintenance mode.
- Because of a rare scenario of incorrect computation of configuration and overrides, some managed entities may go into an unmonitored state. This behavior is accompanied by 1215 events that are written to the Operations Manager log.
- Recovery tasks on “Computer Not Reachable” Operations Manager Monitor generate failed logons on SCOM Agents that are not part of the same domain as the management groups.
- The ManagementGroupCollectionAlertsCountRule workflow fails and generates a “Power Shell Script failed to run” alert.
- Get-SCOMGroup cmdlet fails when thousands of groups are created in Operations Manager.
- Organizational unit properties for computers that are running Windows are not discovered or populated. This discovery is part of the System Center Internal Library MP. After this update, organizational unit properties will be discovered for all computers that are running Windows.
- When the Operations Manager Health Service agent starts, and the agent is configured for AD integration, if the agent cannot contact Active Directory at all, it immediately goes dormant and stops trying to connect and obtain the policy from Active Directory.
Issues that are fixed in the UNIX and Linux management packs
- SHA1 is deprecated, and SHA256 certificates are now supported on the management server that’s used to sign the Unix/Linux OMI certificate.
- OMI does not work on Linux servers configured for FIPS compliance.
- Avg. Physical disk sec/transfer performance counters are not displayed for Hewlett Packard computers.
- OMI displays incorrect Memory information on Solaris 10 computers.
- Network adapter performance is not displayed for SLES 12 x64 platform in the Operations Manager Console.
- Cannot discover file systems on HPUX 11.31 IA-64 computers with more than 128 disks. Previously it supported only 128 VGs. Now support is extended to 256 VGs.
- Deep monitoring cannot be started successfully on some JBoss applications because the discovery of the JBoss application server sets the Disk Path for the JBoss server incorrectly. Deep monitoring was not being started in JBoss stand-alone mode when a nondefault configuration was used.
UR12 for SCOM 2012 R2 has been release as usual you can get it from the download catalog or through windows update.
Changes and fixes
- When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server, the upgrade fails for the following configuration:
- Server A is configured as System Center 2012 R2 Operations Manager including Management Server.
- Server B is configured as System Center 2012 R2 Operations Manager, including Operations Manager Database (OpsMgrDB), Operations Manager Data Warehouse (OpsMgrDW) and Operations Manager Reporting Server.
( X ) Management Server Upgraded Check
The management server to which this component reports has not been upgraded.
- Recovery tasks on “Computer Not Reachable” messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
- When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
- SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
- Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
- IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
- There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
- You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
- When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted. Additionally, the following is logged in the Operations Manager log file:
Log Name: Operations Manager
Source: Health Service Modules
Event ID: 10801
Task Category: None
Description: Discovery data couldn’t be inserted to the database. This could have happened because of one of the following reasons:
– Discovery data is stale. The discovery data is generated by an MP recently deleted.
– Database connectivity problems or database running out of space.
– Discovery data received is not valid.
Additionally, you may receive the following exception, which causes this issue to occur:
Exception type: Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException
Message: ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c
StackTrace (generated): SP IP Function 000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385
Changes and fixes for Unix and Linux
- RHEL 7 on Power8 is now supported in System Center2012 R2 Operations Manager
- SHA1 is deprecated and SHA2 is now supported on the management server that’s used to sign the UNIX/Linux Operations Manager i (OMi) certificate.
- OMi start attempts fail on all FIPS-enabled UNIX/Linux systems. This fix updates the agents to support FIPS-enabled systems.
- The Average Physical disk sec/transfer performance counters are not displayed for Hewlett Packard systems.
- OMi displays incorrect memory information for Solaris 10 systems.
- The Network Adapter Performance counter is not displayed for SLES 12 x64 platforms in the console.
- You can’t discover file systems on HPUX 11.31 IA-64 computers that have more than 128 disks. Previously, only 128 VGs were supported. This update extends support to 256 VGs.
- Deep monitoring can’t be started successfully for some Jboss applications because the discovery of the Jboss application server sets the DiskPath for the Jboss server incorrect. Deep monitoring is not started in JBoss stand-alone mode when a nondefault configuration is used. This update provides additional support for JBoss stand-alone mode.
Hot off the press Update Rollup one for SCOM 2016 has been released it is available through the catalog or here
UR 11 is out all the details are available – here
Products that have an update are: Service Provider Foundation, Virtual Machine Manager and also the Windows Azure Pack Websites.
We will see later in the week if other products are also getting updates,
Update Rollup 9 for SCOM 2012 R2 has been released and contains a variety of fixes. As usual the update is available through windows update or in the download catalogue here.
As always test thoroughly before implementing in a production environment.
Issues that are fixed in this update rollup
- SharePoint workflows fail with an access violation under APMA certain sequence of the events may trigger an access violation in APM code when it tries to read data from the cache during the Application Domain unload. This fix resolves this kind of behavior.
- Application Pool worker process crashes under APM with heap corruptionDuring the Application Domain unload two threads might try to dispose of the same memory block leading to DOUBLE FREE heap corruption. This fix makes sure that memory is disposed of only one time.
- Some Application Pool worker processes become unresponsive if many applications are started under APM at the same timeMicrosoft Monitoring Agent APM service has a critical section around WMI queries it performs. If a WMI query takes a long time to complete, many worker processes are waiting for the active one to complete the call. Those application pools may become unresponsive, depending on the wait duration. This fix eliminates the need in WMI query and significantly improves the performance of this code path.
- MOMAgent cannot validate RunAs Account if only RODC is availableIf there’s a read-only domain controller (RODC), the MonAgent cannot validate the RunAs account. This fix resolves this issue.
- Missing event monitor does not warn within the specified time range in SCOM 2012 R2 the first time after restartWhen you create a monitor for a missed event, the first alert takes twice the amount of time specified time in the monitor. This fix resolves the issue, and the alert is generated in the time specified.
- SCOM cannot verify the User Account / Password expiration date if it is set by using Password Setting objectFine grained password policies are stored in a different container from the user object container in Active Directory. This fix resolves the problems in computing resultant set of policy (RSOP) from these containers for a user object.
- SLO Detail report displays histogram incorrectlyIn some specific scenarios, the representation of the downtime graph is not displayed correctly. This fix resolves this kind of behavior.
- APM support for IIS 10 and Windows Server 2016Support of IIS 10 on Windows Server 2016 is added for the APM feature in System Center 2012 R2 Operations Manager. An additional management pack Microsoft.SystemCenter.Apm.Web.IIS10.mp is required to enable this functionality. This management pack is located in %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups alongside its dependencies after the installation of Update Rollup 9.
Important Note One dependency is not included in Update Rollup 9 and should be downloaded separately:
- APM Agent Modules workflow fail during workflow shutdown with Null Reference ExceptionThe Dispose() method of Retry Manager of APM connection workflow is executed two times during the module shutdown. The second try to execute this Dispose() method may cause a Null Reference Exception. This fix makes sure that the Dispose() method can be safely executed one or more times.
- AEM Data fills up SCOM Operational database and is never groomed outIf you use SCOM’s Agentless Exception Monitoring to examine application crash data and report on it, the data never grooms out of the SCOM Operational database. The problem with this is that soon the SCOM environment will be overloaded with all the instances and relationships of the applications, error groups, and Windows-based computers, all which are hosted by the management servers. This fix resolves this issue. Additionally, the following management pack’s must be imported in the following order:
- The DownTime report from the Availability report does not handle the Business Hours settingsIn the downtime report, the downtime table was not considering the business hours. This fix resolves this issue and business hours will be shown based on the specified business hour values.
The updated RDL files are located in the following location:
%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Reporting
To update the RDL file, follow these steps:
- Go to http://MachineName/Reports_INSTANCE1/Pages/Folder.aspxMachineName //Reporting Server.
- On this page, go to the folder to which you want to add the RDL file. In this case, click Microsoft.SystemCenter.DataWarehouse.Report.Library.
- Upload the new RDL files by clicking the upload button at the top. For more information, see https://msdn.microsoft.com/en-us/library/ms157332.aspx.
- Adding a decimal sign in an SLT Collection Rule SLO in the ENU Console on a non-ENU OS does not workYou run the System Center 2012 R2 Operations Manager Console in English on a computer that has the language settings configured to use a non-English (United States) language that uses a comma (,) as the decimal sign instead of a period (.). When you try to create Service Level Tracking, and you want to add a Collection Rule SLO, the value you enter as the threshold cannot be configured by using a decimal sign. This fix resolves the issue.
- SCOM Agent issue while logging Operations Management Suite (OMS) communication failureAn issue occurs when OMS communication failures are logged. This fix resolves this issue.