• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 433
  • Last Modified:

Office 2007 installation using OCT or config.xlm

I need advice on the best way to proceed with Office 2007 deployment for my company.  I recently upgrade all computers to Outlook 2007 and left the rest of Office 2003 intact.  In the coming months I need to upgrade the rest of the suite.  I created a custom .msp file using the OCT to deploy Outlook.  All went well.  One snag is that on the Remove Previous Version section of the OCT, I didn't accept the default behavior and instead told it to only remove Outlook.  I created a new .msp to enables the rest of the suite but when I deploy that it doesn't remove 2003.  I understand this to be by design and I can get around it by running the uninstall msiexec command.  The new .msp enables the rest of the suite but when I try to open Word or another program for the first time it proceeds to finish the install.  In the .msp I selected 'run all from my computer'.  How can I get around this so that the users don't have to install on first use?  Is modifying the config.xml file a better route at this point?  
  • 3
  • 2
1 Solution
So just to clarify:
1) Your first MSP installed Outlook 2007, removed Outlook 2003 and left the rest of Office 2003 intact.
2) Your second MSP is supposed to install the rest of Office 2007 and remove the rest of Office 2003.

1) When a User first launches Office 2007 (Word, Excel, etc..) Office 2007 completes the installation or perfroms a "Self-Healing"?
2) Does this step run pretty fast or take a while? (Want to see if it is just a few items or the entire Suite that is being Configured/Fixed)
3) Are you currently scripting the Uninstall of Office 2003?
4) If so, is this occuring before or after the Office 2007 is installed?
5) If it is after, this may be what is causing a "Self-Heal".
XTADMINAuthor Commented:
Good summary.  That is exactly that I'm doing.  Yes, when a user first launches Office 2007 it seems to complete the installation.  It takes a while.  Longer than I want my users to have to sit through.  It seems to be doing the entire suite.  I am scriting the uninstall of Office 2003 BEFORE the install of 2007 using "start /wait MsiExec /i \\pathtomsi\PRO11.MSI /qb REMOVE=ALL".
Out of curiosity, when just Outlook 2007 is installed along with Office 2003, where is the "OutLook.exe" located?  I am wondering if this is installed in the normal Office 2007 location or if it is installed in the Office 2003 location?

What may be going on here is that when you installed Outlook 2007, it wrote files or registry information that pertain to the Office 2003 install.  Now, when you run the Uninstall script to remove Office 2003 it may be killing some info for OUtlook 2007.  After Office 2007 is installed and a user launches the shorcut, a 'Self-Heal" is taking place.

Maybe try this:
If your second MSP is set to uninstall Office 2003, try to run it wihout first calling your Office 2003 Uninstall command, instead uninstall Outlook 2007 first.  This may allow the Office 2007 installation to migrate the data, perform the Uninstall of 2003  and not trigger a "Self-Heal",

Information about using 2007 Office suites and programs on a computer that is running another version of Office:
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

XTADMINAuthor Commented:
outlook 2007 is installed to c:\Program Files\Microsoft Office\Office12.  I tried installing office 2007 without removing 2003 and it still ran the self-heal after the install.  What if I run setup.exe /repair ProPlus after the install of 07?
Have you set the MSP to Run All From My Computer or Install on First Use? choosing the latter would make the system install the application on first run, otherwise it would be normal for the applications (MSI based) running an advertised shortcut to perform a self repair.  Basically Self Repair is where it sets up the HKCU/User based settings for example registry entries, Application Data files etc.. while you can override this, it's not recommended as some users may experience problems with configuartion settings etc..

You could try running a /modify ProPlus switch for the installation this should work.

XTADMINAuthor Commented:
/modify along with a customized config.xml file worked.  Thanks for your help
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now