Configuration Manager client computers no longer use a variety of inventory scan tools to scan for software update compliance, but instead the Windows Update Agent (WUA) on client computers. There are several inventory scan tools in SMS 2003 that scan client computers for software update compliance. When a site is upgraded to Configuration Manager 2007 and the Inventory Tool for Microsoft Updates is found on the site server, most likely the central site, the tool is automatically upgraded. After the upgrade, the Inventory Tool for Microsoft Updates is fully operational for SMS 2003 client computers at the site, the Inventory Tool for Custom Updates is supported, but with conditions, and the other scan tools have very limited support. Using the scan tools on Configuration Manager 2007 client computers is not supported. For more information, see Planning the SMS 2003 Software Updates Upgrade.

SMS 2003 displayed the same software update multiple times in the SMS Administrator console for each language and product for the update. Configuration Manager 2007 has introduced the concept of software update bundles, where a software update is displayed only once in the Configuration Manager console. Software update deployments are initiated by selecting the bundle update, and when creating the deployment the administrator can define which language specific update files will be downloaded and made available to client computers.

Note
After upgrading from SMS 2003, software updates that existed for each language and product are still displayed in the Configuration Manager 2007 console and to the client if they are available to install, but they have the word Legacy appended to them.

Supersedence is when a new software update contains the same fixes that were in a previously released software update. In the past, new and previously released software updates, which contained the same fix, might have both been marked as required when the only one that was necessary was the newer software update.

In Configuration Manager 2007, software updates uses the Windows Update Agent which partially addresses the issue of supersedence. When new software updates are released that contain fixes for previously released updates, Microsoft Update is refreshed with information relating to the new software update and any software updates that it supersedes. As client computers scan for software update compliance, any required software updates that supersede previous updates are returned with compliance state but the previously released software updates are not returned. The exception to this is when a Service Pack contains a required software update. The Windows Update Agent returns both the software update and the service pack with a required compliance state. This provides administrators with the flexibility to deploy individual software updates or full service packs.

Configuration Manager 2007 no longer uses advertisements for delivering software updates. Software update deployments are now used as the vehicle that delivers software updates to client computers. The deployment properties contain the relevant information about the software updates in the deployment, the target collection, the settings that impact client behavior when running the deployment, the deployment schedule settings, and so on. When a deployment is created, client computers receive it as part of the Configuration Manager policy. For more information, see About Software Update Deployments.

Deployment packages are used to host the files for the software updates in a deployment, much like that of software distribution packages. The main difference is that the deployment package is used to get the files to the distribution points, but once that process completes, client computers will access the software update files from any package shared folder on any distribution point regardless of whether the package was defined in the deployment that targeted the client. When the client computer receives a new deployment, it determines where the software update files are located, independent of the deployment, and install from the preferred location. For more information, see About Software Update Deployment Packages.

Selective Download

Deployment templates provide the ability to save a set of deployment properties for use in future software update deployments. When a deployment template is used in creating a new deployment, it populates the deployment with the preconfigured properties. This provides consistency among deployments with similar requirements and saves a lot of administration time. For more information, see About Deployment Templates in Software Updates.

Update lists provide the ability to initiate a deployment for a set of software updates contained in the list. Using the update list provides several benefits when deploying and monitoring software updates and is, therefore, part of the recommended software updates workflow. Update lists allow administrators to create a deployment from the update list instead of manually selecting the set of updates every time a new deployment is created. They allow administrators to use reports for specific update lists to monitor the compliance for the software updates and help to troubleshooting updates contained in the list. Update lists also allow administrators to create update lists with approved updates, and then delegate the responsibility to deploy the update lists. For more information, see About Update Lists in Software Updates.