Software Deployment

Java(TM) Update fails to apply changes to your system. Error 1722

I'm still getting the error message 1722 (Windows Installer message) after installing 1.4.2.02 on some Windows XP Professional SP1 with all the latest patches. I've searched all over the forums and found other people having the same issues. Some people out there have tried the following:

-Disable Symantec Antivirus (Norton) prior to install
-Hard code the installation directory using the Windows Installer property INSTALLDIR=<path for program>
-Cutting down the long name j2re-1_4_2_02-windows-i586-p.exe to something like j2re142.exe.
-Applying the latest MS patches for XP sp1
-Regional Locale and Code settings. Everything in our enviroment has the same Regional Locale of English.

Command line used in Microsoft SMS 2.0
j2re-1_4_2_02-windows-i586-p.exe /s /v" /qb JAVAUPDATE=0 WEBSTARTICON=0

Event Log error mesasge has something to do with patchjre.exe. Details below

=================================================================================
Product: Java 2 Runtime Environment, SE v1.4.2_02 -- Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action patchjre, location: C:\Program Files\Common Files\Java\Update\Base Images\j2re1.4.2-b28\patch-j2re1.4.2_02-b03\patchjre.exe, command: -s "C:\Progra~1\Java\j2re1.4.2_02\"
=================================================================================

What is patchjre.exe and what exactly is this thing doing?

I have tried all of the above and still mixed results. After a failed install of 1.4.2.02 I would then reimage the PC and try again, the next time the installer would work. I'm getting this, on average 1 out of every 4 machines. I've also tried doing this just using a command line batch file and not Microsoft's SMS and still the same results. I've also enabled verbose logging to the installer using the /L*v switch and didn't really find anything out of the ordinary except for a failure return code of 3 talking about the patchjre thing which I stated above in the event log capture. We've determined that this is not a Group Policy for users or computers.

If any of you have any more ideas or a sample command line that has been tested and deployed and works, that would be great. Again, thanks for all your support and efforts in these great forums.