How to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 2 (SP2) (902349)


The information in this article applies to:

  • Microsoft Office Professional Edition 2003
  • Microsoft Office Standard Edition 2003
  • Microsoft Office Students and Teachers Edition 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Basic Edition 2003
  • Microsoft Office Access 2003
  • Microsoft Office Excel 2003
  • Microsoft Office FrontPage 2003
  • Microsoft Office OneNote 2003
  • Microsoft Office Outlook 2003
  • Microsoft Office PowerPoint 2003
  • Microsoft Office Publisher 2003
  • Microsoft Office Word 2003
For a Microsoft Office XP version of this article, see 922665.

INTRODUCTION

This article describes how to change the source for a client computer from an updated administrative installation point to a Microsoft Office 2003 or Microsoft Office 2003 Service Pack 2 (SP2) administrative installation point.

SUMMARY

A popular method to deploy and maintain Microsoft Office in an organization is by using an administrative installation point. In this scenario, updating the administrative installation point and performing a recaching reinstallation of Office on client computers is usually the most efficient method of updating client computers.

The recaching reinstallation method replaces the cached .msi file on the client computer and updates all Office files as required. New client computers that are installed by using the updated administrative image automatically receive the newer version of the .msi file. That is, you do not have to chain updates to the core installation of Office.

If an administrator wants to use Microsoft Update (MU), Windows Server Update Services (WSUS), Microsoft Baseline Security Analyzer (MBSA) 2.0, or Systems Management Server (SMS) 2003 Inventory Tool for Microsoft Updates (ITMU), the administrative installation point must be an original baseline source without any updates or hotfixes applied. Or, you must update the administrative installation point to Office 2003 Service Pack 2 (SP2) and recache the client computers.

Starting with Office 2003 SP2, all minor updates that have been released are full-file administrative software updates. Therefore, MU and WSUS can correctly detect and deploy software updates to administrative installation points that have been updated to Office SP2.

Because binary client software updates were created for versions of Office 2003 that are earlier than Office 2003 SP2, the only supported recommendation for pre-Office 2003 SP2 administrative installation points is an installation source that is at an original baseline source or that has been updated to Office 2003 SP2

If you have to add, to modify, or to remove a transform, you must remove the current installation before you deploy a fresh installation with the new transform from an original baseline source or from an Office 2003 administrative installation point that has been updated to Office 2003 SP2.

Additionally, you must remove the current installation and then deploy a fresh installation from an original baseline source or from an Office 2003 administrative installation point that has been updated to Office SP2 if all the conditions are true:
  • The installation is managed through Active Directory directory service software deployment.
  • The client computer has version 3.0 or later versions of Microsoft Windows Installer installed.
  • The client computer has one or more client-side Office updates currently installed.
  • The current administrative installation point has a service pack that is not Office 2003 SP2 installed.
If these conditions are not true, you should be able to change the client to use an original baseline source or an Office 2003 administrative installation point that has been updated to Office 2003 SP2 without having to uninstall and install a fresh installation as expected.

MORE INFORMATION

Note If you want to update an Office 2003 administrative installation point to Office 2003 SP2, review the "How to update to an administrative installation point with Office 2003 SP2" section.

