Eric,

I am having the same issue. My question is though, I have never needed to
edit the XML files and my command line through SCCM: setup.exe /adminfile
XXXX.msp has been working fine until last week. I am unsure what is going
on, but when I manually try this command line without SCCM, I receive the
prompt to choose onenote or office 2007, which has never happened before.
When I choose either, it fails the install and then in the Application logs,
it appears that it is trying to install the word.en-us setup.xml.

also the weird thing is, once this started to fail, my outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs (which are
pushed through GPO) have also started to fail for server authentication.

is there an easier way to fix this without having to edit every xml file for
office pro 2007? i am unsure what the point of making the msp file if i have
to edit the xml files.

Sarah

"Eric A." wrote:

To avoid getting the setup screen that offers all the office products...

Call the config.xml that is in the standard.ww folder during setup..

Example = \\server\share\Office12\setup.exe /config
\\server\share\Office12\Standard.WW\Config.xml /adminfile
\\server\share\Office12\OCTFILE.msp

--
Eric Palm
MSFT Office Setup


"AG" wrote:

I've built an .msp with the OCT, but still keep getting the selection screen
with all the Office products contained on the DVD (I have the volume
edition). When I run setup, this screen appears where I can select Access
2007, Office Standard 2007, etc. When I select Standard, the package is
applied, but how can I create a silent install so the Standard package I
built is installed without having user interaction?