Office 2007 Professional Plus - Group policy - Error

[Fred Zilz]

I am attempting to setup my Group policy installation package for my Office
Proffesional Plus. (We have office 2003 Professional w/ SA which upgrades to
Professional Plus). So I have the network installation point, but when I
attempt to setup my Software installation package and direct it to
share\pror.ww\prorww.msi

I get an error, "Add operation failed. Unable to extract deployment
information from the package. Run validation on the package to ensure that
the package is correct."

What am I doing wrong. I have seen a couple of newsgroup posts in other
newsgroups that indicated only the Enterprise version could be deployed
through Group Policy. I know this can not be true. That would be just
insane.

Please let me know the real answer.

Note, I did not create an MSP but rather edited the XML. I originally
started to create and MSP file but the /admin or installation customization
tool does not launch from the Professional Plus media (files not found).

Thank you in advance for your advice and support.

 

[Bob Buckland ?:-\)]

Hi Fred,

For the 2007 Office system a basic oNIP (Office network Installation Point) is a CD image. However, unlike Office 2003, where
separate Office Admin Instalation Points (oAIP) were recommended, you can pile on other Office 2007 products into your single oNIP
(or keep them separate if you choose.

Having said all of that, only Enterprise media based editions of the 2007 Office products will include the \Admin folder and
contents that, along with a volume license key, are the needed 'parts' to run the 2007 Office Customization Tool (OCT2007). For
Office 2003, only Enterprise edition volume license keys were able to setup an oAIP, so while the technologies and approaches are a
bit different the 'groundrules' for being able to use the customization procedures and tools are pretty much the same.


Even with the Enterprise editions and volume license key for 2007 deploying by GPO is not the recommended approach, in part because
GPO installations don't understand .MSPs for customization. In your scenario it looks like you're bypassing Setup.exe? Using
Setup.exe is pretty much required for Office 2007.

You may want to take a look at the information on GPO in the 2007 Office Resource Kit (ORK2007) at http://microsoft.com/office/ork

==============
I am attempting to setup my Group policy installation package for my Office
Proffesional Plus. (We have office 2003 Professional w/ SA which upgrades to
Professional Plus). So I have the network installation point, but when I
attempt to setup my Software installation package and direct it to
share\pror.ww\prorww.msi

I get an error, "Add operation failed. Unable to extract deployment
information from the package. Run validation on the package to ensure that
the package is correct."

What am I doing wrong. I have seen a couple of newsgroup posts in other
newsgroups that indicated only the Enterprise version could be deployed
through Group Policy. I know this can not be true. That would be just
insane.

Please let me know the real answer.

Note, I did not create an MSP but rather edited the XML. I originally
started to create and MSP file but the /admin or installation customization
tool does not launch from the Professional Plus media (files not found).

Thank you in advance for your advice and support.
--
Fredrick A. Zilz >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Fred,

For the 2007 Office system a basic oNIP (Office network Installation Point) is a CD image. However, unlike Office 2003, where
separate Office Admin Instalation Points (oAIP) were recommended, you can pile on other Office 2007 products into your single oNIP
(or keep them separate if you choose.

Having said all of that, only Enterprise media based editions of the 2007 Office products will include the \Admin folder and
contents that, along with a volume license key, are the needed 'parts' to run the 2007 Office Customization Tool (OCT2007). For
Office 2003, only Enterprise edition volume license keys were able to setup an oAIP, so while the technologies and approaches are a
bit different the 'groundrules' for being able to use the customization procedures and tools are pretty much the same.


Even with the Enterprise editions and volume license key for 2007 deploying by GPO is not the recommended approach, in part because
GPO installations don't understand .MSPs for customization. In your scenario it looks like you're bypassing Setup.exe? Using
Setup.exe is pretty much required for Office 2007.

You may want to take a look at the information on GPO in the 2007 Office Resource Kit (ORK2007) at http://microsoft.com/office/ork

==============
I am attempting to setup my Group policy installation package for my Office
Proffesional Plus. (We have office 2003 Professional w/ SA which upgrades to
Professional Plus). So I have the network installation point, but when I
attempt to setup my Software installation package and direct it to
share\pror.ww\prorww.msi

I get an error, "Add operation failed. Unable to extract deployment
information from the package. Run validation on the package to ensure that
the package is correct."

What am I doing wrong. I have seen a couple of newsgroup posts in other
newsgroups that indicated only the Enterprise version could be deployed
through Group Policy. I know this can not be true. That would be just
insane.

Please let me know the real answer.

Note, I did not create an MSP but rather edited the XML. I originally
started to create and MSP file but the /admin or installation customization
tool does not launch from the Professional Plus media (files not found).

Thank you in advance for your advice and support.
--
Fredrick A. Zilz >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Fred,

For the 2007 Office system a basic oNIP (Office network Installation Point) is a CD image. However, unlike Office 2003, where
separate Office Admin Instalation Points (oAIP) were recommended, you can pile on other Office 2007 products into your single oNIP
(or keep them separate if you choose.

Having said all of that, only Enterprise media based editions of the 2007 Office products will include the \Admin folder and
contents that, along with a volume license key, are the needed 'parts' to run the 2007 Office Customization Tool (OCT2007). For
Office 2003, only Enterprise edition volume license keys were able to setup an oAIP, so while the technologies and approaches are a
bit different the 'groundrules' for being able to use the customization procedures and tools are pretty much the same.


Even with the Enterprise editions and volume license key for 2007 deploying by GPO is not the recommended approach, in part because
GPO installations don't understand .MSPs for customization. In your scenario it looks like you're bypassing Setup.exe? Using
Setup.exe is pretty much required for Office 2007.

You may want to take a look at the information on GPO in the 2007 Office Resource Kit (ORK2007) at http://microsoft.com/office/ork

==============
I am attempting to setup my Group policy installation package for my Office
Proffesional Plus. (We have office 2003 Professional w/ SA which upgrades to
Professional Plus). So I have the network installation point, but when I
attempt to setup my Software installation package and direct it to
share\pror.ww\prorww.msi

I get an error, "Add operation failed. Unable to extract deployment
information from the package. Run validation on the package to ensure that
the package is correct."

What am I doing wrong. I have seen a couple of newsgroup posts in other
newsgroups that indicated only the Enterprise version could be deployed
through Group Policy. I know this can not be true. That would be just
insane.

Please let me know the real answer.

Note, I did not create an MSP but rather edited the XML. I originally
started to create and MSP file but the /admin or installation customization
tool does not launch from the Professional Plus media (files not found).

Thank you in advance for your advice and support.
--
Fredrick A. Zilz >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Fred,

For the 2007 Office system a basic oNIP (Office network Installation Point) is a CD image. However, unlike Office 2003, where
separate Office Admin Instalation Points (oAIP) were recommended, you can pile on other Office 2007 products into your single oNIP
(or keep them separate if you choose.

Having said all of that, only Enterprise media based editions of the 2007 Office products will include the \Admin folder and
contents that, along with a volume license key, are the needed 'parts' to run the 2007 Office Customization Tool (OCT2007). For
Office 2003, only Enterprise edition volume license keys were able to setup an oAIP, so while the technologies and approaches are a
bit different the 'groundrules' for being able to use the customization procedures and tools are pretty much the same.


Even with the Enterprise editions and volume license key for 2007 deploying by GPO is not the recommended approach, in part because
GPO installations don't understand .MSPs for customization. In your scenario it looks like you're bypassing Setup.exe? Using
Setup.exe is pretty much required for Office 2007.

You may want to take a look at the information on GPO in the 2007 Office Resource Kit (ORK2007) at http://microsoft.com/office/ork

==============
I am attempting to setup my Group policy installation package for my Office
Proffesional Plus. (We have office 2003 Professional w/ SA which upgrades to
Professional Plus). So I have the network installation point, but when I
attempt to setup my Software installation package and direct it to
share\pror.ww\prorww.msi

I get an error, "Add operation failed. Unable to extract deployment
information from the package. Run validation on the package to ensure that
the package is correct."

What am I doing wrong. I have seen a couple of newsgroup posts in other
newsgroups that indicated only the Enterprise version could be deployed
through Group Policy. I know this can not be true. That would be just
insane.

Please let me know the real answer.

Note, I did not create an MSP but rather edited the XML. I originally
started to create and MSP file but the /admin or installation customization
tool does not launch from the Professional Plus media (files not found).

Thank you in advance for your advice and support.
--
Fredrick A. Zilz >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Fred Zilz]

Thank you I will look at that. The instructions I have read so far show the
GPO steps but show enterprise as an example, they don't state that it is the
only license that works. Yes, it is the MSI that I use in GPO not setup.exe.

I have used GPO, because it is so easy, I drop a new computer into an ou and
reboot and all the software installs and I am done. GPO is already there in
the server products I have, so I am already setting up GPO, It is a shame if
I can not take care of everything right there.

 

[Fred Zilz]

Thank you I will look at that. The instructions I have read so far show the
GPO steps but show enterprise as an example, they don't state that it is the
only license that works. Yes, it is the MSI that I use in GPO not setup.exe.

I have used GPO, because it is so easy, I drop a new computer into an ou and
reboot and all the software installs and I am done. GPO is already there in
the server products I have, so I am already setting up GPO, It is a shame if
I can not take care of everything right there.

 

[Fred Zilz]

Thank you I will look at that. The instructions I have read so far show the
GPO steps but show enterprise as an example, they don't state that it is the
only license that works. Yes, it is the MSI that I use in GPO not setup.exe.

I have used GPO, because it is so easy, I drop a new computer into an ou and
reboot and all the software installs and I am done. GPO is already there in
the server products I have, so I am already setting up GPO, It is a shame if
I can not take care of everything right there.

 

[Fred Zilz]

Thank you I will look at that. The instructions I have read so far show the
GPO steps but show enterprise as an example, they don't state that it is the
only license that works. Yes, it is the MSI that I use in GPO not setup.exe.

I have used GPO, because it is so easy, I drop a new computer into an ou and
reboot and all the software installs and I am done. GPO is already there in
the server products I have, so I am already setting up GPO, It is a shame if
I can not take care of everything right there.

 

[Fred Zilz]

This the link for the information that led me to believe GPO was a good
solution for my environment, but which does not mention anything about
requiring the enterprise license in order to use GPO.

 

[Fred Zilz]

This the link for the information that led me to believe GPO was a good
solution for my environment, but which does not mention anything about
requiring the enterprise license in order to use GPO.

 

[Fred Zilz]

This the link for the information that led me to believe GPO was a good
solution for my environment, but which does not mention anything about
requiring the enterprise license in order to use GPO.

 

[Fred Zilz]

This the link for the information that led me to believe GPO was a good
solution for my environment, but which does not mention anything about
requiring the enterprise license in order to use GPO.