Description of Cumulative Update 2 for System Center 2012 R2 Configuration Manager

Applies to: Microsoft System Center 2012 R2 Configuration Manager


This article describes the issues that are fixed and functionality that is updated in Cumulative Update 2 (CU2) for Microsoft System Center 2012 R2 Configuration Manager.

Note This update is replaced by update 2994331. For more information about update 2994331, click the following article number to view the article in the Microsoft Knowledge Base:
2994331 Description of Cumulative Update 3 for System Center 2012 R2 Configuration Manager

Issues that are fixed

Administrator Console

  • When you view the Primary Device that is associated with a user, you may see other devices that have the same name, even if they are associated with a different user.
  • Inventory for enrolled devices does not show the last Policy Request time or Management Point data on the Client Activity detail tab of the device summary page.

Remote control

  • A paste operation fails when you try to copy files from a Windows Server 2012 R2 computer to a Windows 8.1 client computer in a Configuration Manager Remote Control session. Additionally, you receive the following error message:
    Unspecified Error

Mobile device management / Intune

  • Policies that apply to devices that are used together with Microsoft Intune may take 10 minutes or more to apply. Additionally, policies that are created before enrollment may not appear on the new device.
  • The Policy Request and Management Point fields for mobile devices may be missing from the Client Activity Details tab on the summary page for a given device.


  • If the maximum size of the Configuration Manager client cache is exceeded by a software update package, the cache continues to increase beyond its specified limit.

Operating system deployment

  • The Run Command Line task sequence action does not start if the package and deployment are configured to download all content locally before the action starts. This occurs only when the same package is shared across multiple task sequences.
  • The Task Sequence Agent (TSAgent) does not use the logging related values that are set in the following registry subkey on a client:


Site systems

  • The SMS Executive service may terminate and return an exception during package processing. The Crash.log file will contain entries that resemble the following (truncated for readability):

    Executable = E:\SCCM\bin\x64\smsexec.exe
    Exception = eeeeffff (EXCEPTION_SMS_FATAL_ERROR)
    Description = "Invalid params exception was raised. Expression is: []. function [], File [] Line [0]."

    This issue can occur if the following conditions are true:
    • Distribution Manager is actively retrying package distribution.
    • An entry exists under the following registry subkey:

      HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER\Retry History\<Package_ID>
    • In this subkey, Package_ID represents the actual package ID number.
    • When this distribution attempt is in progress, the Maximum Number of Retries site component setting is set to a lower value than the Number of Retries value in this registry subkey.
  • Discovery Data Records (DDRs) can be created by using an incorrect domain name when discovery runs in an environment that has a disjointed namespace.
  • Driver packages cannot be downloaded to Pull Distribution Points when the name of the source share ends in a backslash character. Errors that resemble the following are logged in the Smsdpprov.log file:

    CreateFolder failed; 0x8007007b
    CContentDefinition::ExpandContentDefinitionItems failed; 0x8007007b
    CContentDefinition::Expand failed; 0x8007007b
  • In an environment that uses only Active Directory site boundaries, Management Point location requests do not return any results when you use startup media on a client that has two or more IP addresses.

Application Virtualization

  • Modifications to App-V Virtual Environments can fail after nine revisions. Errors that resemble the following are logged in the CITaskMgr.log file:

    CAppSettingVE::DiscoverVirtualEnvironment() failed for virtual environment [VE Id: ScopeId_{guid}/VirtualEnvironment_{guid2}, Revision: 24021336]. Error: (0x80041008)
    EvalAndEnforceVirtualEnvironment failed. Error = 0x80041008 : CITask(ScopeId_{guid1}/VirtualEnvironment_{guid2}.10..Configure.Enforce)
    Note In this log entry, {guid}, {guid1}, and {guid2} all represent the actual ID numbers.

Content management

  • Client content requests do not fall back from a protected to an unprotected distribution point, even when the Allow fallback source location for content option is enabled for that distribution point.

