/build/static/layout/Breadcrumb_cap_w.png

Office XP Pro and Standard combination

Hi,

I created an administrative install of Office XP and after that I used ORK to make 2 MST (Vendor MSI).

MST 1: For Office Professional
MST 2: For Office Standard

If users have standard and needed to upgrade to professional. I have to deinstall Standard and push the Professional to the users. This is annoying because people forget to deinstall the software etc etc

Is it possible to do this from within the MSI?
So if Standard is installed and installing Professional, Standard will be deleted automatically

Or is it possible to update the components if users get the Professional group?

0 Comments   [ + ] Show comments

Answers (13)

Posted by: knight 17 years ago
Orange Senior Belt
0
Hi MARIN,

If you want, you can add a custom action to uninstall the one.

hope this helps,
knight
Posted by: MARIN 17 years ago
Orange Senior Belt
0
Ah okay thanks,

Do you know how, cause I am not familair with custom action.
I know what they can do, but I am not able to make one myself

Suppose I need to product code and search for it?
Posted by: knight 17 years ago
Orange Senior Belt
0
Hi MARIN,

Yes, you can use the product code to remove existing application.

knight
Posted by: MARIN 17 years ago
Orange Senior Belt
0
Can u help me out which tables i have to alter and what should be in them?
Posted by: knight 17 years ago
Orange Senior Belt
0
Add a property which is Path_to_MSIEXEC=c:\WINDOWS\system32\msiexec.exe

then create a Custom Action
Name: RemoveExistingOffice
Type: 50
Source: Path_to_MSIEXEC
Target: /X {Product Code} /QN (X means Uninstall)

Hope this helps,
knight
Posted by: MARIN 17 years ago
Orange Senior Belt
0
Thanks a lot,

Think this could work, but the 2 MST are build on 1 base MSI, so the product code for both applications are the same.
Does this matter?
Posted by: knight 17 years ago
Orange Senior Belt
0
Yes, you got the point. If they run on one MSI then the custom action would not work.
Posted by: MARIN 17 years ago
Orange Senior Belt
0
What about copying the MSI file and generate a new productcode for that msi?

Then there are 2 MSI with different productcodes.
Posted by: knight 17 years ago
Orange Senior Belt
0
I Havent tried that yet, and may be it will work.[8|]
Posted by: MARIN 17 years ago
Orange Senior Belt
0
Hmm,

I created another administrative install, but for some reason the productcode is always the same and cannot be changed.
If I alter the property productcode into something else then the original, the program returns an error.

Does anyone have an idea what to do ?

However, the difference between Standard and Professional is MS Access.
I could check of the msaccess.exe file is present and if so deinstall the software.

But dont know how to alter the tables to check if that file exists and if so deinstall
Posted by: Rhys 17 years ago
Orange Belt
0
If you're using the select media, there should be two different setup.exe. One should be setuppro.exe and one should be setupstd.exe. I'm wondering if those create different product codes and would solve the issues for you.
Posted by: Rhys 17 years ago
Orange Belt
0
When you move to Office 2003, there is a custom maintenance wizard which lets you change components without doing a full deinstall/install. Much nicer.
Posted by: MARIN 17 years ago
Orange Senior Belt
0
Ok, I am one step further.
I have 2 installations. And when Professional is installed and Standard is installing, Professional wants to deinstall.
However, when the installation of standard is running, and wants to deinstall Professional, it returns an error msiexec is already running.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