alconlabs
asked on
Office 2010 customization tool termination
I'm using the Office 2010 customization tool to generate a .MSP file that automates installation. It works with two exceptions:
a) It doesn't execute the service pack .EXE in the Updates folder;
b) I'm running setup.exe in a script. How do I know when it's finished? (Setup appears to return immediately.)
a) It doesn't execute the service pack .EXE in the Updates folder;
b) I'm running setup.exe in a script. How do I know when it's finished? (Setup appears to return immediately.)
ASKER
I don't see any samples described in the referenced link; only an indication that service packs and other updates should be included in the Updates folder:
"If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete."
"If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete."
I went back and looked and you are right about the samples.........sorry about that. However, the link I provided may still have the answer you are seeking. If you scroll to the download section for the admin template and OCT, it says:
__________________________
" NOTE: If you are using the Office Customization Tool to create MSP files for custom installations of Office 2010, <<<we recommend that you use the most recent version of the OCT files.>>>
Updating OCT files is simple – just replace the /Admin folder in your Office 2010 installation files or installation image with the new /Admin folder after extracting it from the download package."
__________________________
I interpret the above to mean you need to use the most recent version of the OCT in order for the update folder to work as intended. Compare the OCT version you used with the one contained in the link....and if the link contains a more recent version of OCT, I would try using the later version.
__________________________
" NOTE: If you are using the Office Customization Tool to create MSP files for custom installations of Office 2010, <<<we recommend that you use the most recent version of the OCT files.>>>
Updating OCT files is simple – just replace the /Admin folder in your Office 2010 installation files or installation image with the new /Admin folder after extracting it from the download package."
__________________________
I interpret the above to mean you need to use the most recent version of the OCT in order for the update folder to work as intended. Compare the OCT version you used with the one contained in the link....and if the link contains a more recent version of OCT, I would try using the later version.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found the appropriate article in MSDN.
Service Pack updates are handled by a separate command line (samples provided in the link above) within the msi due the interaction with the msi restart manager.