Release Notes for System Center 2012 Configuration Manager
Updated: January 14, 2013
Applies To: System Center 2012 Configuration Manager
To search these release notes, press Ctrl+F.
Read these release notes thoroughly before you install Microsoft System Center 2012 Configuration Manager.
These release notes contain information that is required to successfully install System Center 2012 Configuration Manager. These release notes also contain information that is not available in the product documentation.
|If there is a discrepancy between these release notes and other Configuration Manager documentation, the most recent version should be considered authoritative.|
If you want to provide feedback, make a suggestion, or report an issue with Microsoft System Center 2012 Configuration Manager, use the Microsoft Connect site.
For supported configuration information, see Supported Configurations for Configuration Manager.
For documentation for System Center 2012 Configuration Manager, see the Documentation Library for System Center 2012 Configuration Manager. If you have feedback about the documentation, email SMSDocs@Microsoft.com.
Because many features and their underlying infrastructure have changed significantly since System Center 2012 Configuration Manager Beta 1, System Center 2012 Configuration Manager Beta 2, and the Release Candidate, you cannot upgrade these prerelease versions to System Center 2012 Configuration Manager. If you have installed a prerelease version of System Center 2012 Configuration Manager, uninstall it before you install System Center 2012 Configuration Manager. We recommend that you also uninstall and reinstall the operating system after you uninstall a prerelease version of Configuration Manager and before you install the released version of System Center 2012 Configuration Manager.
In addition, Configuration Manager does not support the import of objects from a prerelease version of System Center 2012 Configuration Manager to the released version of System Center 2012 Configuration Manager.
System Center 2012 Configuration Manager does not support an in-place upgrade from Configuration Manager 2007, but System Center 2012 Configuration Manager does support a side-by-side migration.
You can use System Center 2012 Configuration Manager to create migration jobs that migrate objects and content from Configuration Manager 2007 to System Center 2012 Configuration Manager. Additionally, when you migrate Configuration Manager 2007 to System Center 2012 Configuration Manager, you can upgrade a Configuration Manager 2007 distribution point to a System Center 2012 Configuration Manager distribution point. You can upgrade branch distribution points, distribution points on server shares, and standard distribution points from Configuration Manager 2007. You can also upgrade a distribution point that is co-located on a secondary site server. This action uninstalls the secondary site and leaves the distribution point installed. System Center 2012 Configuration Manager does not upgrade primary sites, or any other site system role.
For information about migration, see the Migrating Hierarchies in System Center 2012 Configuration Manager guide.
This section provides the most up-to-date information about issues with System Center 2012 Configuration Manager. These issues do not appear in the product documentation, and, in some cases, might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
When you migrate a Configuration Manager 2007 configuration baseline to System Center 2012 Configuration Manager, the hash of the configuration baseline digest is changed but the version number is not. Because the hash has changed, Configuration Manager queues a request to delete the existing configuration baseline and then downloads the modified configuration baseline. If the client computer or the client service (ccmexec) restarts before completing the delete request, the client does not download the new configuration baseline because the version number is the same as the one that currently exists.
In this scenario, you see error 87d00315 (The CI version info data is not available) on the Deployment tab in the Monitoring workspace.
WORKAROUND After the configuration baseline is migrated, modify it, which automatically increments the version number. For example, make a change to the description of the configuration baseline.
When you enable a software update-based client deployment, the Configuration Manager client does not publish to the software update point. The following error is logged in the WCM.log file:
ERROR: Failed to publish sms client to WSUS, error = 0x80131622
WORKAROUND Download the following software update, and then install it on all site system servers that run the software update point site system role: Update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 for x64-based Systems (KB2530678).
For more information about this software update, see System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4 are installed.
When you configure the Endpoint Protection client setting Automatically remove previously installed antimalware software before Endpoint Protection is installed, Symantec AntiVirus Corporate Edition version 10 and Symantec Endpoint Protection version 11 are not automatically uninstalled on 64-bit computers.
WORKAROUND Manually uninstall these products. Or, install System Center 2012 Configuration Manager SP1.
For additional resources, see Information and Support for Configuration Manager.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.