How to change the source for a client computer from an updated administrative installation point to an Office XP original release version baseline source (922665)


The information in this article applies to:

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

INTRODUCTION

This article describes how to change the source for a client computer from an updated administrative installation point to a Microsoft Office XP original release version baseline source.

SUMMARY

A popular method to deploy and maintain Microsoft Office in an organization is by using an administrative installation point. Usually, the most efficient method to update client computers is to update the administrative installation point and to perform a recaching reinstallation of Office on client computers.

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

For Office XP, you may want to use Microsoft Update or the Microsoft Windows Server Update Services. In this case, the administrative installation point must be an original release version baseline source that has no updates or hotfixes applied. You cannot use Microsoft Office XP Service Pack 1, Microsoft Office XP Service Pack 2, or Microsoft Office XP Service Pack 3.

Binary client software updates existed previously for Office XP. Therefore, the only supported recommendation for Office XP installations is an administrative installation point that is an original release version baseline source.

If you have to add, to modify, or to remove a transform, you must uninstall the current installation. Do this before you deploy a fresh installation that uses the new transform from an original release version baseline source.

Additionally, you must remove the current installation and then deploy a fresh installation from an original release version baseline source when all the following conditions are true:
  • The installation is managed through the Active Directory directory service software deployment.
  • The client computer has version 3.0 or a later version of Microsoft Windows Installer installed.
  • The client computer has one or more binary client-side, non-full-file Office updates currently installed.
  • The current administrative installation point has a service pack installed.
If these conditions are not true, you can change the client to use an original release version baseline source without uninstalling and then installing a fresh installation.

MORE INFORMATION

To change to an original release version baseline source for Office XP, follow these steps:
  1. Create an original release version baseline source.

    An original release version 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 to the source location that you want. Because the compressed source does not contain the product ID key (PIDKEY) or the product ID information in the Windows Installer file, you must include the PIDKEY in the SETUP.ini file or with a transform.
    • 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.
    You may want to update all client computers to the original release version baseline source at the same time. In this case, you can replace the existing source with the original release version baseline source in the same location. Otherwise, we recommend that you create a new location for the original release version baseline source. Then, leave the existing source intact so that you can update the client computers in stages.
  2. Perform a recaching reinstallation.

    You may be able to recache the client computer by using the original release version baseline source before you apply a client-side service pack separately. However, 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 resembles the following command line:

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

    Note In this command line, replace the placeholders as follows:
    • OBSPath is the path of the original release version baseline source.
    • File_Name.msi is the file name of the Windows Installer file.
    • SPPath is the path of the Office service pack.
    • File_Name.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 the administrative installation point is changed to an original release version baseline source. When the service pack does not match the version of the administrative installation point, the installation of a different service pack version may fail. This failure occurs if any updates are already installed on the client.
  3. Run a second recache.

    The REINSTALLMODE property is reset internally when the client-side service pack is included. Therefore, you must run a second recache to correctly register the .msi file from the original release version baseline source. Without the second recache, subsequent updates may not be installed successfully.

    To run the second recaching reinstallation, use a command line that resembles the following command line:

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

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

    Make sure that the correct versions of replacement files are used if any repair is needed. To do this, 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.
For more information about how to update an Office XP installation, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/assistance/HA011525751033.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/7/2006
Keywords:kbnetwork kbDeployment kbExpertiseInter kbhowto KB922665 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.