Office 2007/B2 Group Policy Installation

Has anyone successfully installed Office 2007 via a GPO in Windows 2003
Server? What MSI(s) do you select to publish to a user? I've found some
documentation that indicates it is ProWW.msi. But when I select that MSI in
group policy editor I get the error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

Thanks.

Michael

Hi Michael,

Office 2007 uses multiple .MSI files for each deployment. The 2007 Office system is more modular. The language packs, for
instance, even English are separate from the language neutral base product files.

You may want to review the information in the Office 2007 Beta 2 Resource Kit. Microsoft is interested in feedback on the clarity
and completeness of the procedures there for using the new methods for deploying Microsoft Office 2007

You'll need to have Office 2007 for it's activex control installed to be able to access the site at
http://officebeta.iponet.net/en-us/t...243261033.aspx

The Office 2007 Resource Kit isn't complete yet. In addition to continuing to discuss success/failure/confusion/ah-ha! here you can
also send feedback on the Resource Kit individual web page content directly to Microsoft using the 'Send us feedback' choice on the
top right of each page and using the MS Office 2007 feedback tool from the link below for both the content and the process and the
tools.

===============
"Michael" wrote in message ...
Has anyone successfully installed Office 2007 via a GPO in Windows 2003
Server? What MSI(s) do you select to publish to a user? I've found some
documentation that indicates it is ProWW.msi. But when I select that MSI in
group policy editor I get the error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

Thanks.

Michael
--
I hope this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends

Read about it, try it, or watch the movie
the 2007 Microsoft Office system iinfo is at
http://microsoft.com/office/preview

Already have 2007 Office System Beta 2?
Send Microsoft your feedback (with pictures)
http://sas.office.microsoft.com/

I've read that information in the resource kit but it is very sparse and does
not work (at least for me).

Michael

Hi Michael,

Some days are like that g. Can you provide a bit more detail on 'doesn't work' when you are using the techniques in the Resource
Kit for Office 2007 (i.e. what page on the site are you using for the steps and what specific options are not working.

=========
"Michael" wrote in message ...
I've read that information in the resource kit but it is very sparse and does
not work (at least for me).

Michael
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael

Hi Michael/Bob

I too have had this issue. Having gone through everything in the resoure
kit which I downloaded from Microsoft I get this error when attepting to add
the proww.msi as a new package in a policy assigned to a workstation.

Having copied the contents of the appropraite folder from my Technet Plus
DVD of office 2007 Beta 2 to a installation point on my server I have run the
Office customization tool which has then saved the msp file to the update
folder. Then according to documentation I should then be able to assign the
proww.msi as a new package in a group policy. After selecting the MSI in the
file requester dialog you then get to choose whether you just want to assign
the package or click advanced. Choosing either of these options presents the
message same message documented about being unable to extract the deployment
information.

I have using GPMMC on my xp workstation as well as on a 2003 server. Same
thing.

I have not touched the config.xml as from what I read in the deployment
documents this will only overwrite what is in the msp file.

Any thoughts Bob?

"Michael" wrote:

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael

I never resolved this issue. After wasting far too much time on it, I
abandoned it. I decided I would not test it in a domain environment until
they work out this issue or tell us what we're doing wrong.

Michael

"GrahamR" wrote:

Hi Michael/Bob

I too have had this issue. Having gone through everything in the resoure
kit which I downloaded from Microsoft I get this error when attepting to add
the proww.msi as a new package in a policy assigned to a workstation.

Having copied the contents of the appropraite folder from my Technet Plus
DVD of office 2007 Beta 2 to a installation point on my server I have run the
Office customization tool which has then saved the msp file to the update
folder. Then according to documentation I should then be able to assign the
proww.msi as a new package in a group policy. After selecting the MSI in the
file requester dialog you then get to choose whether you just want to assign
the package or click advanced. Choosing either of these options presents the
message same message documented about being unable to extract the deployment
information.

I have using GPMMC on my xp workstation as well as on a 2003 server. Same
thing.

I have not touched the config.xml as from what I read in the deployment
documents this will only overwrite what is in the msp file.

Any thoughts Bob?

"Michael" wrote:

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael

Hi,
At last I have found someone with the same problem as me. I would love to
be able to give you the answer, but as yet I don't have one. I have loads of
experience of deploying Office 2000/XP and 2003, all of which seemed really
easy in comparison to 2007, although Microsoft (and I do love them) suggest
this is the easiest yet! The idea of adding an .MSP file to the updates
folder is brilliant, but as soon as you do I get the exact same error message
that you get. If you then attempt to modify the XML file, well, you need a
degree in coding to get your head round that way. If this is a bug, it's a
very stupid one as it's holding up the end using testing of the product, if
you can't deploy it, you can't use it. GREAT.
I have been working on and off this since the release of Beta2 and cannot
find any useful information on this error anywhere. I have ask the Online
Concierge Chat in TechNet and have Googled every combination I can think of.
I'm with you budy, it's NOT you. If I ever find the answer, i'll be back!

PS: Clarification of the error: Only happens after you add the .MSP file to
the update folder. Office 2007 deploys a treat with no modifications in the
update folder, but then your end users / testers must add the PIDKEY and
activate it and install all the other options they need. Not great! SOMEONE
HELP!

"Michael" wrote:

I never resolved this issue. After wasting far too much time on it, I
abandoned it. I decided I would not test it in a domain environment until
they work out this issue or tell us what we're doing wrong.

Michael

"GrahamR" wrote:

Hi Michael/Bob

I too have had this issue. Having gone through everything in the resoure
kit which I downloaded from Microsoft I get this error when attepting to add
the proww.msi as a new package in a policy assigned to a workstation.

Having copied the contents of the appropraite folder from my Technet Plus
DVD of office 2007 Beta 2 to a installation point on my server I have run the
Office customization tool which has then saved the msp file to the update
folder. Then according to documentation I should then be able to assign the
proww.msi as a new package in a group policy. After selecting the MSI in the
file requester dialog you then get to choose whether you just want to assign
the package or click advanced. Choosing either of these options presents the
message same message documented about being unable to extract the deployment
information.

I have using GPMMC on my xp workstation as well as on a 2003 server. Same
thing.

I have not touched the config.xml as from what I read in the deployment
documents this will only overwrite what is in the msp file.

Any thoughts Bob?

"Michael" wrote:

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael

I suspect they may force us to use BDD for deployment. I hope not. I've
worked somewhat with the BDD beta and Vista but not Office 2007 yet. It is a
much more complicated path.

Michael

"Danny" wrote:

Hi,
At last I have found someone with the same problem as me. I would love to
be able to give you the answer, but as yet I don't have one. I have loads of
experience of deploying Office 2000/XP and 2003, all of which seemed really
easy in comparison to 2007, although Microsoft (and I do love them) suggest
this is the easiest yet! The idea of adding an .MSP file to the updates
folder is brilliant, but as soon as you do I get the exact same error message
that you get. If you then attempt to modify the XML file, well, you need a
degree in coding to get your head round that way. If this is a bug, it's a
very stupid one as it's holding up the end using testing of the product, if
you can't deploy it, you can't use it. GREAT.
I have been working on and off this since the release of Beta2 and cannot
find any useful information on this error anywhere. I have ask the Online
Concierge Chat in TechNet and have Googled every combination I can think of.
I'm with you budy, it's NOT you. If I ever find the answer, i'll be back!

PS: Clarification of the error: Only happens after you add the .MSP file to
the update folder. Office 2007 deploys a treat with no modifications in the
update folder, but then your end users / testers must add the PIDKEY and
activate it and install all the other options they need. Not great! SOMEONE
HELP!

"Michael" wrote:

I never resolved this issue. After wasting far too much time on it, I
abandoned it. I decided I would not test it in a domain environment until
they work out this issue or tell us what we're doing wrong.

Michael

"GrahamR" wrote:

Hi Michael/Bob

I too have had this issue. Having gone through everything in the resoure
kit which I downloaded from Microsoft I get this error when attepting to add
the proww.msi as a new package in a policy assigned to a workstation.

Having copied the contents of the appropraite folder from my Technet Plus
DVD of office 2007 Beta 2 to a installation point on my server I have run the
Office customization tool which has then saved the msp file to the update
folder. Then according to documentation I should then be able to assign the
proww.msi as a new package in a group policy. After selecting the MSI in the
file requester dialog you then get to choose whether you just want to assign
the package or click advanced. Choosing either of these options presents the
message same message documented about being unable to extract the deployment
information.

I have using GPMMC on my xp workstation as well as on a 2003 server. Same
thing.

I have not touched the config.xml as from what I read in the deployment
documents this will only overwrite what is in the msp file.

Any thoughts Bob?

"Michael" wrote:

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael

Hi,
I said I'd write back when I had the answer and I've got it! You need the
Office Enterprise 2007 edition in order to use GPO to deploy office 2007. If
you have a volume license agreement you can download it now from
licensing.microsoft.com. I have, and i've tested it and it work. It is as
easy as they make out, the problem was that Technet were shipping the ProPlus
version, even though they said they were shipping enterprise, which was why
it wasn't working. Rock on Mircosoft!!!
Hope you have similar experiences! Good luck.

"Michael" wrote:

I suspect they may force us to use BDD for deployment. I hope not. I've
worked somewhat with the BDD beta and Vista but not Office 2007 yet. It is a
much more complicated path.

Michael

"Danny" wrote:

Hi,
At last I have found someone with the same problem as me. I would love to
be able to give you the answer, but as yet I don't have one. I have loads of
experience of deploying Office 2000/XP and 2003, all of which seemed really
easy in comparison to 2007, although Microsoft (and I do love them) suggest
this is the easiest yet! The idea of adding an .MSP file to the updates
folder is brilliant, but as soon as you do I get the exact same error message
that you get. If you then attempt to modify the XML file, well, you need a
degree in coding to get your head round that way. If this is a bug, it's a
very stupid one as it's holding up the end using testing of the product, if
you can't deploy it, you can't use it. GREAT.
I have been working on and off this since the release of Beta2 and cannot
find any useful information on this error anywhere. I have ask the Online
Concierge Chat in TechNet and have Googled every combination I can think of.
I'm with you budy, it's NOT you. If I ever find the answer, i'll be back!

PS: Clarification of the error: Only happens after you add the .MSP file to
the update folder. Office 2007 deploys a treat with no modifications in the
update folder, but then your end users / testers must add the PIDKEY and
activate it and install all the other options they need. Not great! SOMEONE
HELP!

"Michael" wrote:

I never resolved this issue. After wasting far too much time on it, I
abandoned it. I decided I would not test it in a domain environment until
they work out this issue or tell us what we're doing wrong.

Michael

"GrahamR" wrote:

Hi Michael/Bob

I too have had this issue. Having gone through everything in the resoure
kit which I downloaded from Microsoft I get this error when attepting to add
the proww.msi as a new package in a policy assigned to a workstation.

Having copied the contents of the appropraite folder from my Technet Plus
DVD of office 2007 Beta 2 to a installation point on my server I have run the
Office customization tool which has then saved the msp file to the update
folder. Then according to documentation I should then be able to assign the
proww.msi as a new package in a group policy. After selecting the MSI in the
file requester dialog you then get to choose whether you just want to assign
the package or click advanced. Choosing either of these options presents the
message same message documented about being unable to extract the deployment
information.

I have using GPMMC on my xp workstation as well as on a 2003 server. Same
thing.

I have not touched the config.xml as from what I read in the deployment
documents this will only overwrite what is in the msp file.

Any thoughts Bob?

"Michael" wrote:

Here's where the instructions are at:
http://officebeta.iponet.net/en-us/t...797111033.aspx. I've
attempted the "To Deploy with Group Policy" section. That's when I get the
error: "Add operation failed. Unable to
extract deployment information from the package. Run validation on the
package to ensure the package is correct."

I've got quite a bit of experience deploying applications in this manner as
well as writing my own installation packages for commercial applications. I
don't think I'm making some trivial mistake. However, I don't really have
time to dig into their installer package to determine why things aren't
working. I was hoping someone has already attempted this and figured it out.

Thanks,
Michael