Software Deployment

I'm going to try just deleting it in my next java package since I don't really see any use for it. Now we're having problems with a files in use dialog on an upgrade so I'm having to do a taskkill

Delete from where? Inside the MSI?

You can do it either way.
Delete the entry from MSI/MST.
OR
Use the below command-line which works good.

C:\Program Files (x86)\Java\jre<version>\bin\jqs.exe -unregister

I haven't looked at a JRE in a while but, IIRC, the MSI is a collection of ZIPs in the Binary table which a series of Custom Actions extract. Therefore, removing JQS.EXE would have to be done in a CA also, since the RemoveFiles action is sequenced before the installing CAs.

Give Ian a cigar!
Yup, that's right. If you look at the file table in a java MSI it's practically empty. All the file installs and removals are done with CA's. (look at the removefile table and it's got a ton of stuff in it).

So, I use a CA to delete jusched.exe jupdate.exe and (now I'm thinking) jqs.exe and jqsnotify.exe

It's a shame that Sun/Oracle dont' just use Windows Installer standard, but given that Oracle is at v11 of its client software and still uses its horrid java based installer I'm not holding my breath.

Also, in update to my original post, jqs.exe is actually a service, Java Quick Starter so I'm thinking just to stop that before the installation since it's more graceful than killing a task.

good luck! (with Java you'll need it, LOL)

I finally ended up using a wise script CA which disables the jqs service second to last thing in deferred mode with a command line. I also run the same script standalone before the installation starts so that there won't be any fun with the previous version.

Oh, more fun. If you just try to use the service stop in Wise for windows installer or Wise script? Java ignores it. Thanks Oracle! So you have to have a command that does this,
"C:\Program Files\Java\jre6\bin\jqs.exe -unregister
THEN delete Jqs (for good measure I delete jupdate jusched and jqsnotify). that seems to clean up the Java installation pretty well.

Usage: jqs <mode> [<options>]

The following modes are supported:
-help print this help message and exit
-register install JQS service and register browser startup detectors
-unregister uninstall JQS service and unregister startup detectors
-enable enable JQS service
-disable disable JQS service
-pause pause prefetching
-resume resume prefetching
-version print version of the associated Java Runtime

Options include:
-config <config> set JQS configuration file
-profile <profile> set JQS profile file
-logfile <logfile> set JQS log file
-verbose <level> verbose operation

Hi folks,
we disabled that thing the very first moment when it was introduced ( 1.6.10, i think).
It's quite easy to do. Just change this 2 lines in InstallExecuteSequence:
UninstallJQS MODE="U" 3172
to:
UninstallJQS NOT Installed 3187
and:
InstallFinalize 3185
to:
InstallFinalize 3188

With this small change, the service will be disabled right after it gets installed.

Regards, Nick

Nice, but I'd still rather get rid of it altogether. I don't trust the Java MSI's [8D]

Aogilmor- For all the previous versions i usually just deleted jusched.exe, jucheck.exe & jureg.exe but in JRE 6 update 23 i don't see those files under "C:\Program Files\Java\jre6\bin" & i also did the system wide search for those files still no existance. Can you tell me what flavor of JRE were you working on & also if you might know the reason why it's not showing in my case. Thanks in advance

if you're using a system search forget it. the Java install uses CAs to install all the files. Look at the file table. Pretty much empty, right? except for a zip or 2. so you have to sequence a CA AFTER all the Java crap has already run.

And thanks for the idea of also getting rid of jureg.exe, what does it do? I'm also gonna get rid if jqs.exe in 1.6.24

jureg.exe is a Java(TM) Update RegisterTask. I see the the above mentioned files under "C:\Program Files\Common Files\Java\Java Update" only if i run the setup.exe but when i run the MSI none of update files are there. SO i guess if they are not getting installed it's a good sign because i don't really want them in my package.

interesting, thanks. I may delete that one too!
take care,

Java AutoUpdate (JAU) is now a separate installer, JAU.msi. It's wrapped by the JRE setup.exe. If you're working with the JRE MSI directly, then your package won't include JAU, which is probably a good thing.