Edit the STD11.msi Office package with Orca
Ok I am in need of some help here. To be perfectly honest, this is the
first I've messed with orca and msi files.
Here is my overall goal.
Uninstall both Office XP and/or Office 2003 from a users system FIRST
Install Office 2003 through GPO.
I think I can, and correct me if I'm wrong, create a custom action in
the msi, which launches the cmd.exe with the command to launch an
external batch file. If I can set this up to run before ANYTHING else
is run within the MSI, that would be key.
If I can do this, I need to know how. Specifically, what customaction
type, sequence, anything I need to set up, I need the help with.
Any help is GREATLY appreciated.
Justin
first I've messed with orca and msi files.
Here is my overall goal.
Uninstall both Office XP and/or Office 2003 from a users system FIRST
Install Office 2003 through GPO.
I think I can, and correct me if I'm wrong, create a custom action in
the msi, which launches the cmd.exe with the command to launch an
external batch file. If I can set this up to run before ANYTHING else
is run within the MSI, that would be key.
If I can do this, I need to know how. Specifically, what customaction
type, sequence, anything I need to set up, I need the help with.
Any help is GREATLY appreciated.
Justin
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
greenmagnet
18 years ago
G'day.
You're better off using the Office Custom Installation Wizard from the Office Res Kit for creating Office MSTs.
http://office.microsoft.com/en-us/ork2003/HA011402981033.aspx
The office 2003 install can be configured to remove previous versions so you won't need to author any CAs of your own.
You're better off using the Office Custom Installation Wizard from the Office Res Kit for creating Office MSTs.
http://office.microsoft.com/en-us/ork2003/HA011402981033.aspx
The office 2003 install can be configured to remove previous versions so you won't need to author any CAs of your own.
Posted by:
shootist321
18 years ago
Unfortunately this won't work, as 1, it won't remove Access XP because it doesnt think to look for that, since it wouldn't be replacing Access with the Standard version of Office 2003. Also, if the computer already has Office 2003 installed, it installs a 2nd copy of the software, therefore negating any central administration for the nextupgrade. For example, if I use the GPO to assign Office 2003 to a computer that already has 2003, then go to the computer, uninstall office2003, office 2003 is still there, (The original install).
Posted by:
turbokitty
18 years ago
Well, it sounds like you want to wipe out all versions of Office even if they previously had PRO and then install STD. That's a bit odd, but the easiest way to do this is a separate GPO. Don't get cute and use a custom action as MSIEXEC doesn't like being run twice silently and nested installs aren't supported by Microsoft anymore (they specifically tell you not to use them).
Just run msiexec /x{guid} for each product code you have out there.
You could use a reinstall and reinstall mode property to handle your exiting 2003 installations, but that's only if they're the same product exactly. I'd just wipe them all out and start fresh with your new Office 2003 STD GPO.
But that's me.
Deploying Office with GPO.. that sucks.
Just run msiexec /x{guid} for each product code you have out there.
You could use a reinstall and reinstall mode property to handle your exiting 2003 installations, but that's only if they're the same product exactly. I'd just wipe them all out and start fresh with your new Office 2003 STD GPO.
But that's me.
Deploying Office with GPO.. that sucks.
Posted by:
nheim
18 years ago
Hi shootist,
are i assuming this right? All of the apps in question to uninstall are "per machine" installations?
If this is the case, figure out all the upgrade codes of this apps and bring them into the Upgade table with an MST.
See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/customaction_table.asp
Don't forget to add the 'ActionProperty' to the SecureCustomProperties property.
The same could be achieved by using a 'dummy' MSI just to uninstall the existing apps.
Hope this gives you some ideas.
Regards, Nick
are i assuming this right? All of the apps in question to uninstall are "per machine" installations?
If this is the case, figure out all the upgrade codes of this apps and bring them into the Upgade table with an MST.
See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/customaction_table.asp
Don't forget to add the 'ActionProperty' to the SecureCustomProperties property.
The same could be achieved by using a 'dummy' MSI just to uninstall the existing apps.
Hope this gives you some ideas.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.