/build/static/layout/Breadcrumb_cap_w.png

Include 3 patches

Hi,

A quick question. I have to repack OpenText Viewer 9.5 (IXOS) and when it is installed we also want to include 3 seperate patches for the software. The patches is 3 .msi files.
How is the best way to include them? I will do it in WISE.
Can I just install them after the installation of the OpenText Viewer software during the setupcapture?

Thansk!

0 Comments   [ + ] Show comments

Answers (7)

Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: aXz
Can I just install them after the installation of the OpenText Viewer software during the setupcapture?
No, because that would mean you're capturing an MSI which, as you have been advised in the past, is a BIG no-no.

How you go about the exercise depends on how your final 'package' will be deployed. If you're using a deployment system like SMS, Radia or Group Policy, you could simply push them separately. Alternatively - and this would be my preference, you could perform an admin install of your captured MSI, patch the admin install point and then run the installs from that install point.

If, however, you want a discrete, stand-alone package, you could build a WiseScript EXE containing command lines to launch each MSI (your captured one, plus the patches).
Posted by: aXz 16 years ago
Blue Belt
0
Hi,

I found out that it was really easy to include the patches if you use the install.ini file [:)]

In the end of the document you have pree defined if you want to intall some patches. It looks like this:

;ExecuteableFilePath1= \\network place you have the patche\Filename
TO
;ExecuteableFilePath9=
Posted by: aXz 16 years ago
Blue Belt
0
How should the command line look like?
I want to install the Setup.exe point to my install.ini and I want it to be installed silently

I tryd this one I found in the Package kb for a older version of IXOS but it dosent worked
SETUP.EXE SILENTFILE="install.ini" ALLUSERS=1 /qn

Should it be /qn in the end? Should't not be /s?
But it using MSI files in the background.....
Posted by: anonymous_9363 16 years ago
Red Belt
0
I think you have to use the '/V' switch if you want to pass parameters to MSIExec (which is what the setup stub is evidently doing):

. SETUP.EXE /V"SILENTFILE=install.ini ALLUSERS=1 /qn"
Posted by: aXz 16 years ago
Blue Belt
0
Hi,

I read that it was ok to use only the MSI file.
So I used simply msiexec/i [package.msi] SILENTFILE=Install.ini /qn

BUT, the patches I added in the .ini file dosen't install.... [>:]
Posted by: anonymous_9363 16 years ago
Red Belt
0
Well, which is it, MSIExec or Setup? Your original command line clearly shows Setup.EXE!

The Windows Installer engine knows nothing of INSTALL.INI. IIRC, that's used by IBM's set-up stubs, which is what I thought you were using. If you want to stick with calling the MSI directly, go the admin install point route.
Posted by: aXz 16 years ago
Blue Belt
0
Everything else I have put in to the install.ini the installation obey...
And its this way you gonna do it if you read the pdf from Open Text.

Anyway I have a left a Case to the Open Text group... They will look at it.
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