System Center Operations Manager Updates

Standard

In this blogpost I will give information on the released Cumulative Updates for System Center Operations Manager 2007 r2 and System Center Operations Manager 2012. I will try to keeping this post up to date when a new update is released. Most information in this blogpost can also be found on Microsoft Technet and some information is directly copied from Microsoft Technet.

Last Update 16-01-2013

Here are all the Cumulative Update Rollups for System Center Operations Manager 2012.

  • Service Pack 1 : System Center Operation Manager 2012 Service Pack 1 is released on January 2, 2013. This Update Resolves the following Issues:
    • Support for IIS 8
    • Monitoring of WCF, MVC and .NET NT services
    • Azure SDK support
    • Monitoring of SharePoint 2010 with APM (.NET application performance monitoring)
    • Integration with Team Foundation Server 2010 and Team Foundation Server 2012
    • Conversion of Application Performance Monitoring events to IntelliTrace format
    • Support for monitoring of CentOS, Debian, and Ubuntu Linux
    • ACS support for Dynamic Access Control in Windows Server 2012
    • Global Service Monitor – cloud based capability to monitor the health of your web applications from geo-distributed perspective
    • Additional network devices models supported

    More Information on Service Pack 1 can be found here. Kevin Greene wrote a greath blog series on how to install Service Pack 1. Kevin Greene blog series can found: Part 1 Part 2 Part 3

  • Cumulative Update Rollup 3: System Center Operation Managener 2012 Cumulative Update Rollup 3 is released on October 9, 2012. This Update Resolves the following Issues:
    • When you use the 32-bit version of Windows Internet Explorer to start a web console, the “Microsoft.EnterpriseManagement.Presentation.Controls.SpeedometerGaugeUIController” controller does not work correctly
    • When you run a Windows PowerShell cmdlet, you receive the following error message: “Get-BPAModel is not recognized as the name of a cmdlet“.
    • When you try to change a URL in the “web application availability monitoring” template instance, the change is not applied.

    More Information on Cumulative Update Rollup 3 can be found here and can be download from here. Kevin Greene wrote a greath blogpost on how to install Cumulative Update Rollup 3. Kevin Greene blogpost can found here

  • Cumulative Update Rollup 2: System Center Operation Managener 2012 Cumulative Update Rollup 2 is released on July 24, 2012. This Update Resolves the following Issues:
    • The Windows PowerShell module runspace configuration cache grows indefinitely. This causes memory usage to increase.
    • The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired.
    • The System Center Operations Manager agent may crash on Oracle Solaris root zones that are configured to use a range of dedicated CPUs.
    • The UNIX/Linux agent process provider may not enumerate running processes if a process has arguments that include non-ASCII characters. This prevents process/daemon monitoring.
    • The .rpm specification file for the agent for Red Hat Enterprise Linux does not specify the distribution.

    More Information on Cumulative Update Rollup 2 can be found here and can be download from here. Kevin Holman and Kevin Greene both wrote a greath blogpost on how to install Cumulative Update Rollup 2. Kevin Holman blogpost can be found here and Kevin Greene blogpost can be found here

  • Cumulative Update Rollup 1: System Center Operation Managener 2012 Cumulative Update Rollup 1 is released on May 8, 2012. This Update Resolves the following Issues:
    • Environment crashes in Operations Manager due to RoleInstanceStatusProbe module in AzureMP.
    • When multiple (2-3) consoles are running on the same computer under the same user account the consoles may crash.
    • Cannot start or stop tracing for Reporting and Web Console if they were installed to a standalone IIS server.
    • Connected Group alert viewing is not working but no error is given in console.
    • Task result – CompletedWithInfo not supported with the SDK2007 assemblies.
    • SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController need to be public to allow the controls extensibility and reuse
    • WebConsole is not FIPS compliant out of the box.
    • Network Dashboard should overlay Availability when displaying health state
    • Dashboards: Group picker does not show all groups in large environment
    • IIS Discovery: prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API
    • Performance Counters do not show up in Application list view of AppDiagnostics.
    • Console crashes when state view with self-contained object class is opened.
    • PerformanceWidget displays stale ‘last value’ in the legend due to core data access DataModel
    • Availability Report and “Computer Not Reachable” Monitor show incorrect data.
    • Web Services Availability Monitoring Wizard – Console crashes if wizard finishes before test has finished

    More Information on Cumulative Update Rollup 1 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update Rollup 1. This can be found here

