Endpoint Protection

Anyone else having problems with the latest v14.2.770.0000 ?    It does not appear to be communication with the Manager.   The Policy Serial Number, Location Awarness changed to Disabled, and for the Server name, its showing an IP now vs the server hostname.

I had to uninstall and went back to the last stable version which is v14.0.2415.0200. 

Before v14.2.770.000 I installed v14.0.3929.1200, found out this one had an issue when a password was required for uninstalling.  It would not accept the password.  It appears v14.2.770.0000 also has the password uninstall issue.  I had to turn off the password required to uninstall. 

But more important is the problem with it communicating and getting the policy from the manager server.  The shield is green as if things are working correctly.  But when making policy changes, they do not get updated.  System logs shows they it failed to import the policy.  I was also getting a strange issue where IE was unable to go to to any web page.  But Firefox worked.  Outlook emails were not showing any images either due to this.  But after re-installing 14.2.770.0000 it seemed to fix that issue.  But the other issues are still there.  A system scan was supposed to initiate at noon today, but the client did not start scanning.

Has anyone else experienced any issues like this ?

It all started with this thread:

https://www.symantec.com/connect/forums/location-awareness-issues-after-upgrade-sep-142

may be what you're experiencing and if so it may be coming in 14.2 MP1.

I skipped 14.2.760.0000 and went straight to 14.2.770.0000.   While I am aware of the two KB articles below which are applicable to the version I never installed, I am having significant issues with 14.2.770.0000.   I updated the SEPM server and attempted to update a number of clients to 14.2.   Clients indicate they accepted the install package and some inidicate back to SEPM that they are pending a reboot.   However, none of these clients are communicating with the SEPM server correctly.    Clients I did not update, thus still running a 14.0 build, are functional and communicating.

In addition to communications to SEPM failing, these same clients no longer communicate to the cloud portal (sep.securitycloud.symantec.com).    Are these clients talking **at all** to my SEPM server?  It would appear that there is at least a minimum amount of communications as some of the DB timestamps are being updated for these clients.  Columns indicate some clients as having SEP client 14.0.x while having a policy build of 14.2.x.   

What are the work-arounds to get SEP working again?   Many of my clients are roaming laptops that I almost never have physical access to and remote only via SEPM.

https://support.symantec.com/en_US/article.TECH250796.html

https://support.symantec.com/en_US/article.TECH250794.html

Please open a support ticket for this.

Hey Um, Prime,

I have the same problem - unfortunately a solution is not available at the moment:

https://support.symantec.com/en_US/article.TECH250799.embed.html 

Remove the "Last Modified" date from the application specific Firewall policy rules - worked for me.