A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Office » Setup, Installing & Configuration
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

2007 Silent Install?



 
 
Thread Tools Display Modes
  #11  
Old September 9th, 2009, 03:32 PM posted to microsoft.public.office.setup
Eric Ashton
external usenet poster
 
Posts: 42
Default 2007 Silent Install?

Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you didn't configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has since
been removed. (If you place the standard config.xml in the root and simply
run setup it will always use that config.xml and thus install standard.) This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE: multiple
..ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a ticket
with MS.

--
Thank you,
Eric A.
Microsoft Office Setup

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sarah" wrote:

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?

Ads
  #12  
Old September 9th, 2009, 03:35 PM posted to microsoft.public.office.setup
Eric Ashton
external usenet poster
 
Posts: 42
Default 2007 Silent Install?

Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you didn't configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has since
been removed. (If you place the standard config.xml in the root and simply
run setup it will always use that config.xml and thus install standard.) This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE: multiple
..ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a ticket
with MS.

--

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx



--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sarah" wrote:

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?

  #13  
Old September 9th, 2009, 06:49 PM posted to microsoft.public.office.setup
sarah
external usenet poster
 
Posts: 633
Default 2007 Silent Install?

Eric,

Thank you for answering all my questions. This has helped a lot. I've been
researching this for a few days, and to find out I was placing the default
config.xml file in the wrong order on my command line. The example you
showed has worked for me.

I didn't think the other issues I am having were related, just seemed ironic
that it all started happening at the same time. I didn't mean for my
question to sound cynical, just wanted to portray the overwhelming feeling in
my research that has led me to believe I had to edit the config.xml files in
every instance of the product. I just knew there had to be an easier way,
and what I could find was not working.

Thank you for clarifying all of my questions and uncertainties.

As for onenote, I do have a onenote.ww folder in the same source file, but
that has been there for months and both silent installs have seemed to work.
I must have just been lucky lately and somehow made it work in the meantime.

"Eric Ashton" wrote:

Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you didn't configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has since
been removed. (If you place the standard config.xml in the root and simply
run setup it will always use that config.xml and thus install standard.) This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE: multiple
.ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a ticket
with MS.

--
Thank you,
Eric A.
Microsoft Office Setup

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sarah" wrote:

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?

  #14  
Old June 3rd, 2010, 06:19 PM posted to microsoft.public.office.setup
Alicia C.
external usenet poster
 
Posts: 1
Default Required files for pro?

I'm trying to determine which would be the required file folders to run the customization tool for an Office Pro install. I have:

Access.en-us
Admin
Catalog
Excel.en-us
Office64.en-us
Office.en-us
Outlook.en-us
PowerPoint.en-us
Proofing.en-us
ProPlus.WW
Publisher.en-us
Rosebud.en-us
Updates
Word.en-us

When I try to run
setup.exe /admin
I get an error:
"Failed to get available product info."

Am I missing a folder? Any thoughts or suggestions?

Thanks,
Alicia C.



Sarah wrote:

Eric,Thank you for answering all my questions. This has helped a lot.
09-Sep-09

Eric,

Thank you for answering all my questions. This has helped a lot. I have been
researching this for a few days, and to find out I was placing the default
config.xml file in the wrong order on my command line. The example you
showed has worked for me.

I did not think the other issues I am having were related, just seemed ironic
that it all started happening at the same time. I did not mean for my
question to sound cynical, just wanted to portray the overwhelming feeling in
my research that has led me to believe I had to edit the config.xml files in
every instance of the product. I just knew there had to be an easier way,
and what I could find was not working.

Thank you for clarifying all of my questions and uncertainties.

As for onenote, I do have a onenote.ww folder in the same source file, but
that has been there for months and both silent installs have seemed to work.
I must have just been lucky lately and somehow made it work in the meantime.

"Eric Ashton" wrote:

Previous Posts In This Thread:

On Thursday, July 26, 2007 1:34 PM
A wrote:

2007 Silent Install?
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?

On Thursday, July 26, 2007 2:08 PM
Eric wrote:

To avoid getting the setup screen that offers all the office products...
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:

On Thursday, July 26, 2007 2:26 PM
A wrote:

Bingo. Thank you.
Bingo. Thank you.

On Friday, July 27, 2007 10:20 AM
A wrote:

