The Documentation Library for System Center 2012 Configuration Manager and the Configuration Manager 2007 Documentation Library have been updated on the web and the latest content has Updated: September 1, 2013 at the top of the topic.
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.
– Updates include the following:
- 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 the Considerations for Placement of Site System Roles table in the Planning Where to Install Sites System Roles in the Hierarchy section for new information about the certificate registration point.
– 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.
– Updated the prerequisites for Configuration Manager SP1 with a note about the limitations of support for using the Windows ADK with Windows 8.1 and Windows Server 2012 R2.
– Added the following new questions:
- Is there a limit to the number of certificate templates that I can use with certificate profiles?
- Do I really need Windows Server 2012 R2 to deploy certificate profiles?
- When I view the report named Distribution Point Usage Summary, why do I see a value for more clients than I expect to see in the column named Client Accessed (Unique)?
- Why does the value for Bytes Sent (MB), in the Distribution Point Usage Summary report, not always reflect the actual volume of data I deploy?
What’s New in the Configuration Manager 2007 Documentation Library for September 2013
The following information lists the topic that contains a significant change since the August 2013 update.
– Based on customer feedback, updated to correct the name of the discovery log file. It was documented as ntsvdis.log and the correct name is ntsvrdis.log.
This posting is provided “AS IS” with no warranties and confers no rights.