You create a customized Config.xml file for the chained installation of a 2007 Microsoft Office suite. The Config.xml file includes a set of command-line instructions to copy the setup log files to a central share. If the setup chain fails during the installation, the setup log files are not copied to the central share. Instead, the files remain on the computer on which the Setup program failed. Additionally, other commands that are specified in the Config.xml do not run.

To work around this issue, create a batch file that acts as wrapper. The following sample InstallOffice.bat file will copy the setup log files to the central share and will run the installation of the chain setup of the 2007 Office suite.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

md \\<server>\<share>\logs\%COMPUTERNAME%
echo Now Installing Microsoft Office 2007 >> \\<server>\<share>\logs\%COMPUTERNAME%\installstatus.txt
call \\<server>\<share>\office\setup.exe /config \\<server>\<share>\office\quietsetup.xml
echo Microsoft Office 2007 completed with a return code of %ERRORLEVEL% >> \\<server>\<share>\logs\%COMPUTERNAME%\installstatus.txt
echo Finished Installing Microsoft Office 2007 >> \\<server>\<share>\logs\%COMPUTERNAME%\installstatus.txt
copy %temp%\SetupExe*.log \\<server>\<share>\logs\%COMPUTERNAME%