Software Deployment Question

Deploying office 2007 updates/changes

04/09/2008 22377 views

As many of you are aware the /adminfile option can be only used during the initial installation of Office 2007. So now the issue is how to deploy the updates after deploying the initial version. Say I want to modify some features after the initial installation, how do I do it without using config.xml?

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Well you cant apply updates to the original install (on the machines that already have it installed) without removing and reinstalling. So you need to deploy via 3rd party, ie. SMS, script, etc.
The updates folder is for new installs only.
Answered 04/10/2008 by: reds4eva
Second Degree Blue Belt


Could I follow up the question?
If later on the SP2 and SP3 is out, do we have to uninstall and reinstall it again?

Thank you.
Answered 07/17/2008 by: enzogoy
Orange Belt

No reinstall required for SP's. Service packs will apply directly onto whats already installed, by deploying the released exe or extracted msp files, or whatever method you choose to deploy.
You cant use the existing package to deploy it, ie. using the Updates folder. MSPs put in the updates folder are only applied to new installs.
Answered 07/17/2008 by: reds4eva
Second Degree Blue Belt

ORIGINAL: nvdpraveen
Say I want to modify some features after the initial installation, how do I do it without using config.xml?

Have a look at my reply to this note - it discusses the use of the /modify qualifier to the Office 2007 setup.exe. You would still need a modified config.xml if you go down this route.


Answered 07/18/2008 by: spartacus
Black Belt

Hi, I'm having simlar issues. I have deployed Office 2007 to a number of workstations. However I now need to add InfoPath to these installations. I have created my own config.xml to do this.

I use the following command line:
setup.exe /modify InfoPath.en-us /config AddInfoPath2007.xml

I receive the following error:
"This product installation has been corrupted. Run setup again from the CD, DVD, or other original installation source."

AddInfoPath2007.xml contains the following:
<Configuration Product="InfoPath.en-us">
<OptionState Id="XDOCSFiles" State="Local" Children="force"/>

I have no idea why this is failing, I cannot understand what else I need to do to get this to work. Any help would be appreciated.

Answered 07/24/2008 by: MRaybone
Senior Yellow Belt

We are getting ready to start an Office 07 upgrade. Some of our users already have infopath 07 or OneNote 07 installed. Updating them is possible, check out this link: http://technet.microsoft.com/en-us/library/cc179141.aspx

The one thing I have found though is if you have added files or custom installations to run after office is installed. They do not run. For instance we added the XPSPdf installer to the install and have it run after the install is completed. The files get added to the machine but they do not run. Just an FYI. We are running them seperately.

I have updated Infopath to full Office and back again using the /p switch with my MSP files.

Hope this helps.
Answered 08/12/2008 by: sandman2672
Yellow Belt

[font="trebuchet ms"]Hi All,
[font="trebuchet ms"]Has any one repackaged the office 2007(MSI/MST)?
[font="trebuchet ms"]Kindly let me know the steps which has been followed.
[font="trebuchet ms"]I know how to go about using OCT and creating MSP file,But our customer want only MSI/MST ,they can't deploy .exe file in their environment.
[font="trebuchet ms"]Look forward to hear from you all.

[font="trebuchet ms"]
Answered 11/20/2008 by: sunny1984
Senior Yellow Belt

ORIGINAL: sunny1984
I know how to go about using OCT and creating MSP file,But our customer want only MSI/MST ,they can't deploy .exe file in their environment.
Er...how does creating and using an MSI/MSP differ from creating and using an MSI/MST (in deployment terms, that is)? And where does EXE deployment come in? Confused...
Answered 11/21/2008 by: VBScab
Red Belt

Im guessing he means the deployment of setup.exe

Sunny, you'd have to use a wrapper.
Answered 11/23/2008 by: reds4eva
Second Degree Blue Belt

Thanks for your response.
Our client doesn't accept any applictaion in .exe format.All applications which we deliver to our customer should be in MSI/MST format.
We have tried the wrapper msi But it fails since Office standard 2007 has all MSI(Word,Excel,Power and Outlook) wrapped in an EXE.So when we wrap this EXE in a MSI it fails,as only one MSI can run at a time.
Kindly suggest some way to package this application in MSI/MST format.
Look forward to hear from you all.......
Answered 11/24/2008 by: sunny1984
Senior Yellow Belt

Sunny 1984... you should really not try to repackage Office2007 to a new MSI file using some repackaging tool. Even though it might be possible, what will you do with security patches that comes every month? these patches will not work with your new MSI file. This alone should mean that repackaging is not an option.

Create a new install for Office 2007 using /admin and then create a MSI wrapper, that simply launch this install form inside the MSI wrapper. For instance as a custom action.

You may need to explain to the customer about the many patches that Office has, even Critical Security patches that you usually deploy through WSUS or other deployment og Microsoft patches.
Answered 11/30/2008 by: jihan
Yellow Belt

ORIGINAL: sunny1984
Our client doesn't accept any applictaion in .exe format.All applications which we deliver to our customer should be in MSI/MST format.
Do you mean that they won't accept MSPs? Such a dictat indicates a fundamental misunderstanding and you, as the packager, need to explain to them why that is. If they want all future Office updates to have to go through the packaging process (and associated costs, of course) by all means proceed with creating a wrapper.

Do not, however, under ANY circumstance, re-package it. You'll still be fixing it up this time next year...
Answered 12/01/2008 by: VBScab
Red Belt

Hi guys-

Sorry to resurrect this old thread, but this is something I've been fighting with for a couple of weeks and just came across this thread while googling for info. I've got a custom .msp that I created using the OCT that works fine except when it come across a computer that already has an Office 2007 app installed. I've got a handful of users who have been using OneNote for a little while. I'm about to deploy Outlook and OneNote to my entire company, but in testing on a VM that has OneNote installed already, I get the Add/Remove/Repair dialog window. Is there a way to get this thing to skip past this and continue installing? I want this to be silent of course, with no user interaction. It works perfectly on machine that don't have any 2007 apps.
Answered 04/13/2010 by: wafialsafi
Yellow Belt


we are trying to update installed 'Office 2007' with 'Infopath 2007'. For the same, we have created an MSP using OCT. When we install this MSP using msiexec /p <path to MSP>, it is removing all existing features of Office 2007 (like Word, Excel etc.) and installing Infopath 2007.

Please help in this case, where we want install Infopath 2007 keeping intact existing Office 2007.

Thanks in advance.
Answered 04/27/2010 by: vishwanath_x
Senior Yellow Belt

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