Can you tell me which specific product folders I need for Standard, so I don't
Can you tell me which specific product folders I need for Standard, so I
don't have to copy the whole DVD to the share point? I tried just placing
Updates and Standard.ww, added the individual product .ww and -en-us folders
as well as Admin and Catalog, but the install won't start. Why would I need
the Visio and Project folders for Standard setup to run, using such a
specific install command as you gave me?

thx

On Friday, July 27, 2007 10:26 AM
Eric wrote:

You should need these folders for standardCatalogExcel.en-usOffice.
You should need these folders for standard

Catalog
Excel.en-us
Office.en-us
Office64.en-us
Outlook.en-us
Powerpoint.en-us
Proofing.en-us
Rosebud.en-us
Standard.ww
Updates
Word.en-us

--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:26 AM
Eric wrote:

Oh.. and the admin folder if you are using a .
Oh.. and the admin folder if you are using a .MSP
--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:32 AM
Eric wrote:

Also...
Also...

It should be noted that if you copy those folders into it's own folder you
will no longer need to use the /config switch as standard will be the only
product to install so it will not ask which product to install.


--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:50 AM
A wrote:

Thanks for the accurate answer, Eric.
Thanks for the accurate answer, Eric. For my understanding, can you tell me
the difference between the .ww folders and the en-us folders? Why do I use
the Standard.WW folder, but the product en-us not .ww?

On Friday, July 27, 2007 10:56 AM
Eric wrote:

The short answer is that Office 2007 is "language neutral".
The short answer is that Office 2007 is "language neutral". So the main
office components can be integrated to run with any language..

If you were going to apply a french langauge pack for example you would move
the excel.fr-fr and word.fr-fr etc folders into the root and again run setup
pointing to the language neutral standard and it would then install the base
(standard) in French.

--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, January 02, 2009 3:59 PM
Dave H. wrote:

Office 2k7 Enterprise
Whould this list of folders be the same with the exeption of replacing the Standard.ww with the enterprise.ww folder for deploying 2k7 Enterprise?

Dave H.

On Wednesday, September 09, 2009 9:58 AM
Sarah wrote:

Eric,I am having the same issue.
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:

On Wednesday, September 09, 2009 10:32 AM
Eric Ashton wrote:

Hello Sarah, If you are being prompted to choose a product to install when you
Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you did not configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has since
been removed. (If you place the standard config.xml in the root and simply
run setup it will always use that config.xml and thus install standard.) This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE: multiple
..ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a ticket
with MS.

--
Thank you,
Eric A.
Microsoft Office Setup

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sarah" wrote:

On Wednesday, September 09, 2009 10:35 AM
Eric Ashton wrote:

Hello Sarah, If you are being prompted to choose a product to install when you
Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you did not configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has since
been removed. (If you place the standard config.xml in the root and simply
run setup it will always use that config.xml and thus install standard.) This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE: multiple
..ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a ticket
with MS.

--

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx



--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Sarah" wrote:

On Wednesday, September 09, 2009 1:49 PM
Sarah wrote:

Eric,Thank you for answering all my questions. This has helped a lot.
Eric,

Thank you for answering all my questions. This has helped a lot. I have been
researching this for a few days, and to find out I was placing the default
config.xml file in the wrong order on my command line. The example you
showed has worked for me.

I did not think the other issues I am having were related, just seemed ironic
that it all started happening at the same time. I did not mean for my
question to sound cynical, just wanted to portray the overwhelming feeling in
my research that has led me to believe I had to edit the config.xml files in
every instance of the product. I just knew there had to be an easier way,
and what I could find was not working.

Thank you for clarifying all of my questions and uncertainties.

As for onenote, I do have a onenote.ww folder in the same source file, but
that has been there for months and both silent installs have seemed to work.
I must have just been lucky lately and somehow made it work in the meantime.

"Eric Ashton" wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Entity Framework 4.0 POCO-First development and POCO Template
http://www.eggheadcafe.com/tutorials...k-40-poco.aspx
  #15  
Old June 6th, 2010, 08:19 PM posted to microsoft.public.office.setup
Manmohan Rajyana
external usenet poster
 
Posts: 1
Default Required files for pro?

Sirs I am in India, an old retired, new learner, excepting fresh updates
about Microsoft office suite 2007 Home & Students edition. Thanks
"Alicia C." wrote in message ...
I'm trying to determine which would be the required file folders to run
the customization tool for an Office Pro install. I have:

