This month sees additional prerelease information for System Center 2012 R2 Configuration Manager, as well as updates to release versions.

We value customer feedback and try to incorporate it when possible. Although we can’t promise to make the docs perfect for everybody, we are committed to continual improvement. So, keep that feedback coming, and feel free to contact us about anything related to the documentation by using our usual address of SMSDocs@Microsoft.com.

What’s New in the Documentation Library for System Center 2012 Configuration Manager, September 2013

The following information lists the topics that contain significant changes since the August 2013 update.

Based on customer feedback, updated the details for the Configuration Manager console requirements to include the .NET Framework 4.0 full version.

Support for Windows 8.1 and Windows Server 2012 R2 with Configuration Manager SP1, when you use cumulative update 3.

Version details for Android and for mobile devices supported by the Windows Intune connector. The table that presents this information has also been restructured to improve readability.

Replaced details about the interoperability of the Configuration Manager console with a link to the Interoperability between Different Versions of Configuration Manager topic, where this information now appears. This information was also updated to provide better details about interoperability between service pack releases of System Center 2012 Configuration Manager.

Updated the SQL Server requirements (for the site database) to confirm that different sites in a hierarchy can use different versions of SQL Server than that in use by other sites, providing the version is supported by Configuration Manager.

IPv6 support excludes operating system deployment, which requires IPv4.

– Updated the site expansion section to identify the permissions that the user account that runs Setup (to install the central administration site a part of a site expansion) must have at the stand-alone primary site that is being expanded.

– Updated with the clarification that clients that use cloud-based distribution points are not aware of Windows Azure regions, and non-deterministically select any offered cloud-based distribution point.

– Based on customer feedback, added additional information about the ports that you must open during the installation of a site that uses a SQL Server on a different computer from the site server. This topic also includes an update for the port communication (DCOM) that the site server uses to send revocation commands to the issuing CA to revoke certificates that were deployed by using certificate profiles. These certificates are revoked when a device is retired from management, is selectively wiped, or blocked from the Configuration Manager hierarchy.

Join the conversation

Recent Posts from EMS Leaders

Since we first released Azure Information Protection (AIP) on October 1st, we have been busy helping, visiting, and listening to customers worldwide. Our engineering team has also been working hard on rapidly delivering previously requested updates and several new features. Today we are making available a new preview release!... Read more

As 2016 draws to a close, we would like to thank you for choosing Microsoft Enterprise Mobility + Security (EMS) to protect and secure your employees as you continue to digitally transform your organizations. More than 37,000 customers and over half of the Fortune 500 have now chosen EMS.... Read more

On June 22nd, we announced Microsoft Azure Information Protection (AIP), a new service that builds on both Microsoft Azure Rights Management (RMS) and our recent acquisition of Secure Islands. This was quickly followed by the first Preview on July 12th, delivering a comprehensive classification, labeling and protection solution to the market. Today we’re excited to announce that Azure Information Protection is now Generally Available (GA)! ... Read more