Software Deployment

Here's a suggested method :

1) Merge the transform into the base MSI first, (e.g. Open MSI in ORCA, Apply Transform then Save As Transformed or use the wiusexfm script from the Windows Installer SDK.

2) Perform an admin installation of the transformed MSI you created at 1) and slipstream the MSP to the admin point at the same time using a command such as

msiexec /a <transformed .msi file> /p <.msp file>

Your admin point should then contain a transformed and patched installation that you can subsequently deploy.

I guess the success or failure of the above would depend on the scale of the changes your transform makes to the original base MSI - a simple response transform would probably work, but if your transform alters any component codes that the patch is expecting to find, then maybe not ...

Comments welcome from yourself and others as to any potential drawbacks to using the above method [;)]

Regards,

Spartacus

Hi Spartacus,
One thing I should have mentioned is that I can't alter or modify the .MSI, that's why I asked for the 3 thing at one time.
- is it possible to install in this way? :
msiexec /qn /i base.msi TRANSFORMS=transform.mst /p patch.msp

or is it possible to merge the patch and the mst?

Thanks again
KrisBcn

Try BASE.msi TRANSFORMS=transform.mst PATCH=Patch.msp /qn

this may or may not work...

if the /p didn't work, PATCH is another keyword you can try

Hi Gmorgan,
I've tried both cmd lines but it doesn't work anyway ...
I'll give a try to Active Setup, including the msp in the transform, and executing at logon.
If anybody has new ideas please let me know!!!

Thanks 4 all
krisBcn

ORIGINAL: KrisBcn

Hi Spartacus,
One thing I should have mentioned is that I can't alter or modify the .MSI, that's why I asked for the 3 thing at one time.
- is it possible to install in this way? :
msiexec /qn /i base.msi TRANSFORMS=transform.mst /p patch.msp

or is it possible to merge the patch and the mst?

Thanks again
KrisBcn


May I ask why you cannot "alter" the MSI?
You aren't actually altering anything different from what the patch should have been done after it had been installed.
This is still an installation procedure to support future upgrades/patches delivered from the vendor.

Preferred method would be admin install as spartacus stated, but apply the transform after which you may have to alter/recreate to fit the new updated MSI:
Create an administrative installation
Patch the administrative installation
Reuse or recreate the transform for the patched administrative installation
Install the MSI (from the administrative installation) with the transform

Hi Kris,
things would be easier, if you would tell us, what particular product you are talking about.
Have you created the Transform by yourself?
Regards, Nick

Hi again,
I'm talking about Office 2003 apps, custom transforms created by ORK, and its SP2.
I've got some rules to follow when packaging, and I'm not allowed to modify any original msi, that's why I asked that.
Finally the patch will be deployed separately.
That's to all. Thanks.
KrisBcn

Hi Kris,
who gives you this rule 'not to modify original MSI's'? This must be people, which do not quite understand, how Windows Installer works!
If you want to follow this rule, please forget about patching, because patching DOES modify the MSI!
If not on your installation point, definetely on each target machine!

You have two possibilities:
1. Do as AngelD and GMorgan suggested: Set up an installation point and apply all the patches there.
2. Install it with the Transform and local cache, but without the patches and let Microsoft Update take care about the patches.
Hope this helps a bit.
Regards, Nick

Here is a good reference page you could use from Microsoft: Distributing Office 2003 Product Updates

Nheim, there are things in life that we can't choose, and this is one in mine... :_(
But! I'm still alive! :D

Thanks to all anyway,
and AngelD, I'll take a look at the link asap.

KrisBcn

Gents,

I am attempt to do samething here...
but i tried to merge the msp into msi, then only use the transform to modify(slight modification only)
However, it works for manual installation, but not installation through AD.
it is published successfully, but when user click on the Add to install
the install progress will move and stop somewhere then fails
I haven check on the log, but....what could be the fault there?

Hi Wilfred,
are i assuming right, you set up an install point on a distribution server and applied the MSP on it?
Further you are publishing this software to some AD users and they try to install it as a standard user?
Do the users have the necessary rights on the install point?
you have to check the logs again, i'm afraid. But also go to the application tree of Event Viewer. Most of the time, you get some real useful error message in there.
Use 'WiLogUtl.exe' from the 'Installer SDK' to search through the log file.
For deeper investigation, read this: http://technet2.microsoft.com/WindowsServer/en/library/0907105e-7856-4c93-b97f-a9a306623af51033.mspx?mfr=true
Regards, Nick