Office 2007/B2 Group Policy Installation

M

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
 
M

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
 
M

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
 
D

Danny

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!
 
D

Danny

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!
 
D

Danny

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!
 
D

Danny

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!
 
M

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
 
M

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
 
M

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
 
M

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
 
D

Danny

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.
 
D

Danny

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.
 
D

Danny

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.
 
D

Danny

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.
 
F

Fred Zilz

Anyone have a solution for those of us who's volume license is for Prof plus,
not enterprise?
 
F

Fred Zilz

Anyone have a solution for those of us who's volume license is for Prof plus,
not enterprise?
 
F

Fred Zilz

Anyone have a solution for those of us who's volume license is for Prof plus,
not enterprise?
 
F

Fred Zilz

Anyone have a solution for those of us who's volume license is for Prof plus,
not enterprise?
 
D

Danny

Yeah, hi, I do. I was a little over eger in my last post, and hadn't fully
tested the deployment. I have since discovered that any custom .MSP files
that you create using the OCT (Office Customisation Tool) do not get applied,
to any version of Office 2007, when deployed via Group Policy. This is a
little strange and rather anoying, as it seems there is no GUI customisation
tool available for enterprise deployment users. I'll confess to not reading
the instructions properly first time round, if you follow this link and ready
it carfully...

http://technet2.microsoft.com/Offic...52d2-4967-ab9d-0e199c9bf0041033.mspx?mfr=true

....it does say, that MSPs created via the OCT do not get applied during GPO
deployment, and this is a disadvantage of this deployment process. GREAT!!!

You must now configure the config.xml file in the
Office2007Version.WW\Config.XML. It lists the options that are available to
be changed/customised and gives links to further information. I havn't
tested this fully yet, but seems to answer the initial question posted here.

I hope for all our sakes that the config.xml route works. If you have any
further problems, post back and i'll see if I can help.

All the best,
Daniel

PS: It would be really useful if Microsoft produced an updated Office
Resource Kit that allows you to create MST files, but as yet I haven't seen
one.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Error when assigning office2003 to group policy 0
Office 2007 Std Group Policy Deployment Failing 3
Office 2007 Installation via Group Policy 1
Help! Using an MST file to modify installation with group policy 2
Office 2007 Professional Plus - Group policy - Error 12
Problem changing my deployment of office 2007 2
Access 2007 Runtime deployed through Group Policy 1
Office 2007 Enterprise 0

Top