Access.en-us
Admin
Catalog
Excel.en-us
Office64.en-us
Office.en-us
Outlook.en-us
PowerPoint.en-us
Proofing.en-us
ProPlus.WW
Publisher.en-us
Rosebud.en-us
Updates
Word.en-us

When I try to run
setup.exe /admin
I get an error:
"Failed to get available product info."

Am I missing a folder? Any thoughts or suggestions?

Thanks,
Alicia C.



Sarah wrote:

Eric,Thank you for answering all my questions. This has helped a lot.
09-Sep-09

Eric,

Thank you for answering all my questions. This has helped a lot. I have
been
researching this for a few days, and to find out I was placing the default
config.xml file in the wrong order on my command line. The example you
showed has worked for me.

I did not think the other issues I am having were related, just seemed
ironic
that it all started happening at the same time. I did not mean for my
question to sound cynical, just wanted to portray the overwhelming feeling
in
my research that has led me to believe I had to edit the config.xml files
in
every instance of the product. I just knew there had to be an easier way,
and what I could find was not working.

Thank you for clarifying all of my questions and uncertainties.

As for onenote, I do have a onenote.ww folder in the same source file, but
that has been there for months and both silent installs have seemed to
work.
I must have just been lucky lately and somehow made it work in the
meantime.

"Eric Ashton" wrote:

Previous Posts In This Thread:

On Thursday, July 26, 2007 1:34 PM
A wrote:

2007 Silent Install?
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?

On Thursday, July 26, 2007 2:08 PM
Eric wrote:

To avoid getting the setup screen that offers all the office products...
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:

On Thursday, July 26, 2007 2:26 PM
A wrote:

Bingo. Thank you.
Bingo. Thank you.

On Friday, July 27, 2007 10:20 AM
A wrote:

Can you tell me which specific product folders I need for Standard, so I
don't
Can you tell me which specific product folders I need for Standard, so I
don't have to copy the whole DVD to the share point? I tried just placing
Updates and Standard.ww, added the individual product .ww and -en-us
folders
as well as Admin and Catalog, but the install won't start. Why would I
need
the Visio and Project folders for Standard setup to run, using such a
specific install command as you gave me?

thx

On Friday, July 27, 2007 10:26 AM
Eric wrote:

You should need these folders for standardCatalogExcel.en-usOffice.
You should need these folders for standard

Catalog
Excel.en-us
Office.en-us
Office64.en-us
Outlook.en-us
Powerpoint.en-us
Proofing.en-us
Rosebud.en-us
Standard.ww
Updates
Word.en-us

--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:26 AM
Eric wrote:

Oh.. and the admin folder if you are using a .
Oh.. and the admin folder if you are using a .MSP
--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:32 AM
Eric wrote:

Also...
Also...

It should be noted that if you copy those folders into it's own folder you
will no longer need to use the /config switch as standard will be the only
product to install so it will not ask which product to install.


--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, July 27, 2007 10:50 AM
A wrote:

Thanks for the accurate answer, Eric.
Thanks for the accurate answer, Eric. For my understanding, can you tell
me
the difference between the .ww folders and the en-us folders? Why do I
use
the Standard.WW folder, but the product en-us not .ww?

On Friday, July 27, 2007 10:56 AM
Eric wrote:

The short answer is that Office 2007 is "language neutral".
The short answer is that Office 2007 is "language neutral". So the main
office components can be integrated to run with any language..

If you were going to apply a french langauge pack for example you would
move
the excel.fr-fr and word.fr-fr etc folders into the root and again run
setup
pointing to the language neutral standard and it would then install the
base
(standard) in French.

--
Eric Palm
MSFT Office Setup


"AG" wrote:

On Friday, January 02, 2009 3:59 PM
Dave H. wrote:

Office 2k7 Enterprise
Whould this list of folders be the same with the exeption of replacing the
Standard.ww with the enterprise.ww folder for deploying 2k7 Enterprise?

Dave H.

On Wednesday, September 09, 2009 9:58 AM
Sarah wrote:

Eric,I am having the same issue.
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:

On Wednesday, September 09, 2009 10:32 AM
Eric Ashton wrote:

