Cumulative Update 1 for System Center 2012 Configuration Manager

CU1 for SCCM 2012 is released. The important thing to notice is that this update is actually marked as hotfix and I recommend to install if you have and want to resolve some of these issues:

Administrator Console
  • When a new distribution point is added to a package that contains more than 100 existing distribution points, the new distribution point cannot be added, and you receive the following error message in the Administrator Console:

    The SMS Provider reported an error.

    When you click Details in the error message, a "Quota Violation" message is displayed that is followed by the details of the stack trace.

  • The link to the online privacy statement for the Customer Experience Improvement Program in the Administrator Console is fixed.
Application Management
  • If a Deployment Type is added or changed before Distribution Manager processes an earlier change, the content may not be sent to a child site.
  • The prestaged content file for a Deployment Type (DT) is not created for remote Distribution Points when there are multiple DTs for the same application. For more information about prestaged content, go to the following Microsoft TechNet website:

    Operations and Maintenance for Content Management in Configuration Manager

Asset Intelligence
  • Volume license editions of Microsoft SQL Server 2012 may be duplicated in the Asset Intelligence Installed_Software_data hardware inventory class.
  • Microsoft SQL Server 2008 R2 Service Pack (SP1) is not listed in the Asset Intelligence License 01D – Microsoft License Ledger Products on a Specific Computer report.
  • The pre-provisioned Asset Intelligence Synchronization Point certificate is updated with a new expiration date.
  • When a dynamic list is used for the Install Application task sequence, not all deployment types will be installed. This issue occurs when one of the deployment types restarts the computer. In this case, any deployment type after the restart is not installed. The state messages that are associated with each application indicate Success. This issue can be seen most clearly in the smsts.log file on the client when the log file is filtered in the CMTrace for entries that contain the text "Installing application."
    The following is an example sequence:

    Installing application ‘App 1’
    Installing application ‘ContentID for App 1′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID1}’
    Installing application ‘App 2’
    Installing application ‘ContentID for App 2′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID2}’
    Installing application ‘App 3 – Exit Code 3010′
    Installing application ‘ContentID for App 3′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID3}’
    Installing application ‘App 4’
    Installing application ‘ContentID for App 2′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID4}’

    Note Both ‘App 2’ and ‘App 4’ share the same content ID. In this example sequence, ‘App 4’ was not installed following the restart that ‘App 3’ triggered.

Out of Band Management
  • Power Control and Clear Audit Log collection-based actions fail for externally provisioned AMT clients. The amptopmgr.log file contains entries that resemble the following entry:

    Error: CSMSAMTDiscoveryTask::Execute, discovery to client_computer failed. General Worker Thread Pool: Error, Can not execute the task successfully. Remove it from task list.

  • Site Database
  • Replication Link Analyzer incorrectly detects a syscommittab system table issue and suggests reinitialization if the SQL Errorlog contains the following string:


  • A primary device cannot be selected for user-based pre-deployment if the device does not have the Configuration Manager client installed.
Site Systems
  • A Reporting Services Point may not be installed or start if the SQL Reporting Service does not start within one minute. The srssp.log file may contain entries that resemble the following entry:

    Starting service ‘ReportServer’
    Time out has expired and the operation has not been completed.

  • The SMS Executive service may stop unexpectedly if the Exchange Connector PowerShell cmdlet fails. The EasDisc.log file may contain entries that resemble the following entry:

    ERROR: [MANAGED] Cmdlet failed: Starting a command on remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.

  • The Site System Status Summarizer component may cause the SMS Executive service to stop unexpectedly if the site server fully qualified domain name (FQDN) is more than 50 characters, and the default installation path is used. The relevant entries from the Exception Information section of the crash.log files contain the following entry:

    Executable = C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
    Exception = eeeeffff (EXCEPTION_SMS_FATAL_ERROR)

The hotfix can be downloaded from here.

Applying CU6 on SCOM 2007 R2 by Kevin Holman

We didn’t had to wait long and Kevin offers us the best guide to apply CU6. Just read the article here.

Cumulative Update 6 for System Center Operations Manager 2007 R2 is available

A few days ago CU1 for SCOM 2012 was released. It seems SCOM Team is not sleeping and they released CU6 for SCOM 2007 R2. Here it is what is offered in the release:

