Office updates fail to install on most of the clients.
After further investigation, it is discovered that the update returned one (or more) of the following error codes:
There could be several reasons why these error codes are returned.
The install program for the Office* update program has the Starting Window set to Normal. This causes a command prompt window to appear on the screen and, if a user is not logged on, the update will fail.
The Office update requires access to the source installation files, but cannot find a valid path to where they are stored. Typically, Office installations come from a network share. If these files are moved, or if the path to them changes, the clients become out of date and hold an invalid location in their registry. When the update cannot find these files, it will try to prompt the user for a valid location. Since the update is set to run hidden, the window is suppressed and the update fails.
It is possible for the clients to have a valid network location for source files, but when the updates attempts to retrieve those files, the update again fails. This would be caused by running the Office update with the System Account and storing the files on a share with limited access.
The End User License Agreement pops up whent the Software Update is being executed.
The following Solutions coincide with the causes:
Go to the Software Update Policy > Advanced Tab.
Select the Command Line link for the corresponding update.
Ensure the results, at the bottom of the Window, display /quiet or /q.
Verify there exists a valid UNC path to a server that has the source installation files for Office.
Open the Altiris Agent GUI > Software Delivery Tab
Expand the Options Dropdown and enable the top 3 options
Open the Software Updates Tab
Double click the corresponding update
Open the Download History Tab
Select the links provided to ensure they are valid
If there are no valid links, run the Check Software Update Package Integrity Check as outlined on KM: HOWTO9835
Ensure the credentials for updates are input as needed. Keep in mind that the update will only install if these settings are matched on the client.
Settings on the Console > Settings > All Settings > Software > Patch Management > Microsoft and on the Programs tab.
Example: If the 'Run with Rights' are set to 'Specified User,' and the Admin Account credentials are in place, ensure the 'Program can run:' 'Whether or not the user is logged on;' otherwise, that Admin account will need to be logged in to the client when the Software Update Cycle begins.
The Office install source is not on the network, but rolled out through a CD in the image. This issue lies outside Patch Management. Please view the following links for further assistance with this issue: