We recently acquired Microsoft Office 2010 and to my surprise it does not bring an MSI to deploy it. But then I made a lil reasearch and found out that through the config.xml file you can customize MS Office by generating an msp. However I could not find anywhere else through the files where I could add customized table property entries (such as Company-Packagecode property, Author, Subjet, Title, etc) which I would normally add in the mst through Installshield. I was thinking about generating a dummy msi pointing installation vbs script (which contains embedded commands to run setup /admin blabla bla)

Does anyone have any ideas? Any other suggestions where I can have a lead.

Thank a bunch guys!!!

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

use the OST tool.. setup.exe /admin to customize.. Other than Company property which is under Organization Name value within "Install Location & Org Name" section, I dont see the others.

You might be able to Add Your own properties to "Modify Setup Properties" via the OST. Most of the fields you mention reside in a Summary table within IS or Wise, however not all MSI's have it. Plus, to my recollection, those values are only used if someone right-clicks on the MSI to read it. I don't think it appears in Add_Remove.

However, if your company is using this data for querying then you could modify the vendors MSI. I would not recommend this but you could create a backup of the OfficeMUI.msi file found in Office.en-us folder of your sources files. Then Open up MSI file via Orca, and then View, Edit Summary Information and save file with the same name. When you run the install it will use the edited MSI file you created...

for commandline install do this... setup.exe /adminfile config.msp

Answered 08/27/2013 by: ekgcorp
Tenth Degree Black Belt

  • Thanks for the prompt response ekgcorp, Im gonna give OfficeMUI.msi a try and see if edited entries applies through the install
  • It's not advisable to modify the vendor msi. As office is always run as a full setup that will be started with a command in your distribution tool It's sensible to extend the command to run an additional package (msi) to do your administrative settings.

    You could alternatively write your required registry values or run scripts in the appropriate location in the creation of your setup configuration. The values will then be included in the xxx.msp you have generated from the setup.exe -admin.
    • @ EVEEN...True that!! is it best practice not to change directly vendor's MSI therefore I believe editing through OCT is the most str8forward way to add values to the full setup
Please log in to comment
Answer this question or Comment on this question for clarity