/build/static/layout/Breadcrumb_cap_w.png

Upgrade from Office XP to Office 2003 with GPO

Hallo.
I have a major problem; I hope someone can help me.
We running Office XP as standard in our Company, Office Xp installs with a installation script under the OS Installation "WinXP" All users have WinXP and Office XP as standard. We install every "Core/Standard" applications with this installation script, all other applications installs from Add&Remove Programs. We distribute all this applications with software policy /gpo all software is in published mode.

I want to make Office 2003 available from Add&Remove programs so all users that want to install the new version get it Easy.
My problem is that if I distribute Office 2003 in published mode to USER the old version doesn’t uninstall because that version is installed manually "installation script"
If I publish office 2003 in assign mode to COMPUTERS is work fine, but I can not run this option because other LAN issues.
I MUST distribute the software in publish mode to USERS, so I need a solution to get Office XP upgraded good..

//Best Regards Richoo2000

0 Comments   [ + ] Show comments

Answers (2)

Posted by: WiseMonkey3 19 years ago
Senior Yellow Belt
0
Hi,
I'd be using the Microsoft Office Resource Kit (ORK) to create a transform file to publish with the MSI, as one of the option screens in the Installation Wizard has settings for removing previous versions.
If you have already tried this then there is another option in the Installation wizard to run programs or command lines, you could run the uninstallation from here.

Or be really crude and edit the MST file after you've created it and put in your own custom script to uninstall the old version first, this is generally not recommend as when you are creating transform files for Office products it's best to use the ORK.

good luck.
Posted by: richoo2000 19 years ago
Yellow Belt
0
We are using one MST file built from Costum Installation Wizard. I have the option remove all previous installations.. But i doesnt work, i think is because the application is installed thru the script.
Its one option to run the uninstallation from the run options in mst, but i dont think its work good because you already have ONE msi installation in process..

//Richoo
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