ProPlus.ww/config.xml /ProPlus.ww/ProPlusWW.msi.
We used an uninstall startup script it would check the registry for office 2k3 and if present uninstall it, then the GPO would kick in and install 2007 not the most streamlined deployment procedure but it did the trick:). I've actually got Office 2007 GP deployment working however getting it to deploy/upgrade a machine already running Office 2003 has been a real bitch. It may be a stupid question but are you sure the key you've put in your config.xml file actually works with the SKU of Office you're deploying? If so, post your config.xml (minus the key:p) and I'll see if I can see any problems. Even then, it's still a bitch to do a normal, unattended, group policy install. Which MSI did you point the policy? As far as I know, only Office 2007 Enterprise can be deployed by Group Policy and you need to use the Enterprise.WW.msi (or something like that) file. Then unzip it to the location your drive letter office 07. a does nothing /admin loads the customisation tool, i've created a.msp but i dont know what to do with it recopy the files off the disk - i had to do that once. Download Proplusww.msi 2007 6 Jan The msi files are there but will not open/unpack/function. Run validation on the package to ensure that the package is correct. Unable to extract deployment information from the package. I'm trying to deploy Microsoft Office 2007 Pro but get error add operation failed.
I would still love to know how to do this.
If so, post your config.xml (minus the key:p) and I'll see if I can see any problems. It may be a stupid question but are you sure the key you've put in your config.xml file actually works with the SKU of Office you're deploying? Proplusww.msi 2007 Download