Here are all the Cumulative updates that are released by Microsoft for System Center Operations Manager 2007 r2. A summary of the cumulative Updates can be found here

  • Cumulative Update 7: System Center Operation Managener 2007 r2 Cumulative Update 7 is released on Jan 9, 2013. This Update Resolves the following Issues:
    • Console performs poorly when User Roles are used to scope object access.
    • Availability data is not shown for the current day when daily aggregation is used.
    • Behavior is inconsistent between some views on web console and console.
    • Log files do not roll over when the Unicode log file is monitored.
    • Several security issues are fixed.
    • Logical disk performance statistics are not collected for some volume types on Solaris computers.
    • Some Network Adapters on HP-UX computers may not be discovered.
    • Network adapter performance statistics are not collected for HP-UX network adapters.
    • The Solaris 8 and 9 agent may not restart after an ungraceful shutdown.

    More Information on Cumulative Update 7 can be found here and can be download from here. Roel Knippen wrote a blogpost on how to install Cumulative Update 7. This can be found here

  • Cumulative Update 6: System Center Operation Managener 2007 r2 Cumulative Update 6 is released on May 14, 2012. This Update Resolves the following Issues:
    • RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
    • UI is limited to only 100 MB for the Memory Usage field in the wizard.
    • Additional OIDs in auth certificate are not processed correctly.
    • AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
    • Cannot open reporting pane on OpsMgr 2007 R2 remote console.
    • Cannot view schedule for scheduled report
    • ManagementServerConfigTool with the option “promoterms” fails because it stops polling the SDK Service.
    • OpsMgr reports are failing on Windows 7 with the error: “Cannot initialize report.”
    • ACS events have “n/a” as their category in the ACS database.
    • Watch agentless monitoring listener to detect failure to respond.
    • SCOM SDK memory leak on cryptography keys and cryptography contexts.
    • After you click Edit Schedule, a message box appears, and you cannot save the change value
    • Audit events can be lost when the AdtServer process crashes.
    • The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
    • After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
    • On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
    • The OpsMgr agent for AIX does not report the arguments for monitored processes.
    • When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
    • On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.
    • Support for IBM AIX 7.1 (POWER).
    • Support for Oracle Solaris 11 (x86 and SPARC).

    More Information on Cumulative Update 6 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 6. This can be found here

  • Cumulative Update 5: System Center Operation Managener 2007 r2 Cumulative Update 5 is released on July 5, 2011. This Update Resolves the following Issues:
    • Restart of non-Operations Manager services when the agent is updated.
    • Updated ACS reports.
    • TCP Port Probe incorrectly reports negative ping latency
    • MissingEvent Manual Reset Monitor does not work as expected.
    • Drillthrough fails because of rsParameterTypeMismatch in the EnterpriseManagementChartControl.
    • ACS – Event log message is truncated or corrupted in SCDW.
    • UI hang caused by SDK locking.
    • ACS Filter fails for certain wildcard queries.
    • Edit Schedule button is disabled with SQL 2008 R2.
    • Web console times out when you open the left navigation tree.
    • Scheduled Reports view for Windows Server 2003 and for Microsoft SQL Server 2005 Reporting Services SP3 CU9 returns “System.IndexOutOfRangeException: Index was outside the bounds of the array.”
    • Signed MPs cannot be imported when new attributes are added to existing classes.
    • Performance data for LVM managed partitions is not available
    • Process monitor does not keep name if run by using symbolic link.
    • AIX with large number of processes crashes with bad alloc.
    • Support for Red Hat 6

    More Information on Cumulative Update 5 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 5. This can be found here

  • Cumulative Update 4: System Center Operation Managener 2007 r2 Cumulative Update 4 is released on January 31, 2011. This Update Resolves the following Issues:
    • The Performance and Resource Optimization (PRO) Tips feature does not function correctly after you install Cumulative Update 3 for SCOM 2007 R2.
    • The Alert view does not work correctly when the source of an alert contains both monitors and rules
    • The event description is not collected by the Azure management pack. To resolve this issue, build the Windows Azure application by using Windows Azure SDK 1.3.
    • The monitoring host process may stop responding on a computer that is running on Windows Server 2003 Service Pack 2 (SP2).
    • The performance of the Diagram view is slow if a user role is in the scope of many groups
    • In the web console properties for an alert, the hyperlinks on the Knowledge tab are not active.

    More Information on Cumulative Update 4 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 4. This can be found here

  • Cumulative Update 3: System Center Operation Managener 2007 r2 Cumulative Update 3 is released on October 1, 2010. This Update Resolves the following Issues:
    • Feature addition: Azure Application Monitoring
    • Feature addition: Parameter Extraction in Web Application Synthetic Transactions
    • Some ACS reports do not work as expected in Windows Server 2008
    • SCOM 2007 SP1 Reports do not run after a shared Data Warehouse is upgraded to SCOM 2007 R2
    • The SDK Services stops working due to an unhandled exception, and the operations console becomes unresponsive
    • Multi-selection in the alert view is not maintained during a view refresh
    • The operations console stops working when creating an override on the cluster resource group monitor
    • When Agentless Exception Monitoring (AEM) is set up to use SharePoint, reports from Watson are blocked
    • The Operations Manger Console stops working when a high number of instances of State Views or Alert Views are left open for extended durations
    • Upgrading MPs that include new properties may not recreate views correctly
    • The total transaction response performance counter in URL monitoring is not accurate
    • MPs with empty knowledge elements cannot be imported in Operations Manager 2007 R2
    • Monitoringhost.exe does not work reliably on Windows 2003 SP2 X64 Domain Controllers
    • Alerts using the “Specific Time Period” criteria are not included during automatic alert view refresh
    • ACS forwarders with 15 character names in workgroups are unable to communicate with the ACS collector
    • Language packs authored for a previous version of an MP cannot be imported once an updated MP is released
    • Language Pack import fails if the MP contains strings which are not contained in the English Management Pack
    • Generic performance reports consume a large amount of temporary database space and can fail for Windows Server 2003 Computer Groups
    • When using a remote console the notification wizard does not work in certain situations
    • The SDK service may stop working due to an arithmetic overflow error in very rare circumstances
    • The notification scheduler does not compensate correctly for different time zones

