http://support.microsoft.com/kb/2717295

Issues that are fixed

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

        (http://technet.microsoft.com/en-us/library/988b456a-efa8-45d1-89a6-894585dfca38#BKMK_PrestageContent)    

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.

Client

• 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:
  3999
• 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:

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

Known issues

Update of the Administrator Console

When the Administrator Console is first installed, a copy of the Adminconsole.msi file is cached in the %Temp% folder of the user who initiated the installation. If that MSI file is missing, the Configmgr2012adminui-rtm-kb2717295-i386.msp update file may not be applied. When this update is distributed by using Software Distribution, the installation may fail, and an exit code of 1603 is logged in the excecmgr.log file.

To resolve this issue, reinstall the original release of the Administrator Console by using Consolesetup.exe, then apply this update.