Video Screencast Help

SEP 11 Manager Remote Console and Java 7

Created: 23 Oct 2012 | 4 comments

I had the SEP Manager (11.0.5) console working just fine on my Win7 Pro x64 box with Java 7 Update 7.  Today I upgraded to Java 7 Update 9 which broke my SEPM console where it now wants to install Java 6 Update 14 if I try getting to my SEP server via IE to reload the manager.  Did the usual to clear the Java temp files and uninstalled the SEP Manager via Add/Remove Programs but the webpage continually prompts to install Java 6.

Forum posts seem to indicate Java 7 isn't compatible although how was it working before when Add/Remove Programs only listed the 32 and 64-bit versions of Java 7 Update 7 on my PC?  I haven't touched my SEP server which is running Java 6 Update 35 just fine with the SEPM console.  I noticed Oracle's site has Update 37 as the latest Java 6 release.  Anyone know if this version is compatible with my remote SEP Manager or is there a way to get the latest Java 7 Update 9 to work?

Comments 4 CommentsJump to latest comment

Brɨan's picture

It isn't compatible but it will work cool

I've had a few versions of 7 work fine while other versions didn't.

See this:

Support for Java 7 and above

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Mithun Sanghavi's picture


Check this Article:

Support for Java 7 and above.

Java 7 is not supported as of now with SEP. However in the further releases of SEP, it would be supported.

In your case, Install the Older version of Java 1.6 update 31 and then work on the steps provided in the Article below:

Running two versions of the remote Java console for Symantec Endpoint Protection Manager on the same machine

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Clint's picture

FYI: I decided to try the latest Java 6 Update 37 on my PC.  At least the areas in the console which I oftentimes use appear to be working normally (i.e. who knows whether I only have partial functionality).  With all of these client-side Java issues, good thing I didn't upgrade Java on my server or else I'd be really in a bind.