/build/static/layout/Breadcrumb_cap_w.png

Modify existing Office 2010 installs by add Publisher 2010

I have existing installs of Office 2010 which we didnt include Publisher 2010 now I want to add this to some users without having to uninstall Office and reinstall with all features.

What I tried so far 

run networkshare/setup.exe /modify STANDARD /config NETWORKSHARE/addpublisher.xml

 

create xml file with contents below

<Configuration Product="STANDARD">

<Setup Id="STANDARD" Type="Product" ProductCode="{90140000-0019-0409-0000-0000000FF1CE}"/>

</Configuration>

 

What do I add to the xml file to make it run silent

 Ok I added this to make it silent

<Display

   Level="none"

   CompletionNotice="no"

   SuppressModal="yes"

   AcceptEula="yes"

/>

Log Name:      Application

Source:        MsiInstaller

Date:          31/10/2012 11:24:28 AM

Event ID:      1035

Task Category: None

Level:         Information

Keywords:      Classic

User:          MBRCDOM\markdart

Computer:      SOEWIN7VM.mbrc.internal

Description:

Windows Installer reconfigured the product. Product Name: Microsoft Office Publisher MUI (English) 2010. Product Version: 14.0.6029.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MsiInstaller" />

    <EventID Qualifiers="0">1035</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2012-10-31T01:24:28.000000000Z" />

    <EventRecordID>2226</EventRecordID>

    <Channel>Application</Channel>

    <Computer>SOEWIN7VM.mbrc.internal</Computer>

    <Security UserID="S-1-5-21-2367212997-3885883645-3035891645-1175" />

  </System>

Event Message

  <EventData>

    <Data>Microsoft Office Publisher MUI (English) 2010</Data>

    <Data>14.0.6029.1000</Data>

    <Data>1033</Data>

    <Data>0</Data>

    <Data>Microsoft Corporation</Data>

    <Data>(NULL)</Data>

    <Data>

    </Data>

    <Binary>7B39303134303030302D303031392D303430392D303030302D3030303030303046463143457D3030303066313261313664616136346331663632306639626234616135663737653462353030303030393034</Binary>

  </EventData>

</Event>

 


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Run setup.exe /admin, add the Publisher feature and save configuration as a .msp. Run the msp using msiexec /p /qb
Posted by: piyushnasa 12 years ago
Red Belt
4

Sorry buddy, but it is a lot simpler to do than this long procedure which you have mentioned here and there is no need for XML files.

Office 2010 comes with an inbuilt Office Customization toolkit which you can run to customize office 2010.

run setup.exe /admin and the customization toolkit will open up.

First try to bring it to the state you have right now and then just enable the Publisher feature in there and save it as an .MSP file.

Now you can deploy this MSP file on top of your Office 2010 packages already installed and then it will add Publisher to those users.


Comments:
  • so after creating the new MSP which I have no issues with. I only want to deploy to a group of machines and not affect any existing machines. If I place that msp into the updates folder do I just run the setup directly with no switches ? - Mdart 12 years ago
  • Just tried running the setup after creating the new msp file and i get the add remove dialogue box so this is not updating silently - Mdart 12 years ago
  • dont run setup.exe
    Run the MSP
    MSIEXEC /p <MSP> /qb - piyushnasa 12 years ago
  • thanks will give that a go - Mdart 12 years ago
  • That worked well thanks for your help - Mdart 12 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