Office Updates and WSUS support

MS Office Administrative Install Points and Microsoft Update and WSUS update support

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 Word 2003
- Microsoft Office XP Professional
- Microsoft Office XP Standard
- Microsoft Office XP Small Business
- 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 Word 2002

SYMPTOMS

No Microsoft Office updates are displayed when using Microsoft Update or Microsoft Windows Software Update Services (WSUS) and the client computer is configured to use a Microsoft Office administrative installation point as a installation source. However, the same client computer may show available Office updates if the Office Update Web site is used. (Note: the Office Update Web site informs you that one of more of the updates cannot be installed because Office was first installed from an updated administrative installation point.)

CAUSE

This behavior occurs if a client machine uses an updated Office administrative installation point as the installation source. Updates can only be properly detected by Microsoft Update or by WSUS if they have been applied directly to a client machine and not to an administrative installation point.

Microsoft Update or WSUS can be used to update a client computer only if the installation source has not been updated.

WORKAROUND

To work around this issue, use of the following methods:

Method One

Revert the updated administrative installation point to an unaltered installation source.

Method Two

Continue to update Office clients by patching the administrative installation point.

REFERENCES

For more information about how to update Office XP installations by using a patched administrative installation point, visit the following Microsoft Web site:

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

For more information about how to update Office 2003 installations by using a patched administrative installation point, visit the following Microsoft Web site:

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

For more information about how to revert an updated administrative installation point, , click the following article number to view the article in the Microsoft Knowledge Base:
902349 How to revert an updated administrative installation point to an unaltered installation source.

How To: Switch Microsoft Office to use an original baseline source

SUMMARY

This document describes the process for switching the source for a client machine to a Microsoft Office original baseline source (OBS) from an updated administrative installation point (AIP).

A popular method of deploying and maintaining Microsoft Office is through the use of an AIP.  In this scenario, patching the AIP and executing a recaching reinstall Office on the clients is usually the most efficient patching strategy. The recaching reinstall replaces the previously cached MSI file on users' computers and overwrites any old files with the newer versions. New clients that install from the patched administrative image automatically get the updated version — you do not need to chain patches to the core installation.

However, if an administrator wishes to use Microsoft Update (MU) or the Windows Software Update Services (WSUS), the AIP must be an OBS without any updates or hotfixes applied. In most scenarios, it is not necessary to completely uninstall Microsoft Office to switch the client to a fresh installation from an original baseline source.

NOTE: You must uninstall the current installation and deploy a fresh install from an OBS if:

1. The installation is managed through Active Directory (AD) Software Deployment and any of the following requirements are true:

o       The client machines have a version of Windows Installer greater than or equal to 3.0

o       The client machines have one or more client side Office updates currently installed

o       The current AIP has a Service Pack installed

1. You need to add, modify or remove a transform.

MORE INFO

Switching to an OBS only requires a few steps.

Step One: Create an OBS

An OBS is either a copy of the original compressed media or an AIP built from the original compressed media with no other updates applied.

• A compressed source is easiest to build (simply copy the original CD to the desired source location), but will not contain your PIDKEY and/or Product Id information in the .msi.
• You must create an AIP in order to have the PIDKEY and/or Product Id information self-contained in the .msi

                                              

NOTE:  If you will be updating all client machines to the OBS at the same time, you can replace the existing source with the OBS in the same location; otherwise, the recommended method is to create a new location for the OBS (leaving the existing source intact) to allow switching the clients in stages.

Step Two: Execute a recaching reinstall

Although it may be feasible to recache the client with the OBS and deploy a client side Service Pack (SP) separately, it is more efficient, and frequently necessary, to apply the client side Service Pack during the recaching reinstall. To do so one would execute a command line like the following:

MSIEXEC.EXE /I <Path to OBS>\<filename>.msi REINSTALLMODE=VOMU PATCH=<Path to SP>\<filename>.msp

If the Office installation is managed through an AD Software Deployment you should not use the command line method to execute a recaching reinstall. Instead redeploy the package and then use WSUS to distribute the Service Pack.

Step Three: Update the client machine with additional Office updates

The distribution of all updates that were previously part of the updated AIP should be expedited to ensure that the proper versions of replacement files are used if any repair is needed. You can now use WSUS to distribute these and any additional Office updates,

Optional: If you are using Office 2003 it is recommended that you also implement a Local Installation Source (LIS). This can be accomplished with the LISTool.

REFERENCES

For more information about how to update Office XP installations, visit the following Microsoft Web site:

Strategies for Updating Office XP Installations
For more information about how to update Office 2003 installations, visit the following Microsoft Web site:
Strategies for Updating Office 2003 Installations

For more information about the LISTool, visit the following Microsoft Web site:

Change the Local Installation Source After the Installation

For more information about on the use of an Office AIP with MU or WSUS, click the following article number to view the article in the Microsoft Knowledge Base:

903773 Applicable Office updates not detected when using Microsoft Update or Windows Software Update Services (WSUS),

 
APPLIES TO

•	Microsoft Office Professional Edition 2003
•	Microsoft Office Standard Edition 2003
•	Microsoft Office Student and Teacher 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 Word 2003
•	Microsoft Office XP Professional Edition
•	Microsoft Office XP Standard Edition
•	Microsoft Office XP Small Business Edition
•	Microsoft Office XP Standard Edition for Students and Teachers
•	Microsoft Office XP Developer Edition
•	Microsoft Access 2002 Standard Edition
•	Microsoft Excel 2002 Standard Edition
•	Microsoft FrontPage 2002 Standard Edition
•	Microsoft Outlook 2002 Standard Edition
•	Microsoft PowerPoint 2002 Standard Edition
•	Microsoft Word 2002 Standard Edition

 This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm