Java 7u40 - Messages Popping up on Client Machines

Comments

6 comments

  • Arjan Versloot

    Hi,

     

    Did you solve this issue?

    We have the same problem with Java 7u51

     

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Arjan,

    On those machines that are experiencing this problem make sure to deploy the ALTERNATE Java package. See the video below.

    0
    Comment actions Permalink
  • Matt

    Yup, I believe the alternate package solved this.  As far as I know, we haven't used the alternate for any other deployments, just the one (40) that we had this issue with.

    0
    Comment actions Permalink
  • Arjan Versloot

    thanks, I'm going to try that.

    0
    Comment actions Permalink
  • James Witt III

    Any idea what causes this? I have this message coming up on several packages that I have build and I would like to avoid it. Thanks.

    0
    Comment actions Permalink
  • Me

    Java update is very troublesome, and I am also trying to figure out the best way to update java without using the ALTERNATE package.

    We are running several applications that are dependent on Java - and there require weird settings to java. 

    Just killing browsers is problematic at least without having users prompted before. Although I find that the success rate of java deployment is dependent of killing browsers before an update.

    I added the message step... but as I see it, it is only giving the user an option of clicking "OK" - and if they don't do anything within the wait time, the update continues anyway.

    Is it possible to have give the users a choise of "yes/no" (or even better a postpone)?

    Regards, Lars.

    0
    Comment actions Permalink

Please sign in to leave a comment.