The Configuration Manager 2007 Documentation Library and the Documentation Library for System Center 2012 Configuration Manager have been updated on the web and the latest content has Updated: February 1, 2012 at the top of the topic.
You might have noticed that the default view for TechNet is now Lightweight, rather than Classic. And that the Lightweight view has replaced the star rating with the simpler “Did you find this helpful? Yes/No feedback mechanism. If you want to return to the familiar Classic view, click the Preferences icon in the top right of the page. Then, from the Choose View page, click Classic.
One disadvantage that we’ve found with the Lightweight view is that it doesn’t have the Collapse All/Expand All control in the top left of the page. When you search on a page (Find) that has collapsed sections, search will not find text in sections that are collapsed. An easy way around this, is to click Expand All before you search on a page. However, this capability is not included in the Lightweight view. In both views, search finds topics even when sections are collapsed; the limitation applies to searching on a page.
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 Configuration Manager 2007 Documentation Library for February 2012
The following information lists the topics that contain significant changes since the January 2012 update.
Planning for PXE Initiated Operating System Deployments
- Updated to clarify that only boot images can be distributed to a PXE service point.
How to Create an Exclusion List for Unknown Computer Support
- Updated to add information about how to create a MACIgnoreListFile registry key for 64-bit servers.
What's New in the Documentation Library for System Center 2012 Configuration Manager, February 2012
Supported Configurations for Configuration Manager
- Updated the site system role prerequisites and added the minimum hardware requirements for site systems.
Planning for Hardware Configurations for Configuration Manager
- New topic that provides hardware guidance for large sites in production environments.
Configure Database Replicas for Management Points
- New topic about how to configure a SQL Server replica for the site database.
Planning for High Availability with Configuration Manager
- New topic that lists the high availability options that Configuration Manager supports.
Install a Configuration Manager Console
- Updated section in the Manage Site and Hierarchy Configurations topic that provides information about how to install the Configuration Manager console by running the Configuration Manager Console Setup Wizard, or by using a command prompt.
Configuration Manager Unattended Setup
- Updated section in the Manage Site and Hierarchy Configurations topic that provides information about how to install Configuration Manager by creating an unattended installation script and running Setup with the /script command option.
Configure the Site Database to Use a SQL Server Cluster
- New section in the Manage Site and Hierarchy Configurations topic that provides information about using a virtual Microsoft SQL Server cluster instance to host the Configuration Manager site database.
Unattended Site Recovery Script File Keys
- New section in the Backup and Recovery in Configuration Manager topic about how to recovery the site by using an initialization file with the /script Setup command-line option.
How to Install Clients on Windows Computers in Configuration Manager
- Updated the sections about upgrading the client by using a package and program, and by using automatic client upgrade.
How to Assign Client Computers to a Site in Configuration Manager
- Clarified that a Configuration Manager 2007 can successfully assign to a System Center 2012 Configuration Manager site, but that this scenario is to support automatic client upgrade only. Until the client is upgraded to System Center 2012 Configuration Manager, the client will not install settings, applications, or software updates.
What’s New in Configuration Manager
- Updated the Client Status section to remove the information about Active Directory last logon time, and updated the Hardware Inventory section to clarify that the sms_def.mof file is no longer used in System Center 2012 Configuration Manager.
Configuring Software Updates in Configuration Manager
- Updated the steps for configuring software updates to prevent unwanted software updates from being synchronized.
Operating System Deployment in Configuration Manager
- This section has been updated for the following topics:
Technical Reference for the Hierarchy Maintenance Tool (Preinst.exe) in Configuration Manager
- New topic that covers how and when to use the Hierarchy Maintenance tool.
Technical Reference for the Icons Used for Software Updates
- New topic that lists and explains the icons that software updates uses.
Technical Reference for Accounts Used in Configuration Manager
- Fixed the publishing problem that we reported last month, so that now the group names that end in _<sitecode> are no longer listed as _[sitecode].
Frequently Asked Questions for Configuration Manager
- Updated with new entries that include the following:
-- The Configuration Manager Writing Team
This posting is provided "AS IS" with no warranties and confers no rights.
Too bad we'll never see this due to the new SCCM Server OS Client Licensing. Any company that manages servers with SCCM will see at least a 10X increase in cost. That's only for 2 procs.
New section in the Backup and Recovery in Configuration Manager is nicely explained.
Congratulations, all new and improved documentation is much appreciated.
You mention near the top that you have clarified that only boot images can be distributed to a PXE service point. This is of course both correct and well worth pointing out, but an error that I have seen at a great deal of sites, and which also creates a lot of posts in the forums, is because of the opposite: The need to have the boot images on an ordinary distribution point as well as on the PXE service point.
Maybe this also deserves some clarification?