Cumulative Update 6 for Operations Manager 2007 R2 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.

Cumulative Update 6 for Operations Manager 2007 R2 resolves the following cross-platform issues:

  • 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.

Cumulative Update 6 for Operations Manager 2007 R2 adds the following cross-platform features:

  • Support for IBM AIX 7.1 (POWER).
  • Support for Oracle Solaris 11 (x86 and SPARC).
    The update can be downloaded here. Keep in mind that is around 1 GB in size.
    If you are monitoring Cross Platform systems you need to update the MP’s for them after you apply the update. They can be found here.
    The full article about the update is located here.
    I suggest you give a couple of weeks time and test the update in Test environment before apply to production.
    Kevin Holman still hasn’t released an article with details how to apply the update but the process is probably the same like in CU5. You can find Kevin’s article about CU5 here and use it as a reference.

SCOM 2012: Cumulative Update Release 1 is out

It has been a couple of weeks since SCOM 2012 was released and we are getting the first cumulative update. This is becoming something like a good practice for Microsoft products. If you wonder if it is worth it installing it – hell yeaaaaah. Here are the issues that will be resolved after applying the update:

Operations Manager Update (KB2674695) – Windows monitoring
Issue 1

Environment crashes in Operations Manager because of RoleInstanceStatusProbe module in AzureMP.

Issue 2

When multiple (two or three) consoles are running on the same computer under the same user account, the consoles may crash.

Issue 3

You cannot start or stop tracing for Reporting and Web Console if they were installed to a stand-alone server that is running IIS.

Issue 4

Connected Group alert viewing is not working, but no error is given in console.

Issue 5

Task result – CompletedWithInfo not supported with the SDK2007 assemblies.

Issue 6

SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController have to be public to give the controls extensibility and reuse.

Issue 7

WebConsole is not FIPS compliant out of the box.

Issue 8

Network Dashboard should overlay Availability when displaying health state.

Issue 9

Dashboards: Group picker does not show all groups in large environment.

Issue 10

IIS Discovery: Prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API.

Issue 11

Performance Counters are not displayed in the Application list view of AppDiagnostics.

Issue 12

Console crashes when state view with self-contained object class is opened.

Issue 13

PerformanceWidget displays stale "last value" in the legend because of core data access DataModel.

Issue 14

Availability Report and "Computer Not Reachable" Monitor display incorrect data.

Issue 15

Agent install fails on Win8 Core because of dependency on the .NET Framework 2.0.

Issue 16

Web Services Availability Monitoring Wizard – Console crashes if the wizard finishes before a test has finished.

Issue 17

Several Windows PowerShell changes are needed:

  • Changed License parameter in Get-SCOMAccessLicense to ShowLicense
  • Changed SCOMConnectorForTier cmdlets to SCOMTierConnector
  • Some formatting changes
Operations Manager Update (KB2674695) – Unix and Linux monitoring
Issue 1

Schannel error events are logged to the System log on Operations Manager Management servers and on gateways that manage UNIX/Linux agents.

Issue 2

On HP-UX, Operations Manager cannot discover and monitor a logical volume composed of more than 127 physical volumes.

Issue 3

Upgrade of UNIX and Linux agents fails when using Run As credentials in the Agent Upgrade Wizard or Update-SCXAgent Windows PowerShell cmdlet.

Operations Manager Update (KB2674695) – New feature

Update Rollup1 for Operations Manager adds support for Oracle Solaris 11 (x86 and SPARC).

You can read the full article for the fixes here.

This time the update is only 76 megabytes which is great improvement to the 1,2 GB CU5 update for SCOM 2007.

Another great improvement is that you know get one .exe file which you extract and there are separate .msp files for every component of SCOM 2012 – no more copying different files and construction a command line to install agents manually.

The CU can be downloaded here.

If you use SCOM to monitor Unix and Linux servers you will need to update the management pack for UNIX and Linux Operating Systems. You can grab it from here.

So now when you have the update you need a plan to apply it. Only Kevin Holman can give you all the details on installing updates for SCOM. Just read his article OpsMgr 2012: Cumulative Update Release 1 (UR1) ships–and my experience installing it.

Safe updating.