How can I deploy a office 2007 Custom MSP file to a computer that has a partial install of Office 2007 already on it?

I am trying to deploy a custom configuration of Office 2007 to computers that already have a presence of Office 2007 on them. I am using the same version of office 2007 but from a different server. This deployment works fine if the computer doesn't have any Office 2007 on it. I can even deploy a modification via a custom MSP and it makes the changes.-- But I f I deploy this MSP file to a computer that already has part of the office 2007 suite on it. I just installs Office 2007 and doesn't remove Office 2003. How can I get around this without having to uninstall office 2007 first?
havilandpAsked:
Who is Participating?
 
havilandpAuthor Commented:
Office 2007 can only remove previous versions of Office during the initial install. It is that way by design. I think that is a cop out on Microsoft's part
0
 
ThinkPaperIT ConsultantCommented:
Can you clarify your question?
Is the problem that you are trying to reinstall Office 2007 (with the custom.MSP) on top of machines with 2007?
Or are you talking about machines with the older version of Office (2003)?

Basicaly, what are you trying to accomplish with trying to push the custom.MSP to a system already installed with Office 2007? Are you trying to limit certain installs from taking place, removing extra components, resubmit the product key.. ???
0
 
havilandpAuthor Commented:
We were not ready to implement the full office 2007 so when users needed parts of Office 2007 (Outlook 2007, InfoPatth 2007 etc). The Office 2007 cd's were copied up to a network location and custom installs were done at these users computer and just the parts they needed were installed. Now I have been tasked to deploy Office 2007 to about 100 computers. Some of these computers do not have a presence of Office 2007 on them.

The ones that don not have presence of office 2007, I can deploy to without a problem. The install follows my configuration fine, I put SP1 and other patches and my custom .msp file (Removes all office 2003 except for access and installs ,word, excel, ppt, publisher outlook and infopath.) When I sent this with setup.exe /admfile to computers that already had presence of office 2007 it brought up the local setup of the computer and prompted for modifying. I them created an MSP file that told the computers to remove excel. When I deployed this MSP file to the computers taht I installed the initial Office 2007 it did Just what I had requested. I then modified the MSP file to Remove all office 2003 except for access and install ,word, excel, ppt, publisher outlook and infopath. I then deployed this MSP file (without Setup.exe) and it installed office 2007 but in did not un-install Office 2003.
Both the older 2007 partial installs were created from the same CD files and the same volume license key.
If I un-install Office 2007 from the computers that have the partial installs, I can deploy from my install point without incident. I have to think I should be able to modify the existing install?
0
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.

 
ThinkPaperIT ConsultantCommented:
How are you deploying Office 2007? And how did you deploy Office 2003 previously?

I don't know if this helps..
http://technet.microsoft.com/en-us/library/cc179141.aspx

Take a look especially at this command:
msiexec.exe /p \\server\share\custom.msp

Note I haven't tried it myself
0
 
havilandpAuthor Commented:
I 've done that. The problem is You do a custom install of Office 2007 and only install infopath 2007 because you need that to use say sharepoint 2007. 6 months later you get the ok to migrate users to Office 2007 but not install Access 2007 but keep Access 2003. On the computers that had only infopath 2007 on them, they will get office 2007 but it doesn't un-install Office 2003. you end up with both versions of Office on your computer.
0
 
ThinkPaperIT ConsultantCommented:
What is the particular reason for needing to keep previous version of Access 2003?

And back to my previous question, how did you deploy Office 2003 and how are you deploying Office 2007 now? Are you using group policy, scripting?

Also - were you ever able to successfully do a _complete_ Office 2007 install on top Office 2003? (thus being able to completely remove O2k3)?
0
 
havilandpAuthor Commented:
We have users taht have databases from access 2003 and they're are concerned with upgrading to access2007 and having compatability issues.
Office 2003 was mostly installed from network during build of computer, some were installed via group policy in the domain.
For the issues I'm having now the computers are not in the domain. I am deploying office 20007 with a package I created . It copies the whole office 2007 structure down to the computers windows\temp directory and runs the setup.exe with custom msp file. If the computer doesn't have any presence of Office 2007 it removes all office 2003 (Except for Access) an installs sp1 and other patches from the updates directory and installs all of Office 2007 except for access with out any problem.

If a presence of Office 2007 is on the computer the whole office 2007 structure is copied to the windows temp directory and the msp is run without setup. Office 2007 gets installed with no issues but Office 2003 is not un-installed.
0
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.

All Courses

From novice to tech pro — start learning today.