Software Deployment

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).

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=

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.....

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"

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.... [>:]

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.

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.