How best should I manage Application updates via KACE (JAVA)
Hello,
Looking for some insight in best managing application updates via KACE. Java is used heavily in the enviroment and whenever Java has a update we get loads of helpdesk request that they are unable to access their application as the browsers are requring Java to be updated. I did read that JAVA updates take up to 10 days to reach KACE so I think this wont be any helpful relying on patch management for Java updates.
Answers (3)
10 days is accurate: http://www.kace.com/support/resources/kb/article/how-soon-after-their-release-will-patchesbe-available
If you need to update sooner, you can always use a managed install or script to push the update.
Examples:
http://www.itninja.com/blog/view/deploying-32-bit-java-silently-to-both-32-bit-and-64-bit-windows-via-mi
http://www.itninja.com/blog/view/kace-install-java-7-update-11-using-a-script-removes-previous-versions
I keep patching to MS updates only...Managed Installs are the best first option for pushing applications. They are easy to target, filter themselves from machines that already have the software installed, and run on client check-in. If I can't get a MI to work I'll build a script. The Java offline installer can be installed silently with the /s switch.
Personally I rely on patching for everything BUT Java, Reader, and Firefox. Why? The come out with updates so often and they require a bit of testing, so I just do MI's for those three. It's easy enough to build for each, and it allows me some flexibility and logic to cleanup older trash at the same time if needed.
