Software Deployment

Essentially you want to create a WiseScript exe that "wraps" the install. All it will do is extract the patch to the desktop and execute it with a command line so that it runs silently. However, you do not want to re-package or capture a patch as a general rule. I don't really see the benefit of using Wise in this instance but the process would be pretty straight forward. If you have questions about Wise Packaging in general, see the examples that come with the product.

[quote]ORIGINAL: yarborg

Essentially you want to create a WiseScript exe that "wraps" the install. All it will do is extract the patch to the desktop and execute it with a command line so that it runs silently. However, you do not want to re-package or capture a patch as a general rule. I don't really see the benefit of using Wise in this instance but the process would be pretty straight forward. If you have questions about Wise Packaging in general, see the examples that come with the product.


thanks yarborg,

you mean just crerate a wrapper through wisescript.exe, inside we can call command that apply the patch for .MSI

msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb.

Am i right.

Thanks,Sourav.

Yes that is what I am talking about. You may also not have to use the original MSI but might be able to just reference the GUID of the MSI. Usually this can be found in the registry key HKLM\Software\Windows\CurrentVersion\Uninstall. You will have to go through the list of keys until you find one that says Office 2000. The GUID will be listed in the Uninstall key.

Keep in mind that if you are sending out the patch with an MSI you will need to put the patches and the MSI in the wrapper wise package, unless of course it is already on the local machine or stored in cache. Depends on how the original installation was done.