I need to combine Ms Office sp3 and mst that has already been created to install the Access.msi.

Can anyone give me some pointers as to be best way to do this.

I've created an msi with the items that the patch contains.

We cannot specify an msp install due to the way the s/w will be deployed. Ideally some util (mergemsi.exe maybe?)or way of combining the sp3.msi i have created with the .mst would be best but short of adding each file/reg entry into the mst manually I don't know of an easier way?


cheers
0 Comments   [ + ] Show Comments

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.

Answers

0
TOBES_UK:
I've use this in this syntax in the past and it worked out perfect for me:

To update the administrative installation point with the patches run the following commands based on the syntax:

msiexec.exe /p [path\name of MSP file] /p [path\name of MSP file] /a [path\name of MSI file]

Hope it help u.
Answered 02/16/2006 by: MSI911
Senior Yellow Belt

Please log in to comment
0
Couple things:

The msp patches the MSI, not the transform. The transform just specifies what should be installed from the MSI.

Typically deploying office, and then later on deploying a patch would work like this:

Inital deployment:
1. Create an admin install point from MSI
2. Deploy the MSI to your environement with an MST to specify what gets installed.

Patch is released for office:
1. Patch your administrative install point.
2. Send reinstall command to everyone that has the original version.
Answered 02/16/2006 by: Bladerun
Green Belt

Please log in to comment
0
Cheers chaps, modified the .msi with the .msp and will use the original .mst when deploying....Job done :) (going to like this website).
Answered 02/17/2006 by: TOBES_UK
Senior Purple Belt

Please log in to comment
0
Hi again, thought i was gaining ground on this item but I'm now encountering an issue with running the below:

MSIEXEC /A "source.msi" TRANSFORMS="source.mst" TARGETDIR="destination" SHORTFILENAMES=TRUE

I'm running this to create an admin install with shortfilenames to publish up to Radia for deployment.

I'm getting the following error...

"YOU CANNOT CREATE AN ADMINISTRITIVE INSTALLATION IMAGE FROM THIS SOURCE. PLEASE RUN SETUP /A WITH AN ORIGINAL INSTALLATION SOURCE."

Any ideas chaps?
Answered 02/20/2006 by: TOBES_UK
Senior Purple Belt

Please log in to comment
0
i am not 100% sure but it may already be an admin install and therefore you cannot create an admin from an admin.
are the files uncompressed beside the msi?
check the admin table of the msi to ensure that entries are present
Answered 02/20/2006 by: misk
Orange Senior Belt

Please log in to comment
0
ORIGINAL: misk

i am not 100% sure but it may already be an admin install and therefore you cannot create an admin from an admin.
are the files uncompressed beside the msi?
check the admin table of the msi to ensure that entries are present



Cheers misk, was thinking upon the same lines but recalled the .msi I had /a /p'd had already had this done for sp2 and was ok when i /a /p's it again for sp3.

BTW no compressed files beside the msi. What entries should present in the table?
Answered 02/20/2006 by: TOBES_UK
Senior Purple Belt

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