[Today’s Post is provided by the Configuration Manager Writing Team]
The Configuration Manager documentation library (http://technet.microsoft.com/en-us/library/bb680651.aspx) has been updated on the Web and the following information lists the topics that are new or contain significant changes since the June 2009 update. The latest content that has been updated on the Web has Updated: July 1, 2009 at the top of the topic.
We don’t have as many updates for you this month, because we’ve been working on documentation for Service Pack 2 (to be included with Configuration Manager 2007 SP2 RC) and the SuperFlows. The updates that we have come from customer feedback. 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 Configuration Manager Documentation Library for July 2009
The following information lists the topics that are new or contain significant changes since the June 2009 update:
– Updated to include the support statement that Configuration Manager clients are not support with Network Address Translation (NAT), unless the site is configured for Internet-based client management and the client detects that it is on the Internet.
– Updated to include a feature section for Out of Band Management. This includes the versions of AMT that are supported, operating system limitations for the out of band management console, and the support statement that out of band communication to an AMT-based computer is not supported if it is running the Routing and Remote Access service in the client operating system.
– Updated with the new entry “Security Registry Keys for Native Mode Remain in Captured Images”. This issue was reported in the forums when a customer used a captured image from a native mode client that used a different CA hierarchy to the one used on the production network, and it resulted in the client being unmanaged. This troubleshooting entry includes the prescribed additional steps to take if you capture an image from a native mode client. .
– Updated with the new entry “Task Sequence Always Performs Certificate Revocation Checking in Native Mode Site”. This issue documents how to identify a known issue with task sequences always checking the CRL in a native mode site, even after following the procedures to disable CRL checking on clients. In this scenario, if the CRL cannot be accessed, all native mode communication will fail and the smsts.log file will record: WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED.
This posting is provided “AS IS” with no warranties and confers no rights.