Client has asked to package Office 2003 to co-exist with Office 2000 already on build. Anybodyout there done this already? What problems do you think it is inviting? Would it be better to just upgrade?
Any input appreciated.
0 Comments   [ + ] Show Comments


Please log in to comment

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


That can't be done,
you will have to use Softgrid (Softricity) or SVS (Altiris) to solve that.
Answered 05/24/2006 by: AngelD
Red Belt

Please log in to comment
Microsoft makes a provision for this and it works quite well, I recommend reading the Office 2003 Resourse Kit for complete details.

There are a couple of things to keep in mind: You can have Outlook 2000 or Outlook 2003 but not both. When you run the custom installation wizard you have the option of removing previous versions of Office but you can only run the mst provided by the CIW once, then you have to use the Custom Maintenance Wizard -- which does not have the option to automatically remove previous Office versions. So if you want to get rid of Office 2000 at some point and only use Office 2003 then you have to use a seperate utility that Microsoft provides. It works pretty good too.

It is always better to upgrade to the newer version and remove the older version and you open yourself to all sorts of issues, like which app is the default app and file associations, and unintended file conversions. It's best to solve the issue and then do the upgrade.

Hope this helps.
Answered 05/24/2006 by: papardun
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity