Office 2010 Std using OCT
Hi,
I have been tasked to create an installer that removes all previous versions of Office Std and Pro of 2003, leave Access (regardless of version), and finally install Office 2010 Std. I've created an msp file using the OCT that removes all Std versions of 2003 and leaves Access. But when I run the exe against a user that has Pro 2003, it leaves behind those Pro tools and other unwanted apps. I guess my question is, can I create something inside of the exe of Std 2010 OCT that will allow me to uninstall all versions of Pro and Std and then install 2010, while leaving Access. Or would it be easier to VB script all of this?
I have been tasked to create an installer that removes all previous versions of Office Std and Pro of 2003, leave Access (regardless of version), and finally install Office 2010 Std. I've created an msp file using the OCT that removes all Std versions of 2003 and leaves Access. But when I run the exe against a user that has Pro 2003, it leaves behind those Pro tools and other unwanted apps. I guess my question is, can I create something inside of the exe of Std 2010 OCT that will allow me to uninstall all versions of Pro and Std and then install 2010, while leaving Access. Or would it be easier to VB script all of this?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
WiseAppPackager
13 years ago
In a similar situation, I had used a single WiseScript to perform pre-install tasks and then install main app (of course there were other customization tasks as well). And, I'd learned from the experience that its better to avoid using scripts, however simple it sounds.
In your case - you can created scripts to remove unwanted apps and include those in 'Add installations and run programs' section of OCT.
In your case - you can created scripts to remove unwanted apps and include those in 'Add installations and run programs' section of OCT.
Posted by:
Helpy
13 years ago
Your best solution is to use the MS Office 2003 Custom Installation Wizard and creating a new or editing an existing .MST file. You can then create an 'uninstall' .MST with all options unselected (i.e. Not Available) except for MS Access 2003. Run this job/script/deployment prior to your installation of MS Office 2010 and you'll no longer see the see the Legacy folders for Office Tools/Shared Features/etc for the 2003 package in your start menu. It will be replaced by the Tools for the 2010 package if you chose to install them in your .MSP file creation.
I have found this approach to be a cleaner process then relying on the newer versions of the applications to take care of the cleanup. Hope this helps.
I have found this approach to be a cleaner process then relying on the newer versions of the applications to take care of the cleanup. Hope this helps.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
