Chris Nackers

ConfigMgr / SCCM

System Center 2012 Configuration Manager - CU2 Available

2012-11-27

From the archive (2012). Written for the tools of the time, so some details may be out of date.

Download here.

Issues that are fixed
Operating System Deployment
  • When dynamic media is used to deploy an operating system to a computer that was imported into the database together with a computer name, the correct name is not applied. Instead, the computer is named “MININT-xxxxx.”
    Note “xxxxx” is a placeholder for a 5-digit number.
Site Systems

  • Assume that a Discovery Data Records (DDRs) message contains several organizational unit (OU) paths that are longer than 220 characters. In this situation, the message is not processed by Data Discovery Manager. Additionally, the DDM.log on the site server contains events that resemble the following:CDiscoverySource::ValidateSchema - array property User OU Name can not expand size so rejecting.
    CDiscoverDataManager::ProcessDDRs - Unable to update data source

  • The SMSDBMon component cannot write a file whose file name contains over 260 characters. Additionally, the Smsdbmon.log file contains events that resemble the following:Warning: Could not create file E:\SCCM\inboxes\ccr.box\308202FC308201E4A0030201020210149EC80845C6C08E4A6CB705563CF87E300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3132303630353030303830305A180F32313132303531333030303830305A3016311430120603550403130B5369746520536572766572.CPC, Error=3.

  • After you install Cumulative Update 1 for System Center 2012 Configuration Manager, the status of a management point site incorrectly reports 0 bytes of available disk space.
    For more information about Cumulative Update 1, click the following article number to view the article in the Microsoft Knowledge Base:
    2717295 Description of Cumulative Update 1 for System Center 2012 Configuration Manager

  • When SMS Executive cannot access source files for an application among several applications, you cannot use Dynamic Variables in task sequences to deploy these applications.

Application Management
  • If the requirements of an application contain Service Pack 1 or specific values, the application will fail its application model evaluation. Therefore, the application has a Requirements not metentry when it is displayed in Software Center on a client computer. Additionally, the DCMReporting.log file on the client computer contains events that resemble the following:Targetting of CI is Version Specific
    CDCMReporting::AddPoliciesForCI
    GetInstanceFromLantern failed (0x80041002).

Additionally, the Smsts.log file on the Configuration Manager client will contain events that resemble the following if the application is made available for installation from a task sequence:

Start to compile TS policy
Failed to load property ‘Order’. Error 0x80041002
Failed to load policies from XML.
Not found (Error: 80041002; Source: WMI)
End TS policy compilation
Step 2 out of 2 complete
Install application action failed: ‘Sample App’. Error Code 0x80041002

  • Update 2744420 is included in this update.
    For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    2744420 Update supports Alternate Content Provider in Task Sequence in System Center 2012 Configuration Manager

Asset Intelligence

  • Windows 8 and Microsoft Office 2013 suites are not reported correctly in Asset Intelligence reports.
Site Database
  • When a site is migrated to System Center 2012 Configuration Manager, any direct membership collection rules that were created in Microsoft System Center Configuration Manager 2007 might be removed.