This month's updates are primarily for revisions based on customer feedback. We do 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
What's New in the Configuration Manager Documentation Library for December 2009
The following information lists the topics that contain significant changes since the November 2009 update.
- Updated for the information regarding the client certificate, which is not used for authentication to the software update point. Unlike the other native mode site systems, the software update point doesn't use mutual authentication and uses server authentication only. Other topics have been updated to clarify this exception, including
Benefits of Using Native Mode
- Updated with the important clarification that you cannot create NAP policies on a site that is inheriting software updates from a parent site. When you configure software updates synchronization with Microsoft, make sure that you configure this synchronization on the site from which you want to create Configuration Manager NAP policies.
- Updated to clarify that when CCMSetup reads client installation properties that are published to Active Directory Domain Services, the default management point is always returned as the location from which clients download installation files. This means that if clients are within the boundaries of a secondary site that contains a proxy management point, they will still download the client source files from the primary site.