Yes this is a Volume Licensed copy.
Main Topics
Browse All TopicsAlright here is the break down. I have created a shared folder (full permissions) with all of the Office 2007 files. I am using the ProPlusww.msi for this installation push. I have created an MSP file for the configuration changes I would like to apply during the installation. I have used the msiexec /a (filename.msi) /p (filename.msp) to update the MSI file with the new patch file I have created. This was done by using this KB artical http://support.microsoft.c
The initiall install of Office 2007 via GPO is working but it is just doing a default installation. It appears that the MSP package that I have created is not getting applied when the Office is getting pushed. I have followed the above KB artical to incorporate the MSP file into the MSI file but it is not working.
More info: Once the default MSI package for Office 2007 is pushed if I go to the shared folder and run the .MSP file manually it will change the settings as it should have with the initial installation. Event viewer and rsop.msc both say installation is successful.
Any help is greatly appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi there, mst files are generally used to create custom installs of msi packages rather than msp. An msp is simply that - a patch to modify an existing installation. That's why it worked when you ran it manually after installing.
Anyhow, MS Office provides it's own tools to allow you to customise the installation - the CIW (custom install wizard). Use this wizard to create the mst file.
Sorry the correct term is OCT, not CIW, read this : http://technet.microsoft.c
Going into the Office Customization Tool it only gives me the option to create MSP files to apply to Office 2007 installations. It does not say anything about having to create an MST file. I understand the MST file as I have worked with this when deploying Office 2003 but not quite sure about Office 2007.
Yes I have gone to the root folder were setup.exe is located and ran setup.exe /admin from the cmd. I have created the MSP package with all of the settings and saved it to the same folder where the proplusww.MSI file is located. I then used the command msiexec /a (filename.msi) /p (filename.msp) as instructed by the KB artical i have listed above but it still isn't working. From my understanding this command is suppose to like "fuse" the MSP into the MSI with all of the changes, then you just use the MSI file and it will be modified as you intended.
I have been doing some more research on this issue and the only thing I could find that I wasn't doing was putting the file.MSP into the updates folder under the Office 2007 share. After doing this it was still not working. I have since been searching more and it appears that Microsoft has listed that this typically doesn't work.
I have gone to the second route of using the "config.xml" file to transfer the Office company settings to the installation. This was also without success.
The last resort I have tried was installing Office 2007 from a startup script. Using the synax belolw...
"\\server\sharename\setup.
Once I used this format in a batch file and created a startup script via GPO I was able to install Office 2007 with all of the settings and policys that my company uses (finally getting somewhere).
The only down fall with the startup script once I have run this on the computers it needs to be removed. There is also no "Uninstall" function like an MSI package that can be uninstalled from the server.
Hopefully anyone that is encountering this issue can incorporate a startup script l(ike I have) rather then MSI to MSP package for their needs.
Business Accounts
Answer for Membership
by: SandroSPosted on 2009-10-15 at 11:04:14ID: 25583079
Is the ProPlusww.msi from a OpenLicense CD? and the Code too?