Office 2007 config.xml and GPOs

[Niel Smith]

Anyone have any tips on how to get Office 2007 to use the config.xml file
when pushed out with a GPO?

I've added my corporate product code to the config.xml file in the same
folder as the .msi but it seems to ignore it.
I am following instructions posted on the MS TechNet site,
http://technet2.microsoft.com/Offic...9605-42d3-9798-3b698fff3e081033.mspx?mfr=true

 

[GrahamR]

Hello Niel

It may seem an obvious question but have you un commented out the line in
the xml file? (removed the <!-- at the start of the line and --> at the end)

I have found that the product key also needs to be entered without the
hypens, ie just the characters surrounded by speach marks).

Also, to my cost of a few sleepless nights, when I deployed through active
directory I found that the keys in the XML are case sensitive. When I
specified some optionstate details (later in the file) I found that I had put
OptionState ID rather than OptionState Id which generated a nasty error when
trying to allocate the msi though GPO. You may want to check that the cases
are exactly the same as the original MS file.

Regards

Graham

 

[Niel Smith]

That worked great Graham, Thanks!

Hello Niel

It may seem an obvious question but have you un commented out the line in
the xml file? (removed the <!-- at the start of the line and --> at the
end)

I have found that the product key also needs to be entered without the
hypens, ie just the characters surrounded by speach marks).

Also, to my cost of a few sleepless nights, when I deployed through active
directory I found that the keys in the XML are case sensitive. When I
specified some optionstate details (later in the file) I found that I had
put
OptionState ID rather than OptionState Id which generated a nasty error
when
trying to allocate the msi though GPO. You may want to check that the
cases
are exactly the same as the original MS file.

Regards

Graham