Here's a good tip from Frank Rojas, one of our Senior Support Engineers from Charlotte, North Carolina. This one concerns installing Office 2007 as an Install Software task in an OSD Task Sequence so if you either planning on doing this or are trying it now and having trouble, check this out:
Issue: When trying to deploy Office 2007 via an SCCM 2007 OSD Task Sequence, the installation of Office 2007 fails or times out. The SMSTS.log may not indicate what the exact problem is. The Office 2007 setup logs in the %WINDIR%\Temp folder also do not indicate any errors or what is causing the problem, but the Office setup logs do tend to be short and do not contain much data, making it appear that the installation did not progress very far.
Cause: This issue is caused by the Office 2007 installation not being set up to properly run silently during the Install Software task. As with any software being deployed via SMS/SCCM, the installation needs to be set up to run silently if being run within a Task Sequence or if no user interaction is needed or desired. Normally, this is done by adding switches that add silent install options to the install executable (normally /S or /qn). However, in the case of Office 2007, this is controlled by the MSP file created by the Office Customization Tool (OCT).
Resolution: Create a MSP file that will run the Office 2007 setup silently. To do this follow the steps below:
Other changes can be made to the Office 2007 installation using the Office Customization Tool and saved as part of the MSP file., however the above settings are required in order for the Office 2007 installation to run silently.
To edit an existing MSP file that will run the Office 2007 setup silently follow these steps:
Other changes can be made to the Office 2007 installation using the Office Customization Tool and saved as part of the MSP file, however just like above, these settings are required in order for the Office 2007 installation to run silently.
J.C. Hornbeck | Manageability Knowledge Engineer