Install Office 2007 by GPO

[Marc Bastian]

Hi,

as with Office XP and 2003, i'm trying to install Office 2007 by a GPO
object:
Therefore i used the built in OCT (Office Customization Tool) wich generated
a .MSP file. Placing this .MSP file under the \updates folder in the network
installation point does only affect installation made directly with
setup.exe (this works wonderful, but that's not what i want).

I read on the MS website (Technet) that i have to create/change a file named
"config.xml": But why can i do changes in the OCT and then have to edit a
..XML file? Why doesn't the OCT create this .XML file for me?

I hope this isn't a new "feature" for admins :-(



Thanks,
Marc

 

[Bob Buckland ?:-\)]

Hi Marc,

The Office Customization Tool (OCT) creates .MSP patch files to apply the customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e. precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

FWIW, deploying Office 2007 by GPO is not a highly recommended method for large scale deployments. The procedure (and the 'Note')
on this are at
http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

============
Hi,

as with Office XP and 2003, i'm trying to install Office 2007 by a GPO
object:
Therefore i used the built in OCT (Office Customization Tool) wich generated
a .MSP file. Placing this .MSP file under the \updates folder in the network
installation point does only affect installation made directly with
setup.exe (this works wonderful, but that's not what i want).

I read on the MS website (Technet) that i have to create/change a file named
"config.xml": But why can i do changes in the OCT and then have to edit a
..XML file? Why doesn't the OCT create this .XML file for me?

I hope this isn't a new "feature" for admins :-(

Thanks,
Marc >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Marc,

The Office Customization Tool (OCT) creates .MSP patch files to apply the customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e. precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

FWIW, deploying Office 2007 by GPO is not a highly recommended method for large scale deployments. The procedure (and the 'Note')
on this are at
http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

============
Hi,

as with Office XP and 2003, i'm trying to install Office 2007 by a GPO
object:
Therefore i used the built in OCT (Office Customization Tool) wich generated
a .MSP file. Placing this .MSP file under the \updates folder in the network
installation point does only affect installation made directly with
setup.exe (this works wonderful, but that's not what i want).

I read on the MS website (Technet) that i have to create/change a file named
"config.xml": But why can i do changes in the OCT and then have to edit a
..XML file? Why doesn't the OCT create this .XML file for me?

I hope this isn't a new "feature" for admins :-(

Thanks,
Marc >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Marc,

The Office Customization Tool (OCT) creates .MSP patch files to apply the customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e. precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

FWIW, deploying Office 2007 by GPO is not a highly recommended method for large scale deployments. The procedure (and the 'Note')
on this are at
http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

============
Hi,

as with Office XP and 2003, i'm trying to install Office 2007 by a GPO
object:
Therefore i used the built in OCT (Office Customization Tool) wich generated
a .MSP file. Placing this .MSP file under the \updates folder in the network
installation point does only affect installation made directly with
setup.exe (this works wonderful, but that's not what i want).

I read on the MS website (Technet) that i have to create/change a file named
"config.xml": But why can i do changes in the OCT and then have to edit a
..XML file? Why doesn't the OCT create this .XML file for me?

I hope this isn't a new "feature" for admins :-(

Thanks,
Marc >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Marc,

The Office Customization Tool (OCT) creates .MSP patch files to apply the customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e. precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

FWIW, deploying Office 2007 by GPO is not a highly recommended method for large scale deployments. The procedure (and the 'Note')
on this are at
http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

============
Hi,

as with Office XP and 2003, i'm trying to install Office 2007 by a GPO
object:
Therefore i used the built in OCT (Office Customization Tool) wich generated
a .MSP file. Placing this .MSP file under the \updates folder in the network
installation point does only affect installation made directly with
setup.exe (this works wonderful, but that's not what i want).

I read on the MS website (Technet) that i have to create/change a file named
"config.xml": But why can i do changes in the OCT and then have to edit a
..XML file? Why doesn't the OCT create this .XML file for me?

I hope this isn't a new "feature" for admins :-(

Thanks,
Marc >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Marc Bastian]

Bob,

Hi Marc,
The Office Customization Tool (OCT) creates .MSP patch files to apply the
customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e.
precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network
Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in
the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

Thats right! But the CIW created a nice .MST file.
With this .MST i have been able to easily deploy Office to all computers
within group policy.
I loved this way, because i deploy all our centrally managed application
within group policy.

Now, as you told me, i have to edit the config.xml file. Why can't the OCT
generate this file for me?
I think this would help me and lots of other people to deploy Office within
group policy.
At this moment, i really can't see the improvement or the "overvalue" :-(

FWIW, deploying Office 2007 by GPO is not a highly recommended method for
large scale deployments. The procedure (and the 'Note')
on this are at

http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

I am talking about 150 client, distributed over 4 sites. SMS would be a
little bit "oversized".
And as i told you: "i love" deploying apps with group policy


As i saw on this or other newsgroups the past days, a lot of people have the
same problem.
Hope Microsoft will improve this "feature" a little bit in the future.


Thanks,
Marc

 

[Marc Bastian]

Bob,

Hi Marc,
The Office Customization Tool (OCT) creates .MSP patch files to apply the
customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e.
precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network
Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in
the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

Thats right! But the CIW created a nice .MST file.
With this .MST i have been able to easily deploy Office to all computers
within group policy.
I loved this way, because i deploy all our centrally managed application
within group policy.

Now, as you told me, i have to edit the config.xml file. Why can't the OCT
generate this file for me?
I think this would help me and lots of other people to deploy Office within
group policy.
At this moment, i really can't see the improvement or the "overvalue" :-(

FWIW, deploying Office 2007 by GPO is not a highly recommended method for
large scale deployments. The procedure (and the 'Note')
on this are at

http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

I am talking about 150 client, distributed over 4 sites. SMS would be a
little bit "oversized".
And as i told you: "i love" deploying apps with group policy


As i saw on this or other newsgroups the past days, a lot of people have the
same problem.
Hope Microsoft will improve this "feature" a little bit in the future.


Thanks,
Marc

 

[Marc Bastian]

Bob,

Hi Marc,
The Office Customization Tool (OCT) creates .MSP patch files to apply the
customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e.
precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network
Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in
the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

Thats right! But the CIW created a nice .MST file.
With this .MST i have been able to easily deploy Office to all computers
within group policy.
I loved this way, because i deploy all our centrally managed application
within group policy.

Now, as you told me, i have to edit the config.xml file. Why can't the OCT
generate this file for me?
I think this would help me and lots of other people to deploy Office within
group policy.
At this moment, i really can't see the improvement or the "overvalue" :-(

FWIW, deploying Office 2007 by GPO is not a highly recommended method for
large scale deployments. The procedure (and the 'Note')
on this are at

http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

I am talking about 150 client, distributed over 4 sites. SMS would be a
little bit "oversized".
And as i told you: "i love" deploying apps with group policy


As i saw on this or other newsgroups the past days, a lot of people have the
same problem.
Hope Microsoft will improve this "feature" a little bit in the future.


Thanks,
Marc

 

[Marc Bastian]

Bob,

Hi Marc,
The Office Customization Tool (OCT) creates .MSP patch files to apply the
customizations. The Config.XML file lets you tailor what
features or .MSP files are applied, when the MSOCache is created (i.e.
precached or as part of setup). The default version is
already included as part of the initial setup of an Office Network
Installation Point (oNIP).

The Setup.ini file from Office 2000-2003 that is replaced by Config.XML in
the 2007 editions, wasn't created by the Office
Customization Wizard (CIW).

Thats right! But the CIW created a nice .MST file.
With this .MST i have been able to easily deploy Office to all computers
within group policy.
I loved this way, because i deploy all our centrally managed application
within group policy.

Now, as you told me, i have to edit the config.xml file. Why can't the OCT
generate this file for me?
I think this would help me and lots of other people to deploy Office within
group policy.
At this moment, i really can't see the improvement or the "overvalue" :-(

FWIW, deploying Office 2007 by GPO is not a highly recommended method for
large scale deployments. The procedure (and the 'Note')
on this are at

http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx

I am talking about 150 client, distributed over 4 sites. SMS would be a
little bit "oversized".
And as i told you: "i love" deploying apps with group policy


As i saw on this or other newsgroups the past days, a lot of people have the
same problem.
Hope Microsoft will improve this "feature" a little bit in the future.


Thanks,
Marc