Announcement: Configuration Manager Documentation Library Update for December 2008

  • Article

No, there’s no new release of the software this time. But that didn’t stop us from continuing to make revisions and additions to the Configuration Manager documentation library. The library is now updated on the Web: TechNet Configuration Manager documentation library.

For a list of topics that have had a significant technical change since the R2 release in August, see What's New in the Configuration Manager Documentation Library for December 2008.

Of particular note for OSD admins, the task sequence actions (AKA steps) and their related variables have been updated to better describe each action’s significance in the OSD process. Additionally, task sequence variable descriptions now specify whether they are written (output) or read (input) by a specific task sequence action, with examples where possible.

You will also want to check out the updated Support Configurations topics, which now include information about the use of SQL Server 2008 to host the site database, and support for Windows Server 2008 Hyper-V, Windows XP Professional SP3, and Windows Mobile 6.1.

All topics that have been changed for this update have at the top Updated: December 1, 2008. This includes any topics from RTM, SP1 and R2 that have significant technical changes, and also topics that have had minor updates such as non-technical typos and minor clarifications.

Not listed in the What’s New topic, but updated with the information we provided on this blog as a result of customer issues from the forums:

· How to Configure the WSUS Web Site to Use SSL

· Ports Used in Software Updates

· How to Configure the Active Software Update Point Component to Use an NLB Cluster

In addition to the Library, we’ve now published the following to the Web:

· Creating Custom Reports by Using Configuration Manager 2007 SQL Views

· Configuration Manager 2007 Client Status Reporting

Most of the documentation changes are a result of customers contacting us with questions, requests for clarifications, and notifying us of omissions and typos – so thank you for helping to improve the documentation for others. We do value your feedback and try to incorporate it when possible.

Keep that feedback coming, and contact us on our usual address of SMSDocs@Microsoft.com.

- Carol

This posting is provided AS IS with no warranties and confers no rights.