Hello Sarah, If you are being prompted to choose a product to install when
you
Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice
a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the
config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you did not configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product
you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has
since
been removed. (If you place the standard config.xml in the root and
simply
run setup it will always use that config.xml and thus install standard.)
This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming
that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE:
multiple
.ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your
installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a
single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a
ticket
with MS.

--
Thank you,
Eric A.
Microsoft Office Setup

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx
--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Sarah" wrote:

On Wednesday, September 09, 2009 10:35 AM
Eric Ashton wrote:

Hello Sarah, If you are being prompted to choose a product to install when
you
Hello Sarah,

If you are being prompted to choose a product to install when you are
running setup, then you have more than one "product" in your Office 2007
source. In other words you have more than one .ww folder. You will notice
a
Onenote.ww folder and a Standard.ww (or enterprise or whatever). When you
have more than one product in the source you will need to call the
config.xml
of the product you want to install.

So you could use:

setup.exe /adminfile XXXX.msp /config standard.ww\config.xml

Even if you did not configure the config.xml for standard this is all you
would need for the install to skip the screen that asks you which product
you
want to install.

Why did this change? There are a few possibilities. Either:

A. Someone added the OneNote standalone source to the Office 2007 source,
and that is why setup is now prompting for which product to install.

B. There was a config.xml in the root of the source before and it has
since
been removed. (If you place the standard config.xml in the root and
simply
run setup it will always use that config.xml and thus install standard.)
This
is not recommended for a few reasons.)

you mention in your post that since you started having issues you noticed
that you are now also having additinal issues: "outlook uninstall msp
started to fail, as well as my live meeting and OCS 2007 installs "

You live meeting and OCS 2007 installs should have nothing to do with your
Office 2007 install and as such are probably not related. I am assuming
that
your Outlook uninstall MSP is a "maintenance" MSP that removes the Outlook
feature. This would also have nothing to do with your Office install.


To Answer your questions:

1.
Question: Is there an easier way to fix this without having to edit every
xml file for
office pro 2007?

Answer: Don't have a source that contains multiple Office 2007
installations. IE: onenote standalone & Office 2007 suite. Also.... your
question sounds cynical. You cannot in fact edit "every XML file". You can
ONLY edit the config.xml files in the 2 WW folders. If you attempt to edit
any other XML files in the source (like setup.xml) your installation will
fail. Secondly, as mentioned above you do not NEED to edit the config.xml
files (although you should edit the single display level line for silent
install) you simply need to point to them during your install line as
mentioned above if your source contains multiple 2007 products. (IE:
multiple
.ww folders)

2.
Question: i am unsure what the point of making the msp file if i have to
edit the xml files.

Answer: The OCT allows for thousands of customizations to your
installation.
There are numerous reasons to make a custom msp whether you customize the
config.xml or not. Reminder: If you have multiple 2007 products in a
single
source you need to "call" the config.xml of the product you are wanting to
install, but technically you do not need to edit it.

If you have any additional questions about this process please open a
ticket
with MS.

--

Config.xml file in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179195.aspx

Office Customization Tool in the 2007 Office system
http://technet.microsoft.com/en-us/l.../cc179097.aspx



--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Sarah" wrote:

On Wednesday, September 09, 2009 1:49 PM
Sarah wrote:

Eric,Thank you for answering all my questions. This has helped a lot.
Eric,

Thank you for answering all my questions. This has helped a lot. I have
been
researching this for a few days, and to find out I was placing the default
config.xml file in the wrong order on my command line. The example you
showed has worked for me.

I did not think the other issues I am having were related, just seemed
ironic
that it all started happening at the same time. I did not mean for my
question to sound cynical, just wanted to portray the overwhelming feeling
in
my research that has led me to believe I had to edit the config.xml files
in
every instance of the product. I just knew there had to be an easier way,
and what I could find was not working.

Thank you for clarifying all of my questions and uncertainties.

As for onenote, I do have a onenote.ww folder in the same source file, but
that has been there for months and both silent installs have seemed to
work.
I must have just been lucky lately and somehow made it work in the
meantime.

"Eric Ashton" wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Entity Framework 4.0 POCO-First development and POCO Template
http://www.eggheadcafe.com/tutorials...k-40-poco.aspx


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 08:40 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright 2004-2017 OfficeFrustration.
The comments are property of their posters.