Software Deployment

Yes it's possible and covered in the section "Deploying with the initial 2007 Office system client installation" in the following article

http://office.microsoft.com/download/afile.aspx?AssetID=AM102512381033

I've reproduced the relevent section below and highlighted the areas most appropriate to your question in bold

Deploying with the initial 2007 Office system client installation

The process of deploying updates with the initial installation of the 2007
Office system has changed significantly from past releases of Microsoft Office.
Previously, deploying updates with the initial product installation was done
through an updated administrative installation source or by chaining the updates
to a compressed installation through the Setup.ini file. Both of these techniques presented challenges. When using an administrative installation source, the local installation source files were not available to use as a cache, so applying any subsequent updates required administrators to make the original installation source available again. The use of full-file versions of the updates mitigated this issue by replacing, not modifying, files that required updates. However, the source was still needed in some cases. The KB article, Full-file version update may request Office source files at http://support.microsoft.com/kb/840169/en-us, discusses this issue.

The 2003 release of the Microsoft Office System introduced the Local Installation Source feature, which helped administrators deploy updates from a CD image copied to a network location. This is often called a compressed CD image because it is a copy of the CD which includes compressed files (.cab) files. While the Administrative installation source extracted and updated files from the compressed files through the Setup /a command, installation from a compressed CD image allowed the Local Installation Source feature to create a local copy of the source files so the client could be updated. However, it was not possible to update the compressed CD image. This meant administrators had to either separate the update installations and initial installation, or edit the Setup.ini file in a text editor to chain the updates to the initial installation.

The 2007 Office system makes this process much simpler with an \Updates folder
within the folder containing the source files. This sub-folder can be used to
incorporate the installation of updates with the initial installation of the 2007 Office system products. Only Windows Installer patch files contained in this folder will be installed with the initial installation, so it is necessary to extract these patches from the Microsoft Self-Extractor package. Customization patches can also be installed in this way. If the Office Customization Tool creates a customization patch, it should be
renamed so that it is installed first. Setup.exe will only process one patch during installation; all of the other patches contained in the folder will be chained at the end of the installation. It is recommended that the customization
patch be renamed by adding a "1" at the beginning of the file name to ensure that it is processed first. There is a large amount of information about the process of modifying the installation and deploying customizations. For more on this process, see the 2007 Office Resource Kit topics within Deployment for the 2007 Office release at
http://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx.

For the office2007sp1-kb936982-fullfile-en-us.exe update package, the steps to
populate the \Updates folder with the update patches are as follows:

Copy the compressed CD image to a network location.
Use the Office Customization Tool to make any necessary modifications to the
installation, and save that customization patch to the \Updates folder. As noted above, ensure that the file name begins with a "1"

Make any modifications to the config.xml file that are needed, and save that file either to the folder containing the Setup.exe file or to another location which will be referenced in the command line launching the installation. An example of the sort of modification that may be included in the config.xml file is information about adding language packs to the installation.

Download the office2007sp1-kb936982-fullfile-en-us.exe file from the Microsoft
Download Center at

http://www.microsoft.com/downloads/details.aspx?FamilyId=9EC51594-992C-4165-A997-25DA01F388F5&displaylang=en.

Use the /Extract:[extract folder] switch to extract the patches from this Microsoft Self-Extractor file. An example of the command line to be used is shown below.

office2007sp1-kb936982-fullfile-en-us.exe /extract:"c:\ExtractFiles"

This command line will launch Setup to extract the files. Prior to beginning the extraction process, the EULA will be displayed. Once the EULA is accepted, the files will be extracted. The quotation marks do not need to be used with the path, but it does make it easier to read the command line. Using quotation marks will also avoid problems with a long file name path containing spaces.

Copy the Windows Installer patch (.msp) files to the \Updates folder.

Repeat the process for any other 2007 Office system SP1 update packages or other updates that need to be installed. The Windows Installer patch file names are unique, so there should be no risk of a file being accidentally overwritten, which may cause a problem with the installation. If the product is being deployed with additional language packs, the language pack service packs would be added to the \Updates folder.

Deploy the product normally.


Hope this is useful to you,

Regards,

Spartacus

I have yet to tackle Office 2007 (phew! The Great Escape!) but I can't imagine it would be too different to other flavours, in that the best option is to create an admin install point, apply all patches and hotfixes to that, then use OCT create your customised install from the admin install point and deploy from there, too.

As I'm speaking from almost-complete ignorance, I'm happy to be corrected.

Hi Spartacus,

I have seen your post about "Office 2007 customization" ,
My requirement : while Installing Office 2007 the Office 2003 and Compatibility (Converter) pack has to get uninstall.
Can we add any Registry search in that package,

Clearify: We cant get msi to create mst by ORK or OCT ,is that sure.

Thanks in advance
Sus