Windows PowerShell

  • Signed PowerShell scripts do not run when the PowerShell Execution Policy client setting is configured as AllSigned. In this situation, errors that resemble the following are logged in the AppDiscovery.log file:

    In-line script returned error output: File C:\Windows\CCM\SystemTemp\<guid>.ps1 cannot
    be loaded. The file C:\Windows\CCM\SystemTemp\<guid>.ps1 is not digitally signed. The script will not execute on the system. Please see "get-help about_signing" for more details..
    At line:1 char:2
    + & <<<< 'C:\Windows\CCM\SystemTemp\<guid>.ps1'
    + CategoryInfo : NotSpecified: (:) [], PSSecurityException
    + FullyQualifiedErrorId : RuntimeExceptionFailed to perform detection of app deployment type App1 DT(App1 DT, revision 1) for system. Error 0x87d00327

    Other client components that run PowerShell scripts record similar errors.

    Note After the installation of Cumulative Update 2, the AllSigned setting functions as expected, assuming that the following conditions are true:
    • PowerShell signing certificates and their issuer's certificate that are used to sign PowerShell scripts must be pre-trusted. Otherwise, the script will not run, and you receive an error message that resembles the following:

      AuthorizationManager check failed.

    • The issuer's certificate must be in the Trusted Root Certification Authorities certificate store for the computer, and the PowerShell signing certificate must be in the Trusted Publishers store for the computer.

Learn about additional Windows PowerShell changes that are included in Cumulative Update 2 for System Center 2012 R2 Configuration Manager.

Additional changes included in this update

Non-Windows clients
This update adds Ubuntu version 14.04 to the list of supported platforms for software distribution.

The non-Windows client update that provides the corresponding Ubuntu support is available from the Microsoft Download Center. Learn about this non-Windows Client update for System Center 2012 R2 Configuration Manager.
Cloud-based Distribution Points
Newly created Cloud-based distribution points use a “Family 2” (Windows Server 2008 R2) Guest operating system. Existing Cloud-based distribution points can be upgraded to Family 2 by using the Azure portal.

Additionally, a possible race condition that affects distribution point status is resolved. For more information, see the following System Center Configuration Manager Team Blog article:

Known issues

The SQL update part of the cumulative update installation process may return a warning message if you manage mobile devices by using Configuration Manager and Microsoft Intune. This message does not stop the installation process. However, additional steps will be required to make sure that the site database is fully updated.

If this issue occurs, the installation wizard displays a warning message for the "Perform Database Update" action. Additionally, the installation log will contain entries that resemble the following:

Task status detail added: A SqlException occurred, Line Number: 0 Error: -2 Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

The configured timeout for the queries from the update installer is not sufficient for script execution on this site, to resolve this issue the update.sql script that this update has copied to the local system can be launched manually.

Task 'Perform Database Update' completed, state is 'warning' LastStatus: A SqlException occurred, Line Number: 0 Error: -2 Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

If this issue occurs, run the Update.sql script manually after the cumulative update installation is complete. Learn about how to install updates for Configuration Manager.

How to obtain Cumulative Update 2 for System Center 2012 R2 Configuration Manager

A supported update is available from Microsoft Support. However, this update is intended to correct only the issues that are described in this article. Apply this update only to systems that are experiencing the issues described in this article. This update might receive additional testing. Therefore, if you are not severely affected by these issues, we recommend that you wait for the next service pack that contains this update.

If the update is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the update.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific update. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which this update is available. If you do not see your language, it is because an update is not available for that language.

Installation information

After this cumulative update is installed on site servers, any operating system boot image should be updated. To update boot images after the hotfix 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.

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 and any associated applications such as the Remote Control Viewer or Status Message viewer before you install this update.
You may be prompted to restart the computer to which the Administrator Console update is being applied if the Remote Control Viewer (CmRCViewer.exe) is being used during the update process.
This can be avoided by closing the Remote Control Viewer before you install the update, or by adding the REBOOT=ReallySuppress parameter to the update installation properties. 

Update replacement information

This update replaces Cumulative Update 1 for System Center 2012 R2 Configuration Manager.

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:


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

Administrator Console
The version that is displayed in the About System Center Configuration Manager dialog is 5.0.7958.1303.

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


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

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