Hmm.. I found this easy in the deployment console. I've just set it to install a package from a hidden share (using $).

\\servername\packages$\Microsoft\Office2007\setup.exe

That works fine in our environment using 6.9 SP1. That install is Office 2007 with SP1 slipstreamed.

Package$ only has read only privileges. In the office2007 folder is the full office cd.

Only custom settings on the package is that we've set it to "Run directly from source" so they don't have the installer left on the machines for anyone to poach. It doesn't ask for a product key as its a VLK version.

When you have customized .MSP file then no need to use any .xml files.

Copy your customized .MSP file to updates folder( Readme.txt: Any patches placed in this folder will be applied during initial install) run the Setup.EXE

If you installation options are included in the your customized *.msp file, then there is no need to use any command line switch.

Thanks
Sid

Also you can go through the following links realted to Office 2007, that are already there in this forum

https://www-secure.symantec.com/community/article/...

https://www-secure.symantec.com/community/forum/61...

https://www-secure.symantec.com/community/download...

Thanks
Sid

Sid,
I have tried that. The MS office install screen flashes and disappears on the target PC. The the
job status on DS shows " Error 30066 during script execution" and the job fails.
Do I need to choose any other options??
The one thing I forgot to mention in my post is that the NS/DS is accross the WAN running the job. Basically the server (installation point) and the PC are at the branch.

Thanks

Error(exit code)30066 is the result of the target machine not meeting the requirements for the Office installation.

Could you check system reqquirments for Office 2007, and cross check them with your machine to confirm weather it is meeting allrequirements or not.

Thanks
Sid

Followin are the System Requirments for Office 2007. Out of these Hard disk space plays very important role
Hard disk :- 1.5 gigabyte (GB); a portion of this disk space will be freed after installation if the original download package is removed from the hard drive
Computer and processor :- 500 megahertz (MHz) processor or higher.
Memory :-256 megabyte (MB) RAM or higher. 512 MB RAM or higher recommended for Instant Search.
Operating system:- Microsoft Windows(R) XP with Service Pack (SP) 2, Windows Server(R) 2003 with SP1, or later operating system.
Other Connectivity to Microsoft Exchange Server 2000 or later is required for certain advanced functionality in Outlook 2007. Connectivity to Microsoft Windows Server 2003 with SP1 or later running Microsoft Windows SharePoint Services is required for certain advanced collaboration functionality. Microsoft Office SharePoint Server 2007 is required for certain advanced functionality. PowerPoint Slide Library requires Office SharePoint Server 2007. Microsoft Internet Explorer 6.0 or later, 32 bit browser only. Internet functionality requires Internet access (fees may apply). * Instant Search requires Microsoft Windows Desktop Search 3.0.
Additional Actual requirements and product functionality may vary based on your system configuration and operating system.
Display 1024x768 or higher resolution monitor
Drive CD-ROM or DVD drive ()

For complete requirements visit
http://office.microsoft.com/en-us/products/HA10166...
http://www.microsoft.com/office/products

Thanks
Sid

rhussain,
I suspect disk space in your case.
Check the disk space on the machines that are errored out.

Thanks,
Eshwar

You guys are awesome.
The disk space was below 400MB. I made 2.5GB of the disk space available. I also ran the updates on that server and installed SP3. The silent install worked great without a restart. I am pretty sure the disk space was the main issue

Thanks again.

Keep in mind that if you keep adding updates to the updates folder you might want to rename your custom MSP file so that it has the number 1 as the first character in the name. I ran into a problem where it was not picking up the custom MSP and after some digging on MS site I found an article that said that setup.exe reads the files in the update directory in alphabetical order.

If you are installing afresh, you can slipstream the service pack into UPDATES folder so that there is no need to install Service pack after the main install.

please see kb#39571

kb.altiris.com/display/1/articleDirect/index.asp

Food for thought, instead of running the command line from the DS, create a Wise script that runs the command line, save it as an .exe and then deploy it.  When you run it from a Wise script you can pass the return codes from the installation back to the DS for reporting so you would know exactly why it failed and also can track which ones have success.

I would strongly recommend Emily's advice.

We do write vbscript as well as wise wrapper scripts for DS installs. In case of vbscripts, we use
wscript.exe //B script.vbs
commandline which will suppress all script prompts.