Jinitiator also supports a silent install through command line. Need to add "-s -sm" to your command line for a silent install. ie c:\temp\jinit1179 -s -m

This doesnt seem to work with the jinit 1.3.1.22 release

With Jinitiator 1.3.1.22, I was able to extract the required files to the temp directory as described in one of the previous posts, I then copied all the files to a folder I created on a network share, and moved the main install files from their "cd1" subfolder folder to the root of the new folder. (no technical reason, just trying to be tidy) The setup worked fine manually when I used the -s -sm parameters, but did not work when I attempted to distribute via SMS 2003 (SMS would get a return code of 0 from the setup and report success, but the app would not actually install). Rather than spend too much time troubleshooting, I repackaged the app into an MSI (posted that info in notes section)

I found for 1.3.1.18 you'll have to first extract the files before using the "-s -sms" switch. First, run jinit13118.exe, then copy the files it extracts to %TEMP% to another location. Then, cancel out of the installation, which will delete the %TEMP% files. In your package, install all nine files (data1.cab, data1.hdr, data2.cab, ikernel.ex_, layout.bin, setup.exe, setup.ini, setup.inx, and setup.iss), then launch "setup.exe -s- -sms" Installs totally silently.

Packaged and isolated Jinitiator 1.3.1.22 with Wise Package Studio 6.1, this worked if I used SmartMonitor in conjunction with Snapshot. When I used snapshot alone, the capture completed but I would get a dll registration error for actpanel.dll when I installed, even if I told the dll not to register. Fair warning - As of this writing I have successfully performed a capture, isolation, manual installation, and tested SMS 2003 distribution, but have not yet verified functionality with all of our business apps, so unknown if there are any problems using my captured version vs. the standard install - will post if I find any new info in that regard.

I MSI'd this for a client.

They had a specific web app that used this. There are some well know issues with Win7 some IE versions that crash.
This is what the testing matrix looked like.