More Information on Cumulative Update 3 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 3. This can be found here

  • Cumulative Update 2: System Center Operation Managener 2007 r2 Cumulative Update 2 is released on June 29, 2010. This Update Resolves the following Issues:
    • The Network Devices State view does not display the device name.
    • The discovery process fails when a double-byte character is inserted into a string that is searched
    • The availability reports that are exported as TIF files or as PDF files are truncated.
    • The property bags of WMIEventProvider module do not support the including or excluding of specific properties
    • The color of the chart lines does not match the legend in the Web console in the Performance view.
    • When SQL Reporting Services is enabled in SCOM by using the United States Federal Information Processing Standards (FIPS) security, the datawarehouse encounters an InvalidOperationException error
    • The monitoring host process does not start the workflows immediately when tasks are received
    • The Operations Manager console crashes when you open multiple customized views in a new window.
    • The Allow Anonymous discovery property in the Internet Information Services (IIS) Management Pack is incorrect in the console.
    • When you run updates, a restart dialog box is shown before the files for the update are delivered.
    • The agent update packages are not deployed to the servers that have the Terminal Services Gateway (TS Gateway) role installed or that have the Remote Desktop Gateway (RD Gateway) role service installed.
    • Audit Collection Services stops collecting data if the Event Log service uses the automatic backup feature

    More Information on Cumulative Update 2 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 2. This can be found here

  • Cumulative Update 1: System Center Operation Managener 2007 r2 Cumulative Update 1 is released on January 30, 2010. This Update Resolves the following Issues:
    • The Product Knowledge tab is displayed as the Company Knowledge tab after you import a language pack for System Center Operations Manager 2007 R2.
    • An agent cannot be removed successfully from a Windows Cluster service node
    • The Heathservice.exe process on a Windows Cluster service passive node may have excessive CPU utilization.
    • The Healthservice.exe process may crash when it uses the OLE DB module.
    • The workflows that use the OLE DB data source may unload themselves if the underlying provider returns a null string or an empty string.
    • An instance of the MonitoringHost.exe process may cause a memory leak in nonpaged pool memory.
    • The notification subscriptions do not work if they are configured to parse a CustomField field or an AlertOwner field.
    • The Operations console loses the status as the current object that is in focus when a search filter is applied.
    • The SRSUpgradeTool.exe process returns an error that states “Failed while updating registry entry for reporting code MSI component” when you try to upgrade SQL Reporting Services 2005 to SQL Reporting Services 2008.
    • The Operations Manager UI may crash when the Connector column and the Forwarding Status column are added to an Alert view.
    • The agents may re-process old Windows event log entries and then incorrectly generate alerts for these events that are not new.
    • Health state reliability fixes and improvements.
    • The Operations Manager Audit Collection Service (ADTServer.exe) does not start on an ACS Collector if the operating system is upgraded to Windows Server 2008 R2.
    • In a performance report that is exported, the list of object instances is not displayed

    More Information on Cumulative Update 1 can be found here and can be download from here. Cumulative Update 1 is included in Cumulative Update 2 Kevin Holman wrote a greath blogpost on how to install Cumulative Update 2. This can be found here

