I'm looking for recommendations for how you all are keeping up with keeping Java current. This week was the first time where Java update was released (8u51) and our working Java installs (8u45) in IE stopped working the same or next day of the new release. In the past, we seemed to be able to keep going for at least a week while the new one got pushed out (see my earlier article on how I push out Java).
I reread Java's config file documentation, and the "deployment.expiration.check.enabled" seems to just suppress the notification to the user of expiration, whereas I may have read that earlier that it wasn't doing the check for expiration at all.
Maybe I should be looking again at using the Patch Management to push java. Does anyone have experience with how well that works when IE is left opened (or Chrome, I realize Chrome blocks java but I don't know if Chrome interferes with the installer). I used to care about using the config files so the user wouldn't see prompts, but we have business critical apps that depend on working Java in the browser, so now I just need to know the best way to support Java 8 updates with CMS 7.5.
I also need to make sure the old versions are removed from the PCs.
It seems like with the blocking of old versions - it would make more sense to push Java once to the users that need it & let Java update itself if it can do it well & remove the old version(s). I don't really trust their mechanisms much though.