.png){kind=spacer}
Software Update Management
SMS 2003 includes a software update management feature. Some components of this feature are automatically installed with SMS 2003. Other components require a Web download and separate installation on the site server. See Table 14.3 for component installation information.
Earlier versions of the software update management components were released as value-added features in the SMS 2.0 Software Update Services Feature Pack. For information about upgrading SMS 2.0 sites that have the software update management tools previously installed, see the "Upgrading SMS 2.0 Software Update Management Features to SMS 2003" section later in this chapter.
For system requirements, see the "Getting Started" chapter in this book.
For information about interoperability issues in a mixed-site hierarchy, see Chapter 6, "Understanding Interoperability with SMS 2.0."
Installation
Table 14.3 shows the components and installation details of the SMS 2003 software update management feature.
Table 14.3 Software Update Tool Installation Details
|
Feature |
Installation Details |
|---|---|
|
Distribute Software Updates Wizard |
Installed by default on the SMS 2003 site server and SMS 2003 Administrator console. |
|
Software updates installation agent |
Installed by default on the SMS 2003 site server. Distributed to SMS client computers automatically when you run the Distribute Software Updates Wizard to create and advertise software update packages. |
|
Software update reports |
Installed by default on SMS 2003 reporting points and the SMS 2003 Administrator console. |
|
Security Update Inventory tool |
Download from the Web at http://www.microsoft.com/smserver/downloads. Separate installation on an SMS site server. |
|
Microsoft Office Inventory tool for updates |
Download from the Web at http://www.microsoft.com/smserver/downloads. Separate installation on an SMS site server. |
Upgrading SMS 2.0 Software Update Management Features to SMS 2003
Table 14.4 lists the actions that are required for upgrading an SMS 2.0 site to SMS 2003 when the SMS 2.0 versions of the SUS Feature Pack tools are already installed.
Table 14.4 Software Update Tool Upgrade Requirements
|
Feature |
Action |
|---|---|
|
Distribute Software Updates Wizard |
Remove the SMS 2.0 version before upgrading to SMS 2003. You can keep associated programs, advertisements, and packages that were created with the wizard. For information about upgrading SMS 2.0 software update packages to SMS 2003, see the "Software Update Management" section in Chapter 6, "Understanding Interoperability with SMS 2.0." |
|
Software updates installation agent |
No separate action required. The SMS 2.0 version of this component is removed when you remove the Distribute Software Updates Wizard from the SMS Administrator console, but this component remains in the packages previously created by the Distribute Software Updates Wizard to ensure that these packages are not broken during migration or upgrade. |
|
Web reporting add-in |
Remove the SMS 2.0 version before upgrading to SMS 2003. This feature is replaced with the Reporting features in SMS 2003. |
|
Software update reports |
If you created any custom software update reports, save them to a file so you can import them into SMS 2003 Reporting. |
|
Security Update Inventory tool Microsoft Office Inventory tool for updates |
As a best practice, remove these tools and install the SMS 2003 versions by using the following procedure after you finish installing and configuring SMS 2003. |
Use the following procedure to upgrade the SMS 2.0 version of the Security Update Inventory tool to the SMS 2003 version.
To upgrade the SMS 2.0 Security Update Inventory tool to the SMS 2003 version
Important
-
The following procedure upgrades the Security Update Inventory tool and its associated collections, packages, programs, and advertisements to SMS 2003 versions. While it does not remove these objects from the SMS site database, the upgrade process replaces any custom properties you set on these objects with the default values. If you have made such changes and want to preserve them, make a note of the configuration settings for these objects before you perform this upgrade.
-
On an SMS 2003 site server, download the installation program for the tool from http://www.microsoft.com/smserver/downloads.
-
Run the installation program (SecurityPatch_xxx.exe, where xxx is the locale code of the package; for example, SecurityPath_ENU.exe for the English language version).
-
When prompted to remove the previous version, click OK.
-
When prompted to remove packages, collections, and advertisements, click No.
-
When prompted to replace the existing package, collections, and advertisements during the installation of the new version, click OK.
-
Following setup, review the configuration settings for the collections, packages, programs, and advertisements for the tool. If necessary, replace the default settings with the custom settings appropriate for your site.
This procedure describes the process of upgrading the Security Update Inventory tool. To upgrade the Microsoft Office Inventory tool for updates, follow the same steps, but substitute the file name OfficePatch_xxx.exe for SecurityPatch_xxx.exe.
Other Issues Affecting an Upgrade
The following are other points to consider when performing an upgrade of the SMS 2.0 version of the software update management tools:
-
SMS 2.0 software update packages created by the Distribute Software Updates Wizard are only upgraded to SMS 2003 packages when they are opened and saved in the SMS 2003 version of the Distribute Software Updates Wizard. For more information, see the "Software Update Management" section in Chapter 6, "Understanding Interoperability with SMS 2.0."
-
The SMS 2.0 Administration Feature Pack tools are not compatible with SMS 2003. You should remove these tools prior to an upgrade of the SMS 2.0 Administrator console to SMS 2003. Compatible versions of these tools will be available for SMS 2003, but are not included in this release.
For More Information
Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.