Maintenance Mode Explained

Standard

Maintenance mode is a option in System Center Operation Manager 2007 r2 and System Center Operation Manager 2012. You can use the maintenance mode option when you are planning a software update or when you planning a hardware upgrade.

When you place a Agent in maintenance mode the workflows that are targeted against the Agent will be susppended during the Maintenance mode. This wil prevent the generation of alerts and notfications. When a Agent is in maintenance mode the following will be suppressed at the agent:

  • Alerts
  • Notifications
  • Rules
  • Monitors
  • Automatic Respones
  • State Changes
  • New Alerts

When you place a Agent in Maintenance mode the following event is generated in the operations Manager Eventlog

EventProperties1216HealthService

Placing a Agent into Maintenance Mode

  1. Open the Operations Manager Console
  2. Under the "Monitoring" expand "Microsoft Windows Server" and select "Windows Server State"

    SystemCenterOperationsManagerConsole

  3. This wil list al the servers that are monitored by System Center Operations Manager
  4. Select a "Agent" and in the "Actions" screen Click "Start Maintenance Mode"

    Actions

  5. In the Maintenance mode settings screen. Select "Selected Objects and all their contained objects" This will put the complete server in Maintenance mode. In the "Category" select the catagory of wich this maintenance mode is placed. Then you select the "Time interval" for the maintenance mode using the option under "Duration" Remember this is required. Press "OK"

    MaintenanceModeSettings

What happens in the background when placcing a Agent in Maintenance Mode?

  1. When you place an agent into Maintenance Mode a call is made to the SDK service to trigger the Maintenance Mode for the agent and the workflow running on that agent are unloaded.
  2. A Configuration update is calculated and sent to the agent. When you check the event log on the agent that is put in Maintenance Mode you see the event 1210 is created on the agent

    EventProperties1210HealthService

  3. On a schedule the RMS checks of the maintenance mode is expiring.
  4. When the maintenance mode is expired, a updated is sent to the agent and the workflows are loaded on the agent

Scheduling Maintenance Mode

