Endpoint Protection

I have 2 issues regarding my Symantec Endpoint Protection 12.1.2 management server running on Windows 2012 server.

1. About twice a week I have to restart the "Symanect Endpoint protection Manager" service and the "Symanect Endpoint protection Manager Webserver" service on the server in order for users to logon to the SEPM management console.  Otherwise it just hangs on a progress bar after you enter the credentials.  Restarting the server also resolves this.
2. When I open the SEP Management Console (primarily from the java-based console), the majority of my servers show as OFFLINE.  Sometimes after waiting a couple minutes, they will change to ONLINE.  I have applied the following fix but it didn't resolve the issue.  This isn't as big an issue as the first item I listed. 

http://www.symantec.com/business/support/index?page=content&id=TECH167284&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D13686382111341f5439x1Bg46epGNQ00aQnC61F10r8sDfSBHX

Thanks.

If you restart the SEPM service than all clients will temporarily go offline from the SEPM.

You may need to enable some advanced logging on the SEPM to determine why its hanging

How to debug the Symantec Endpoint Protection Manager

HI, 

Agree with Brian .

If you restart the SEPM clients go offline from the SEPM.

Reagrds

Ajin

Focussing upon your first issue here (as the second is merely a symptom of your restarting the services as advised by Brian, "Thumbs Up" BTW), when you say you have the restart the services, can you confirm whether or not the services are actually stopped when you look at them?  Also, are you using the Embedded DB or the SQL one?

You may also want to take a look at the below articles relating to the console hanging on logon:

http://www.symantec.com/docs/TECH169955
http://www.symantec.com/docs/TECH95764
http://www.symantec.com/docs/TECH157761
http://www.symantec.com/docs/TECH163614

Other similar articles exist, but these just recommend what you do already (restart the services):

http://www.symantec.com/docs/TECH161661
http://www.symantec.com/docs/TECH132302

#EDIT#
Incidentally, I'd be curious to find out if the clients actually believe the SEPM to be online while it is in this unreponsive state.  To determine this, just wait until to encounter the issue whereby you cannot logon, then find/open a SEP Client via the Systray and client Help -> Troubleshooting and see what is says about the SEPM.  This test is only really applicable if the SEPM services are still started when in the error state.

Assuming the clients believe the SEPM to be online, can you also try logging into the SEPM's reporting component and see if that is working?  The reporting component can be accessed via the below kind of address:

https://<SEPM Hostname or IP Address>:8445/reporting/index.php

These tests are to help narrow down which part of the SEPM is encountering issues (Tomcat or Apache).