IBM Support

Why are my Microsoft Office patch deployments failing?

Technote (troubleshooting)


Problem(Abstract)

The following document describes additional steps necessary to patch Office installations prior to Office 2007.

Resolving the problem

There are three different ways to deploy Office updates and patches in TEM, troubleshooting steps will vary depending on your deployment method:

1. Administrative Installation:

  1. The Office product being patched must be pointing to the correct administrative installation point, the admin point must match the product being patched. An Office 2000 Standard installation cannot be pointing to an Office 2000 Professional admin point. (You can reassign your admin point by using the "Office Administrative Installation Point Reassignment" task in the BES Support site.)
  2. There can only be one Office product present on the computer. Multiple installations of different Office versions is an exception. (Office 2000 Small Business and Office 2000 Professional is not supported, whereas Office 2000 Small Business and Office XP Professional is supported.)
  3. The patch must have been properly applied to the admin point before deploying the action. Click here for information from Microsoft on how to do this.
  4. The administrative installation point must be shared with "read" permissions given to "ANONYMOUS LOGON", "NETWORK", or "EVERYONE" on a Windows NT, Windows 2000, Windows XP, or Windows 2003 system.
  5. Null session must be enabled for the share.

2. Network Installation:

  1. When deploying the action, you must supply a valid UNC path (\\server_name\share_name) to the appropriate Office setup files. The shared setup files must match the product being patched, an Office 2000 Standard installation cannot be patched by providing the Office 2000 Professional setup files.
  2. For Office 2000, there can only be one Office product present on the computer. Multiple installations of different Office versions is an exception. (Office 2000 Small Business and Office 2000 Professional is not supported, whereas Office 2000 Small Business and Office XP Professional is supported)
  3. The Office setup files must be shared with "read" permissions given to "ANONYMOUS LOGON", "NETWORK", or "EVERYONE" on a Windows NT, Windows 2000, Windows XP, or Windows 2003 system.
  4. Null session must be enabled for the share.

3. Local Installation:
There are two methods of supplying a local installation cache to those endpoints that do not already have one available. Note that endpoints with a local installation cache available on disk may deploy Local Installation Fixlet messages without any other preparation:

  1. Local CD Method: The proper Office CD matching the product being patched must be placed in the local CD-ROM drive.
  2. Cache Distribution Method: Use the Microsoft Office Source Configuration Wizard to upload and distribute Office source files to cache locally on client computers. Once files have been cached locally, installation Fixlet messages can now be deployed.

Historical Number

129

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Software edition: Edition Independent

Reference #: 1506000

Modified date: 25 September 2014


Translate this page: