Description of Cumulative Update 4 for System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1

Applies to: Microsoft System Center 2012 R2 Configuration Manager Service Pack 1Microsoft System Center 2012 Configuration Manager Service Pack 2

Summary


This article describes the issues that are fixed and functionality that is updated in Cumulative Update 4 (CU4) for Microsoft System Center 2012 Configuration Manager Service Pack 2 (SP2) and System Center 2012 Configuration Manager R2 Service Pack 1 (SP1). This update applies to both releases.

back to Table of Contents

Issues that are fixed


Mobile device management

  • Synchronization of the Exchange Connector fails, and errors that resemble the following are logged in the EasDisc.log file:
    ERROR: [MANAGED] Exception: An item with the same key has already been added.
    ERROR: Failed to check status of discovery thread of managed COM. error = The parameter is incorrect.
    INFO: Total number of devices discovered 0

    This issue occurs in environments when the same account name exists across multiple domains. For example, user1@contoso.com and user1@domain2.contoso.com.
     

Site Systems

  • The SMS Executive service stops unexpectedly when the SMS_Despooler component is trying to delete a file. Errors that resemble the following are recorded in the Despool.log file on the site server:
    ::DeleteFileW failed for D:\SCCMContentLib\FileLib\1E69\{guid}.SIG
    RemoveFile failed; 0x80070002
    CFileLibrary::AddFile failed; 0x80070002
    CContentBundle::ExtractContentBundle failed; 0x80070002
    ~Failed to extract contents to the content library. 0x80070002
    ~Failed to extract package contents from C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\DESPOOLR.BOX\RECEIVE\PKG12345.TRY. Error = 2

    After this error sequence is recorded, the SMS Executive service may stop.
     
  • The SMS Executive service stops unexpectedly when it processes certificate data. When this occurs, the last entry in the certmgr.log file contains entries that resemble the following:
    RetrievePfxData - WHERE UserItemKey={itemkey} and IsTombstoned=0
  • The Delete Aged Status Messages maintenance task incorrectly removes records from the Update_ComplianceStatus table. This results in inaccurate status reporting for updates older than 6 months.
     
  • CPU usage on the SQL server for a given site may spike under load from many user policy requests in a short period.

Administrator Console

  • The Available software updates count in the Schedule Updates Wizard shows an incorrect count of updates for Windows 10-based client images.

Operating System Deployment

  • 3151994 The SMSTSRebootDelay variable doesn't work for multiple restarts in System Center 2012 Configuration Manager
     
  • The Task Sequence execution engine times out in two minutes, instead of running up to a defined maximum.
     
  • 3183710  The Install Application task does not use content from the pre-staged media in System Center 2012 Configuration Manager

Non-windows clients

  • 3155424 Mac inventory data isn’t processed in System Center 2012 Configuration Manager

Software distribution and content management

  • Software distribution content is not extracted to a secondary drive when the primary drive of a distribution point has insufficient free space. Errors that resemble the following are recorded in the despool.log on the site server:
    Extracting content ABC00001.1
    ::DeleteFileW failed for H:\SCCMContentLib\FileLib\...
    RemoveFile failed; 0x80070002
    CFileLibrary::AddFile failed; 0x80070002
    CContentBundle::ExtractContentBundle failed; 0x80070002
    ~Failed to extract contents to the content library. 0x80070002
    ~Failed to extract package contents from E:\SCCM\INBOXES\DESPOOLR.BOX\RECEIVE\{PKG_File}. Error = 2
  • All content distribution can stall if one distribution point is in a problem state. For example, if the IIS Admin Service (inetinfo.exe) is hanging on one distribution point, all other distribution points will wait for the problematic distribution point to come back online. A message pattern resembling the following is logged in the distmgr.log file on the site server, repeating approximately every two minutes:
    There are still 1 DP threads active for package ABC00139, waiting for them to complete. SMS_DISTRIBUTION_MANAGER 12608 (0x3140)
    There are still 1 DP threads active for package PRI00290, waiting for them to complete. SMS_DISTRIBUTION_MANAGER 14128 (0x3730)
    There are still 1 DP threads active for package ABC0013B, waiting for them to complete. SMS_DISTRIBUTION_MANAGER 8348 (0x209C)
    There are still 2 DP threads active for package ABC000C4, waiting for them to complete.
  • Redistributing a package to a remote distribution point at a secondary site results in all distribution points for that site receiving the package. This issue occurs when the secondary site was recovered, and the original database was lost.
     
  • If the Configuration Manager Content Library (SCCMContentLib) spans multiple drives, and one of those drives is full, content distribution may fail. In this case, errors that resemble the following are recorded in the distmgr.log file:
    ~Use drive D for storing the compressed package.
    CContentBundle::AddContentDefinitionItems failed; 0x80070003
    CDistributionManager::AddContentToBundle failed; 0x80070003
    CDistributionManager::CreatePackageBundle failed; 0x80070003
    ~Error creating package bundle to send copy of package ABC000A2 to site PRI.
    STATMSG: ID=2333 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER"
    To resolve the package error for content created before this update was installed, look for errors that resemble the following in the distmgr.log file:
    MoveFileW failed for Z:\SCCMContentLib\FileLib\5CE9\{GUID}.INI to Y:\SCCMContentLib\FileLib\5CE9\{GUID}.INICFileLibrary::AddFile failed; 0x80070002CFileLibrary::AddFile failed; 0x80070002CContentDefinition::AddFile failed; 0x80070002
    Delete and recreate the package in question.

    Note the first path in the MoveFileW log entry, and delete the metadata file that's reported as missing. In the preceding example, it is "Z:\SCCMContentLib\FileLib\5CE9\{GUID}.INI." If required, use the Content Library Transfer Tool to consolidate the content library to one drive.

    These steps are not required for any content that was created after this update was installed.

