You can deploy Microsoft Office 2007 with RemoteExec. To do this you need the Enterprise version of the Office 2007 CD.
Procedure to follow:
Check that the Service pack 2 (or more) and Windows Installer 3.1 (or more) are installed on all Windows XP computers and that the Service pack 1 (or more) is installed on all Windows 2003 servers. (See Office 2007 requirements for more information).
Copy
the whole content of the Office 2007
Enterprise CD on a share located on a server in order to create
an installation point.
(Example: \\ServerName\Share\Office2007)
Execute from the root of the installation point
the following command line to start the Office
Customization Tool: setup /Admin
Example: \\ServerName\Share\Office2007\Setup.exe /Admin
Select Microsoft Office Enterprise 2007 and click OK.
In Licensing and user interface enter your volume license key(1), check I accept the terms in the license Agreement, select none as Display Level(1), unselect Completion notice, select Suppress modal and select No Cancel.
In Modify Setup properties add the property SETUP_REBOOT and set Never as value. The reboot will be managed by RemoteExec.
Customize the Office installation as you need.
Save the installation customization in the Update folder (.msp file) of the Office 2007 installation point.
Open RemoteExec and in the Configuration tree go to Remote Jobs/New Remote Job/File execution.
Select the file
setup.exe located at the root of the Office
2007 installation point
as file to execute (See the File
execution Actions type).
Example: \\ServerName\Share\Office2007\Setup.exe
Select the System context.
If a reboot is needed and you want to do it immediately after the installation check the Reboot option box. Alternatively you can reboot your Target computers later. You can also schedule this reboot overnight.
Go to the Target Computers section and select the computers on which you want to deploy the Office 2007.
Click Launch
to start the deployment of the deployment of Office
2007 on all these computers.
You can follow the progression of the deployment in the Progress Window.
(1) If you don't provide a valid volume license key the setup will fail. As workaround during your tests you can specify Basic as Display Level. Doing so the installation will succeed even without a license key.