Default can System Center Operations Manager 2007 r2 not allow scheduling maintenance mode. But when you install System Center Operations Manager 2007 r2 Admin Resource Kit you can schedule Maintenace Mode. You can download the Operations Manager R2 Admin Resource Kit from here You can also use the community tool: SCOM Remote Maintenace Mode Scheduler writen by Tim McFadden

For System Center Operations Manager 2012 the Admin Resource Kit is not yet available

More information on Maintenance mode can be found:

Renew Certificates SCOM 2007 r2

Standard

I recieved the following alert in System Center Operations Manager 2007 r2 on our Root Management Server (RMS) and Gateway server.

The certificate used for mutual authentication is expiring on 07/09/2012 6:32:15 AM GMT. If this certificate is not updated by this time, this Health Service will not be able to communicate with other Health Services.

To renew the certificate on the Root Management Server(RMS) or Gateway follow the following steps:

  1. Request a certificate from your certificate authority using the Operations Manager Template and install it on the RMS Sever. More information on How to Obtain a Certificate Using Windows Server 2003 Enterprise CA in Operations Manager 2007 r2 click here. If you are using a Windows Server 2008 Certificate authority click here.
  2. Check in the MMC console that the newly installed certificate has “Server Authentication” and “Client Authentication” by double clicking the certificate – Details – Enhanced Key Usage.
  3. Export the generated certificate from the Certificates console and select “Yes, export the private key” on the first page of the wizard.
  4. Save the certificate as .PFX file, and specify a password for it.
  5. Remove the old imported certificates from System Center Operations Manager with the command MOMCertImport.exe /Remove.
  6. Install the new certiicate with the following command line: “MOMCertImport.exe C:\cert.pfx /Password P@ssw0rd
  7. Check if the registry value “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\MachineSettings\ChannelCertificateSerialNumber” of Serial Number matches that you see in the Properties page of the certificate (the string is in a reverse order).
  8. Restart the System Center Operation Manager health services on the RMS and gateway servers to see if the update is succeeded.

More information on this issue can be found here.

System Center Operations Manager Firewall ports

Standard

When installing System Center Operations Manager you want to keep the local firewall on your servers up and running. You can use the following commands to open the ports you need.

For the command's below to work run the "command prompt as administrator".

Run this on the SQL Server that is the Database server for your Management Servers:

  • netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN
  • netsh advfirewall firewall add rule name = SQLBrowserPort dir = in protocol = tcp action = allow localport = 1434 remoteip = localsubnet profile = DOMAIN
  • netsh advfirewall firewall add rule name = ServiceBroker dir = in protocol = tcp action = allow localport = 4022 remoteip = localsubnet profile = DOMAIN

un this on the Server that is the The web server for Operations Manager:

  • netsh advfirewall firewall add rule name = HTTP dir = in protocol = tcp action = allow localport = 80 remoteip = localsubnet profile = DOMAIN
  • netsh advfirewall firewall add rule name = HTTPS dir = in protocol = tcp action = allow localport = 443 remoteip = localsubnet profile = DOMAIN

Run this on each of the System Center Management Servers:

  • netsh advfirewall firewall add rule name = MgmtPort dir = in protocol = tcp action = allow localport = 5723 remoteip = localsubnet profile = DOMAIN
  • netsh advfirewall firewall add rule name = MgmtConsole dir = in protocol = tcp action = allow localport = 5724 remoteip = localsubnet profile = DOMAIN

When you are using SNMP Network Monitoring run the following commands System Center Management Servers:

  • netsh advfirewall firewall set rule name="Operations Manager Ping Response (Echo Response – ICMPv4 IN)" new enable=yes
  • netsh advfirewall firewall set rule name="Operations Manager SNMP Response" new enable=yes
  • netsh advfirewall firewall set rule name="Operations Manager SNMP Trap Listener" new enable=yes

More information on the "netsh advfirewall firewall" command, can be found here. If you want more information on the firewall ports take a look at the following technet article. This can be found here