Client

  • Software center incorrectly displays a status of Waiting to install when it should display Waiting for next available maintenance schedule.
     
  • Network errors can result in the Location Services component of the SMS Agent Host (ccmexec.exe) generating a sharp increase in CPU activity on client computers.

Software Updates Management

  • Software updates are expired incorrectly based on their creation date instead of their supersedence date.

back to Table of Contents

Additional changes that are included in this update


Vulnerability Assessment

Supported operating systems

  • Mac OS X 10.12 can be targeted as a client platform for the following features:
    • Application Management

    • Settings Management

    Note This update requires the latest release of the Clients for Additional Operating Systems.
  • Ubuntu Linux 16.04 can be targeted for software distribution.

Client

  • Multiple client components are upgraded to remove a dependency on the Visual C++ 2005 runtime.

    Note For the dependency to be removed, the client must be upgraded by using the client setup file, CCMSetup.exe. This is typically invoked through the built-in automatic update feature, or through the client push installation that uses the option to “Always install the client software” enabled. For more information, see How to install clients on Windows-based computers in Configuration Manager.

    Even though CU4 removes the binary dependency on the Visual C++ 2005 runtime files, there are some scenarios in which the files will be replaced on a client by ccmsetup.exe. Specifically, this can occur if ccmsetup.exe is launched by Client Push Install, Client Auto Upgrade, Configuration Manager Health Evaluation, etc. In these cases, the files will be replaced if they are missing on a client, but there is still no dependency between the Configuration Manager client and the Visual C++ 2005 runtime.

back to Table of Contents

How to obtain and install this update


Update information

The following cumulative update is available from the Microsoft Download Center:


If the download window does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update.


Installation information

This update applies to the following:

  • System Center 2012 Configuration Manager Service Pack 2
  • System Center 2012 R2 Configuration Manager Service Pack 1

Restart information

You do not have to restart the computer after you apply this update.

Note We recommend that you close the Configuration Manager Administrator Console before you install this update.

Update replacement information

This update replaces Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager.

Boot images

After this cumulative update is installed on site servers, any operating system boot image should be updated. To update boot images after the update is applied, follow these steps:

  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select the Update Distribution Points action.

    Note This action updates all distribution points. This action may have an adverse effect on an environment that contains many distribution points.
  5. Repeat steps 3 and 4 for all boot images that were previously distributed.

For more information about how to update boot images, see the How to Manage Boot Images in Configuration Manager topic on the Microsoft TechNet website.

back to Table of Contents

How to determine the installation status of this cumulative update


This cumulative update changes the following Configuration Manager version numbers and installation properties.

Site systems

The CULevel value is located under the following registry subkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Setup

Note The CULevel value is set to 4 for Cumulative Update 4.

Administrator Console

The version that is displayed in the About System Center Configuration Manager dialog box is 5.0.8239.1501.

Client

The version that is displayed on the General tab of the Configuration Manager Control Panel item or the Client Version field of device properties in the Administrator Console is 5.00.8239.1501.

Endpoint Protection Client

This update changes the anti-malware client version to 4.7.0214.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client UI.

back to Table of Contents

File information


back to Table of Contents

References


For more information about how to install this cumulative update, see the following Microsoft TechNet resources:


Learn about the terminology that Microsoft uses to describe software updates.

back to Table of Contents