Office 2007/B2 Group Policy Installation

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

 

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

 

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

 

[Mruxsaksriskul]

Hey I got this error as well after playing with the config.xml file. I
found that having the setupupdates element or any other elements the
MSI does not like caused this error for our deployment. I ended up
stripping the config.xml to a bare minumum of product key, company and
it worked fine. I was trying to get the config.xml to site the custom
..MSP file I had made to no avail so I had to remove that element to get
rid of the error.

Hope this helps someone else.

Thanks,

Michael