1 of 1 people found this helpful
This is still an unresolved bug on Java's side, and it can cause failures deploying 32bit Java to a 64bit system. With our Shavlik Protect product our engineering team fixed this issue by using Protect's binaries to perform some additional steps, however, this isn't currently possible with SCUPdates. It is still something our engineering team is looking at so at some point in the future we might have a fix for this even with our SCUPdates content. I do not have any ETA, though.
I hope that helps.
Thanks for the Update.
I know that you guys must have done alot of testing on this subject, is there a slim chance that i could use that knowledge a little to here you guys what you think i could do to solve this particular issue.
Would you guys think that it is possible to install the full msi instead? - and then create a SCCM collection to push down to the clients that needs the install, or would this also result in the error.
What do you guys do?
As far as i can see, this rendors the Java update via the exe file as not possible?