Software Deployment Question

Enabling Silent Auto-update in Java 7.45 as a non-local administrator user - Java best practice gurus wanted ;)

10/21/2013 14093 views

I know you can turn on and off updates , but is this possible or ever been possible? My company wants to install java JRE as a silent-autoupdate "always update" kind of installation, but all my users are domain users, without admin rights. When it finds an update - it prompts for credentials and obviously they are denied. Is this even possible?  If it is not possible to "auto-update" non local admins, I can make the case to management that java releases need to be QA'd and controlled releases. My environment is adminstudio/installshield and SCCM. I know auto-installing updates to java without QA per version , in a enterprise environment, is not good practice, but its not my decision right now.


thank you very much!


 Edit:I need to add - my current environemnt is 7.40 as a patch in place, all notifications and updates turned off via MST table


0 Comments   [ + ] Show comments


All Answers


Short answer is No, it's not possible.  Updates, just like installs, require local Admin rights.

I'm going to put on my grumpy old man hat for a moment.  What you can do it to control the updates through SCCM - that's what its for!  Your management clearly doesn't have a clue about systems management.  Why did they buy SCCM?!  Lumpheads, everyone of them.

Ever see a patch cause a problem?  Yeah, you know why? 'Cause it happens all the time.  That's why we disable auto-updates.  To better manage and control our environments.  What you have to do is use AdminStudio to create a transform and use SCCM to push it silently.  Or you can throw public properties at the MSIEXEC command, but that's not my cup of tea.  Either way, you have to find a way to tell Management to 'go toss' and do things the right way. I'm sure it won't be easy to do...

Answered 10/21/2013 by: vjaneczko
9th Degree Black Belt

  • Ha, ha, ha! Absolutely! Well said!!

    Which Java 7 update was it that was completely broken? Was it 25? I can't remember but I *do* remember it was a total shambles!

    Also, on a related note, let me reiterate: do NOT - ever - blindly let vendor's set-up EXEs loose on your workstations. Always, always, always re-package.

    Oh and field-test your vendor MSIs, too. Adobe Acrobat Pro v9, anyone? Ha, ha, ha!!
  • I agree! I have finally talked them into packaging, QA'ing, and release management for each java update , and thank you for helping prove my case :)
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