Add Microsoft Publisher to Office Professional Plus 2013

Question

Hi,
I'm trying to do a command-line installation to add Microsoft Publisher 2013 to an existing Office Professional Plus 2013. It was assumed that our staff would not need it, but as we have already received one request to get it installed, and the school year
has not yet started, we assume that others will also need it, measuring possibly in the hundreds or thousands. As a result, I'm looking for a batch scripting option.
Via other postings, I found it was possible to script the uninstall of the Office Upload Center via:
msiexec /i{90150000-0011-0000-0000-0000000FF1CE} REMOVE=WxpFiles
I'm looking to find something similar to add Microsoft Publisher. I know that the Office Customization Tool exists, but quite honestly, I don't have time to learn how to use it. I'd prefer not to send my network technicians out to the computers, especially
when there should be better options, but if it comes down to only the GUI, then only the GUI it is.

Answer 1

I'm still not entirely clear as to how this would work. If, for example, I use an MSP to add Publisher, then the user also then needs Outlook, would the Outlook MSP also need to have Publisher set to "Run all from my computer", or could that one just add
Outlook? I havent had a chance to run the OCT yet, my firewall consumed my day today.
By the way, it is exactly this type of question why I was looking for the way to add it via an msiexec flag. If I can remove a part of the Office installation that way, it seems to on me that I should be able to add one as well, even if it is not "the best
way" or "the right way".
You will need to try it out and see how it plays in your environment.
In my environment, we initially customised Office such that InfoPath was set to "Not Available". Subsequently, a need for InfoPath was identified, so I grabbed the original MSPfile which I deployed Office with (sans InfoPath), modified that to set InfoPath=RunFromMyComputer,
set that to [F]orce,  then pushed msiexec /p enableInfoPath.msp, to those computers which needed InfoPath.
Note that I re-used the previous/existing customisation file (the file which already had all features other than InfoPath set to enabled), and toggled the feature state of InfoPath.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)