Topic last updated—November 2007
This topic provides information about troubleshooting software update deployment issues in Configuration Manager 2007.
Software Updates Are Downloaded in
Deploy Software Updates Wizard When They Have Already Been
Downloaded
When creating a software update deployment that will target Systems Management Server (SMS) 2003 clients and at least one software update has not yet been downloaded, all the software updates not in the package configured for the deployment will be downloaded even when they were previously downloaded to another package. When all software updates have been downloaded prior to creating the deployment, when the downloaded updates were previously downloaded to the package selected in the deployment, or when the Deploy software updates to SMS 2003 clients setting is not selected in the deployment, the wizard downloads only the software updates that have not been previously downloaded.
Possible Solution
To prevent this behavior, download the software updates that have not yet been downloaded prior to creating the deployment by using the Download Updates Wizard or the Update List Wizard.
The Deploy Software Updates Wizard
Prompts for Download Settings for Software Updates That Are Already
Downloaded.
When software updates are downloaded to a deployment package by using the Download Updates Wizard or the Update List Wizard and then the same software updates are selected for deployment before refreshing the software updates list view in the Configuration Manager console, the Deploy Software Updates Wizard will prompt for the download settings, making it appear as if the software updates will be downloaded to the package again.
Possible Solution
The software updates will not be downloaded again to the deployment package. The Deploy Software Updates Wizard will verify that the files are in the package and skip the download process. To prevent this behavior, refresh the software updates list view in the Configuration Manager console after downloading software updates and prior to deploying them.
Downloading Large Software Update
Files Might Fail
If you run the Configuration Manager 2007 console on Microsoft Windows Server 2003 or Windows XP computers, downloading large software updates might fail due to a known issue with operating systems earlier than Windows Vista. For example, when you use the Download Updates Wizard, Deploy Software Updates Wizard, or Updates List Wizard to download a large service pack, you might see the error "invalid certificate signature" in the confirmation page of the wizard.
Possible Solution
One of the following workarounds might resolve this issue:
- Close the wizard, restart the Configuration
Manager 2007 console, and attempt to download the large software
update again.
- Run the Configuration Manager 2007 console on
a computer running Windows Vista.
Failed to Deploy Migrated Software
Updates
During the upgrade process, Configuration Manager 2007 Setup appends (LEGACY) to the title for each software update. This helps you identify software updates that were migrated among the new software updates metadata that is synchronized after the upgrade. Software updates with (LEGACY) in the title should not be deployed to clients and are migrated only for software update distributions that were also migrated and for reporting purposes.
Possible Solution
You can run a script to hide these software updates in the Configuration Manager console so that only deployable software updates are displayed. A sample script is available from the Microsoft Script Center Script Repository (http://go.microsoft.com/fwlink/?LinkId=102377).
 Note |
|---|
| Migrated software updates that are in a software update deployment that was also migrated will not be hidden until the migrated deployment is deleted or the updates are removed from the deployment. |
Failed to Deploy Metadata-Only
Software Updates
| Note |
|---|
| The information in this section applies only to Configuration Manager 2007 SP1. |
Metadata-only software updates are available in the Configuration Manager console for reporting and cannot be deployed or downloaded.
Possible Solution
The metadata-only software update must be associated with an update file and republished to Windows Server Update Services (WSUS) running on the active software update point before it can be deployed.