11-22-2012 05:22 PM
Fairly straightforward question... we just upgraded to BES Express 5.0.4 for Exchange and I noticed during the install that Java 6 Update 31 was installed. I'm assuming that BES now exclusively uses J6U31 now but as everyone knows BES and Java do NOT co-exist peacefully and updating Java on a BES server is painful to say the least.
We now have 4 Java versions on our BES Server:
Java 6 Update 15
Java 6 Update 18
Java 6 Update 30
Java 6 Update 31
Best practice is to get rid of old Java versions due to security holes... can I safely remove the old versions or will that knock out my BES server?
11-23-2012 03:11 AM
11-23-2012 02:37 PM
Hmm don't ever recall importing anything so I'm guessing it's safe to go ahead.
Is there a way to check the registry ahead of time to ensure all the BES java paths are pointing to the new Java version? Is there a list of registry entires to check somewhere?
11-26-2012 09:43 AM
Java been updated? Dont update it, it is not needed but check the following
02-20-2013 01:49 PM
version has not been mentioned but might be ok
02-22-2013 05:27 AM
My colleague has upgraded to Java 6 Update 39 last week and had some troubles afterwards. But solved it with the community descriptions ...
and I just upgraded our BESX to 5.0.4 + Security Fix for TIFF images and it installs Java 6 Update 31 ... so, I used the instructions here to uninstall Update 31 and use Update 39 again ...
For nobody except us admins has access to BB server and no one should surf internet on it, we maybe won't need any (further) Java update (Java 6 is EOS, and latest and recommended version is 7 Update 15) but I'll check with my boss if he can sleep better when Java is actual everywhere