|KB article number||KB title|
|SQL Server cumulative updates must be manually installed on secondary System Center 2012 Configuration Manager sites that use SQL Server Express|
|The Apply button is unavailable after clearing the “Enable PXE support for clients” option on a System Center 2012 Configuration Manager Distribution Point|
|Changing the SQL Service Broker port while performing a System Center 2012 Configuration Manager site recovery causes the site to remain in Maintenance Mode|
|Multiple error messages are logged in the System Center 2012 Configuration Manager Distmgr.log file when you update shared Distribution Points|
|The status of a failed upgrade to a shared Distribution Point may be displayed incorrectly as “Failed to upgrade distribution point” in System Center 2012 Configuration Manager|
|Different results are displayed for software updates when you use saved searches in non-English versions of System Center 2012 Configuration Manager|
|You cannot reinstall a System Center 2012 Configuration Manager SMS Provider on a server had the same provider previously uninstalled|
|A System Center 2012 Configuration Manager Distribution Point contains no deployment package after using the Download Software Updates wizard|
|An incorrect number of computers is displayed in the Antimalware Activity report in System Center 2012 Endpoint Protection|
|You cannot use the “New Account” option to reset the password on the Active Directory forest discovery account in System Center 2012 Configuration Manager|
|WDS does not start on a PXE enabled remote Distribution Point in System Center 2012 Configuration Manager|
|Changing a property of a deployment appears to not be saved in System Center 2012 Configuration Manager|
|A PXE enabled Distribution Point that uses a self-signed certificate will generate many files in System Center 2012 Configuration Manager|
|Using the System Center 2012 Configuration Manager CMTrace log viewer to review a log that contains a line exceeding 8000 characters causes the log to be truncated|
|Remote Control fails with error C000012 in System Center 2012 Configuration Manager|
|Issues with System Center 2012 Configuration Manager Application Evaluation if a third party deployment type is not registered properly on a client|
|After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update package or a new application fails|
|Description of Cumulative Update 1 for System Center 2012 Configuration Manager|
|Description of Cumulative Update 2 for System Center 2012 Configuration Manager|
|Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation|
Resolutions to the following issues are also included in System Center 2012 Configuration Manager SP1.
- Setting a schedule in the future for a Software Updates deployment is working now as intended fixing an issue where TSInstallSWUpdate would previously stall and time out.
- The table ClientModeReadiness is now fully replicated. This fixes a previous issue where the report “Count of clients capable of HTTPS communication” would not return data when run on the CAS or would only return data for a particular primary server the report was run from.
- Installing a remote distribution point and specifying a local site system installation account, as opposed to a domain account, now no longer creates an untrusted login error.
- File names with a hash mark (#) are now properly encoded during download.
- Configuration Manager sites can now be used to back up a Remote SQL Server using the UNC path.
- In System Center 2012 Configuration Manager RTM, large database modifications included in a single transaction sometimes caused the replication system to take a long time to extract the change and send it over to another site. In SP1, large modifications are no longer allowed in single transaction.
- When using a variable list to dynamically install a list of applications within a task sequence, if one of the applications cannot be installed because the content is unavailable, policy provider no longer blocks and prevents all other applications from being installed.
- Task Sequences no longer experience significant processing delays or time outs due to large numbers of install software steps within the sequence when clients have slow or poor connections to the management points.