Office 2003 Hotfix Deployment -----------------------------------To support the Windows Installer features of self-repair, installation-on-demand and reinstall, Office

2003 must be able to control how its files are updated. If we simply replace a file with a newer updated version without alerting the Wi ndows Installer, we lose the ability to repair or reinstall the file later if ne cessary. The file will instead be replaced by the old version and we will lose the hotfix. For these reasons, hotfixes for Office 2003 are deployed as Windows Installer pa tch packages (.msp files). These packages have all the information necessary to properly update the Windows Installer database for Office 2003. (See MSDN for complete details: http://msdn.microsoft.com/library/default.asp?url=/library/en -us/msi/setup/overview_of_windows_installer.asp) For Office specific deployment details, see the on-line Office Resource Kit: http://www.microsoft.com/office/or k. Note that there are specific problems associated with applying Outlook hotfixes to installations using the previous service pack. Please refer to the following Knowledge Base article for more information: http://support.microsoft.com/?id=830001 Each Office 2003 hotfix is delivered in two forms: a Full-File patch and a binar y patch. Hotfix Full-File Patch: -------------------------This is a Windows Installer patch package that uses full-file replacement for th e affected files. This can be applied to any Office 2003 administrative installa tion point that is at the required service pack level, regardless of whether oth er hotfixes have been applied. The following command line applies the patch to the administrative installation point: [start] msiexec /a [path to admin image .msi file] /p [path to patch .ms p file] SHORTFILENAMES=TRUE Any subsequent client installation from this image will include the latest versi on of the files. Existing clients will need to recache and repair to this admin istrative installation point after the patch is applied by using the following c ommand line: [start] msiexec /i [path to updated .msi file on the admin image] REINST ALL=[list of features] REINSTALLMODE=vomu [list of features] should be replaced with either "ALL" (without the quotes) or the following list of features specific to the product being updated: <List of Features>

To apply the full-file patch to a client installation: Alternatively, the full-file patch package can be applied to a client computer. There are a variety of methods available to distribute MSP files to client compu ters, such as an e-mail message, a logon script or Microsoft Systems Management Server. Once the file is delivered to the client computer, users can double-cli ck the MSP file to apply the patch to the local computer. The patch can also be run using the following command line: [start] msiexec /p [path\name of update MSP file] Hotfix Binary Patch ----------------This is a Windows Installer patch package that uses binary patching for the same set of affected files as in the hotfix full-file patch. It can be applied to a client installation which has access to the administrative installation point o r the original CD. There are a variety of methods available to distribute MSP files to client compu ters, such as an e-mail message, a logon script or Microsoft Systems Management Server. Once the file is delivered to the client computer, users can double-cli ck the MSP file to apply the patch to the local computer. The patch can also be run using the following command line: [start] msiexec /p [path\name of update MSP file] Miscellaneous: -------------Note 1: You can now use Add or Remove Programs in Control Panel to remove some u pdates. For more information about how to determine whether you can use Add or R emove Programs to remove this specific update and for more general information a bout how to remove updates, see the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/903771 Note 2: Hotfixes are cumulative. This means that this hotfix contains all prior hotfixes for the affected files. For more information please see the following Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;en-us;320519