Software Deployment

ORIGINAL: igluscic

1. The setup /adminfile command line only works on the initial installation and

2. The MSIs for the individual pieces of Office 2007 don't appear to behave like the MSIs I've seen previously. For example, in Office 2003, I believe I could have added Publisher by simply running an MSIEXEC /I Publisher.msi, or something to that effect. So far, if I try to do the same with the PublisherMUI.msi, it exits abruptly. The tail of the log file tells me that the configuration completed successfully, though I don't see any evidence that it actually was installed.

Does this sound familiar to anyone? I'd appreciate any insight that's offered.

Thanks!

-Ivan.



Ivan, 2007 is quite different from 2003 as you've already discovered. you cannot use the msiexec method anymore. You have to use the setup.exe

If you can look at the MSI in Orca and figure out which features you want to add, then you may be able to use ADDLOCAL=Feature to add it. But read up on office 2007 because there really are quite a few differences, and I have not had good luck getting Microsoft to respond to problems.

http://msdn2.microsoft.com/en-us/office/bb330659.aspx

Good luck, Owen

Hello,

You are correct in stating that you can only use setup /adminfile on the initial installation, however the /modify qualifier can be used with setup.exe. The following is an extract from a Technet article

[font="Courier New"]/modify [ProductID]
Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID]in the Setup.xml file for the product you want to modify.

The Setup.xml file is located in the core product folder on the network installation point. In Setup.xml, [ProductID] is equal to the value of the Id attribute of the Setup element. For example:

- <Setup Id="Pro" Type="Product" ProductCode="{30120000-0011-0000-0000-1000000FF1CE}">
Example
\\server\share\Office12\setup.exe /modify Pro /config \\server\share\Office12\AddOutlookConfig.xml

where Office12 is the root of the network installation point.

So all you need is a modified config.xml to instruct setup.exe to add the Publisher feature. You would modify the config.xml in the Publisher.WW folder on the installation point and create an OptionState element in this file as follows :

[font="Courier New"]<OptionState Id=”PubPrimary”
State=”Local”
Children=”force”
/>


Regards

Spartacus

What do I put in the Config.xml just to add all office 2007 features to an existing installation? (Since I can't use an msp file.)

EDIT:
After an ordeal I've got it:

(myconfig.xml)
<Configuration Product="Enterprise">
<Display Level="basic" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<OptionState Id="ProductFiles" State="local" Children="force" />
</Configuration>

(officefix.bat)
start /wait "" "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\Office Setup Controller\setup.exe" /modify Enterprise /config %cd%\myconfig.xml
rmdir /s /q "c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office"


Of course the Analysis Tookpak add-on in Excel still isn't active by default, which is what brought this on...