Silent install of Office 2007 B2TR

[Charles Gregory]

Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas

 

[Bob Buckland ?:-\)]

Hi Chas,

You can combine multiple Office 2007 application skus (products) into a single Office Network Installation Point (oNIP). You can
chain the installs using the config.xml files with a single setup.exe command and for each product you apply the .msp files in the
\Updates folder can be applied as part of that process. (MS Office 2007 product skus contain multiple .MSIs (installation files)
and .MSPs (patch files)are created against the .MSIs.

To use the /Admin switch (available only with a volume license/enterprise key product) with Office 2007 Beta2 Technical Refresh
you'll also need do download the updated contents of the \Admin folder (Admin update) for B2TR from the Office section of
http://microsoft.com/downloads

You may want to take a look at the chaining section in deployment in the MS Office 2007 Resource Kit on
http://microsoft.com/technet/prodtechnol/office/
Part of the scenario for reducing bandwidth for deployments is to precache the \MSOCache (Local Installation Source) from the
Network installation point early and then apply the updates when you do the actual installs. In that scenarios it's using the
MSOCache contents for the actual install and the only thing you're pushing then are the MSPs to it.

========
Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas >>
--
I hope this helped you,

Bob Buckland ?
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net

 

[Bob Buckland ?:-\)]

Hi Chas,

You can combine multiple Office 2007 application skus (products) into a single Office Network Installation Point (oNIP). You can
chain the installs using the config.xml files with a single setup.exe command and for each product you apply the .msp files in the
\Updates folder can be applied as part of that process. (MS Office 2007 product skus contain multiple .MSIs (installation files)
and .MSPs (patch files)are created against the .MSIs.

To use the /Admin switch (available only with a volume license/enterprise key product) with Office 2007 Beta2 Technical Refresh
you'll also need do download the updated contents of the \Admin folder (Admin update) for B2TR from the Office section of
http://microsoft.com/downloads

You may want to take a look at the chaining section in deployment in the MS Office 2007 Resource Kit on
http://microsoft.com/technet/prodtechnol/office/
Part of the scenario for reducing bandwidth for deployments is to precache the \MSOCache (Local Installation Source) from the
Network installation point early and then apply the updates when you do the actual installs. In that scenarios it's using the
MSOCache contents for the actual install and the only thing you're pushing then are the MSPs to it.

========
Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas >>
--
I hope this helped you,

Bob Buckland ?
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net

 

[Bob Buckland ?:-\)]

Hi Chas,

You can combine multiple Office 2007 application skus (products) into a single Office Network Installation Point (oNIP). You can
chain the installs using the config.xml files with a single setup.exe command and for each product you apply the .msp files in the
\Updates folder can be applied as part of that process. (MS Office 2007 product skus contain multiple .MSIs (installation files)
and .MSPs (patch files)are created against the .MSIs.

To use the /Admin switch (available only with a volume license/enterprise key product) with Office 2007 Beta2 Technical Refresh
you'll also need do download the updated contents of the \Admin folder (Admin update) for B2TR from the Office section of
http://microsoft.com/downloads

You may want to take a look at the chaining section in deployment in the MS Office 2007 Resource Kit on
http://microsoft.com/technet/prodtechnol/office/
Part of the scenario for reducing bandwidth for deployments is to precache the \MSOCache (Local Installation Source) from the
Network installation point early and then apply the updates when you do the actual installs. In that scenarios it's using the
MSOCache contents for the actual install and the only thing you're pushing then are the MSPs to it.

========
Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas >>
--
I hope this helped you,

Bob Buckland ?
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net

 

[Bob Buckland ?:-\)]

Hi Chas,

You can combine multiple Office 2007 application skus (products) into a single Office Network Installation Point (oNIP). You can
chain the installs using the config.xml files with a single setup.exe command and for each product you apply the .msp files in the
\Updates folder can be applied as part of that process. (MS Office 2007 product skus contain multiple .MSIs (installation files)
and .MSPs (patch files)are created against the .MSIs.

To use the /Admin switch (available only with a volume license/enterprise key product) with Office 2007 Beta2 Technical Refresh
you'll also need do download the updated contents of the \Admin folder (Admin update) for B2TR from the Office section of
http://microsoft.com/downloads

You may want to take a look at the chaining section in deployment in the MS Office 2007 Resource Kit on
http://microsoft.com/technet/prodtechnol/office/
Part of the scenario for reducing bandwidth for deployments is to precache the \MSOCache (Local Installation Source) from the
Network installation point early and then apply the updates when you do the actual installs. In that scenarios it's using the
MSOCache contents for the actual install and the only thing you're pushing then are the MSPs to it.

========
Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas >>
--
I hope this helped you,

Bob Buckland ?
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net

 

[Bob Buckland ?:-\)]

Hi Chas,

You can combine multiple Office 2007 application skus (products) into a single Office Network Installation Point (oNIP). You can
chain the installs using the config.xml files with a single setup.exe command and for each product you apply the .msp files in the
\Updates folder can be applied as part of that process. (MS Office 2007 product skus contain multiple .MSIs (installation files)
and .MSPs (patch files)are created against the .MSIs.

To use the /Admin switch (available only with a volume license/enterprise key product) with Office 2007 Beta2 Technical Refresh
you'll also need do download the updated contents of the \Admin folder (Admin update) for B2TR from the Office section of
http://microsoft.com/downloads

You may want to take a look at the chaining section in deployment in the MS Office 2007 Resource Kit on
http://microsoft.com/technet/prodtechnol/office/
Part of the scenario for reducing bandwidth for deployments is to precache the \MSOCache (Local Installation Source) from the
Network installation point early and then apply the updates when you do the actual installs. In that scenarios it's using the
MSOCache contents for the actual install and the only thing you're pushing then are the MSPs to it.

========
Hi

I've been trying to add an install of the Office 2007 B2TR apps to a Vista
RC-1 deployment within the Business Desktop Deployment Kit Beta 2.

The first set of Office installations I tried from the public Office 2007
beta 2 download site (in May when it was still free) kept giving me messages
saying that MSP files weren't supported in that version of Office...so I
guess that's the Retail version and it doesn't support silent installs.I do
like the fact that the CIW is built into the main setup...nice one...it'll
save us from always having to downloading CIW from the Office site.

Then I downloaded the DVD from MSDN with all the client apps on the single
DVD. I generated new msp's for each app - annoying that I hd to go through
the whole process for each app as setup.exe /admin asks me which app I want
to use at the start.

Can't we have a single setup /admin with an extended selection for each app
and it's sub-categories on the page where you choose which bits to install?
I'd then end up with one .msp for the whole lot.

Anyway - that setup now runs OK - but even with the GUI turned off, I get a
dialog box which asks we which application I'm installing when I run setup
/adminfile <mymsp>.msp......arrghhh! You know what I'm installing - It's in
the .msp file that I'm giving you!

Any ideas where I'm going wrong?

Chas >>
--
I hope this helped you,

Bob Buckland ?
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net