How to change to an original baseline source

  1. Create an original baseline source. An original baseline source is either a copy of the original compressed media or an administrative installation point. This administration installation point is built from the original compressed media and has no other updates applied.

    Notes
    • A compressed source is the easiest to build. To build a compressed source, copy the original Office CD-ROM to the source location that you want. However, the compressed source will not contain the product ID Key (PIDKEY) or the product ID information in the Windows Installer file.
    • You must create an administrative installation point if you want the PIDKEY or the product ID information to be self-contained in the Windows Installer file.
    If you are updating all client computers to the original baseline source at the same time, you can replace the existing source with the original baseline source in the same location. Otherwise, we recommend that you create a new location for the original baseline source and then leave the existing source intact so that you can update the client computers in stages.
  2. Perform a recaching reinstallation. Although it may be possible to apply the client-side service pack separately from the original baseline source recache, it is more efficient and frequently necessary to apply the client-side service pack during the recaching reinstallation. To apply the client-side service pack during the recaching reinstallation, use a command line that is similar to the following:

    msiexec.exe /i OBSPath\filename.msi REINSTALLMODE=VOMU PATCH=SPPath\filename.msp

    Notes In this command line, replace the placeholders as follows:
    • OBSPath is the path of the original baseline source.
    • filename.msi is the file name of the Windows Installer file.
    • SPPath is the path of the Office service pack.
    • filename.msp is the file name of the Office service pack installation file.
    If the Office installation is managed through an Active Directory software deployment, you should not use the command line method to perform a recaching reinstallation. Instead, redeploy the package, and then use Windows Server Update Services to distribute the service pack.

    Note The service pack that is applied during the recache should match the version of the administrative installation point before it is changed to an original baseline source. If the service pack does not match the version of the administrative installation point, the installation of a different version service pack may fail if any updates have already been installed on the client.
  3. Because the inclusion of the client-side service pack will reset the REINSTALLMODE property internally, you must run a second recache in order to correctly register the .msi file from the original baseline source. Without the second recache, subsequent updates may not install. To run the second recaching reinstallation, use a command line that is similar to the following:

    msiexec.exe /i OBSPath\filename.msi REINSTALLMODE=VM

    Notes In this command line, replace the placeholders as follows:
    • OBSPath is the path of the original baseline source.
    • filename.msi is the file name of the Windows Installer file.
    Note that the only file that is transmitted during the second recache is the .msi file. Therefore, there will be minimal network traffic for this operation.
  4. Update the client computer by installing any additional Office updates.

    To make sure that the correct versions of replacement files are used if any repair is needed, distribute all Office updates that were previously part of the updated administrative installation point as soon as possible. You can now use Windows Server Update Services to distribute these updates and any additional Office updates.

    We recommend that you implement a Local Installation Source (LIS). You can implement an LIS by using the Local Installation Source Tool (LISTool.exe).

    For more information about the Local Installation Source Tool, visit the following Microsoft Web site:

    http://office.microsoft.com/en-us/assistance/HA011402361033.aspx

How to update to an administrative installation point with Office 2003 SP2

  1. Click Start, click Run, and then type the command line for Windows Installer. Use the appropriate options for your installation. Use the following syntax:

    msiexec /p [path\MAINSP2ff.msp]/a [path\name of Office 2003 MSI file] /qb /L*V [path\name of log file]

    Note If an update contains multiple MSP files, you must run the command line separately for each MSP file that you apply to the administrative installation point. You cannot reference multiple MSP files on the same command line. The following table describes the command-line options.
    Command-line optionDescription
    MsiexecExecutable file name for Windows Installer.
    /pEnables Windows Installer to apply an update to an existing installation.
    [path\MAINSP2ff.msp]Path and file name of the MSP file for the update.
    /aEnables Windows Installer to perform an administrative installation of a product on a network share.
    [path\name of MSI file]Path and file name of the Windows Installer package for your original administrative image.
    /qbSets the user interface to the basic level (simple progress and error handling).
    /L*VTurns on logging and sets a path for the log file. The * flag causes the switch to log all information.
    [path\name of log file]Path and file name of the Windows Installer log file.
  2. Perform a recaching reinstallation. Use a command line that is similar to the following:

    msiexec.exe /i OBSPath\filename.msi REINSTALLMODE=VOMU REINSTALL=ALL

    Notes In this command line, replace the placeholders as follows:
    • OBSPath is the path of the original baseline source.
    • Filename.msi is the file name of the Office 2003 Windows Installer file.
    If the Office installation is managed through an Active Directory software deployment, you should not use the command line method to perform a recaching reinstallation. Instead, redeploy the package, and then use Windows Server Update Services, Microsoft Update, or the SMS Inventory Tool for Microsoft Updates to distribute the rest of your updates.
  3. Update the client computer by installing any additional Office updates.

REFERENCES

For more information about how to update an Office 2003 installation, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/assistance/HA011525741033.aspx

For more information about how to use an Office administration installation point with Microsoft Update or with Windows Server Update Services, click the following article number to view the article in the Microsoft Knowledge Base:

903773 No appropriate Microsoft Office updates are displayed when you use Microsoft Update or Windows Server Update Services

Modification Type:MinorLast Reviewed:9/27/2006
Keywords:kbsetup kbhowto KB902349 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.