- This addon is the Microsoft Office Compatibility Pack, used for adding the Office 2007, and Office 2010 formats (docx, xlsx, etc) compatibility to Office XP and 2003
[Integration of msi package]
- The download consists of a 7-zip package which contains the following two files; O12Conv.msi & O12Conv.reg, it is necessary that you unzip the package to extract the two files. The O12Conv.msi can be used with the office integrator on the 'Config 2' tab in 'Chained Install' section so that after the installation of Office XP or 2003 it will install the OCP. It is only necessary to add the O12Conv.msi file in the chained installed section, the O12Conv.reg is only necessary if you are using other forms of deployment. You may need to change the switch you use to install the msi chained package (Full, Basic, etc) in order to get a silent install, I suggest leaving it on the default, Full, and modify only if you find you are not getting a silent install.
[color="Red"]2014-05-06[/color]
[color="Red"][Downloads][/color]
Office Compatibility Pack for English (ENU);
O12Conv_en-us_140506.7z - Download Site 1 (Dropbox)
****************************************************************************************************************************************************
[[color="Blue"]Information FRENCH - FRANCAIS (FRA)[/color]]
- Due to time restrictions and other reasons I am discontinuing the French Compatibility pack.
****************************************************************************************************************************************************
[Integration of OCP from Microsoft]
Microsoft released an updated Office Compatibility Pack that included all updates to Jan 06, 2010. There are now updates which need to be applied to this updated OCP which you can download the updated package above, however there are perhaps people who just want to install the OCP from Microsoft, this download which is an exe file is available here;
http://www.microsoft.com/downloads/details.aspx?familyid=941b3470-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en
If you try to integrate this Compatibility Pack by just adding the file you will find that after the office installation you will be presented with a window to do the Compatibility Pack installation. If you want to do a silent install you can add the following command, by clicking the 'Cmd Line' and enter "/q /norestart" (minus the quotes) in order to get a complete silent install. I've attached a screenshot to demonstrate

[Other Deployment Methods]
In my deployment i try to use group policy installs as much as possible, I know if you are doing one machine you can load the Office files and the integrated chained install for the compatibility pack onto a CD or USB key and run it that way. Also if you have a small network you can put the files on a network share and run the setup.exe for each computer.
However if you try to use group policy to deploy software you know that you need installation file in msi format, which is fine for Office installation, and equally for the installation of the compatibility pack, since it is turned into an msi, however you will probably find that the updates that are integrated and installed on the target system are not registered and thus will appear as needed updates, maybe this is not a big deal for you.
Some thoughts if you want to try to get it all done in one shot, i am a big fan of group policy preferences which is a newer feature in group policy, it allows you to add registry entries into target computers, hense you can add the update registry settings that way, alternatively you can script a startup script to launch the reg file to integrate into the target systems, also you might be able to apply the registry settings remotely, or finally just pass by all the systems to integrate the registry file.
Update [2010-01-15]
Since Microsoft has now released an updated Compatibility Pack file (FileFormatConverters.exe) you should be able to use 7-zip to extract the files, including the msi, to be able to have a msi package that can be deployed by group policy without the issues of adding the registry entries for the updates. You could either use an msi editor like Orca to create an mst (msi transforms file) to make any modifications you want on the orginal installation package, or you could also use the Office Compatibility Pack Administrative Template ;
http://www.microsoft.com/downloads/details.aspx?FamilyId=75BF0831-2F4D-48CE-A0B3-0D6586F9039B&displaylang=en
Which will allow you to make a group policy to make modifications.
There difference between these methods is just that the prior makes the changes on the initial installation vs the group policy which makes the changes only when applied to the particular machine.
Each deployment scenario is different so which way is best is dependent on the scenario, all this is here to do is tell you what some of the choices are.
Hope this helps some people