Deploying office 2007 updates/changes
Hi,
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?
Thanks,
Praveen
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?
Thanks,
Praveen
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
reds4eva
16 years ago
Posted by:
enzogoy
16 years ago
Posted by:
reds4eva
16 years ago
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.
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.
Posted by:
spartacus
16 years ago
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.
Regards,
Spartacus
Posted by:
MRaybone
16 years ago
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"/>
</Configuration>
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.
Cheers,
MRaybone.
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"/>
</Configuration>
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.
Cheers,
MRaybone.
Posted by:
sandman2672
16 years ago
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.
Mike
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.
Mike
Posted by:
sunny1984
16 years ago
[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"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
Posted by:
anonymous_9363
16 years ago
ORIGINAL: sunny1984Er...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...
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.
Posted by:
reds4eva
16 years ago
Posted by:
sunny1984
16 years ago
Hi,
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.......
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.......
Posted by:
jihan
15 years ago
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.
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.
Posted by:
anonymous_9363
15 years ago
ORIGINAL: sunny1984Do 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.
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 not, however, under ANY circumstance, re-package it. You'll still be fixing it up this time next year...
Posted by:
wafialsafi
14 years ago
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.
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.
Posted by:
vishwanath_x
14 years ago
Hi,
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.
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.