


When the SEP console couldn't connect to and push out a client to the workstation, I decided to turn on dropped packet logging on Windows Firewall on the workstation.

I decided to test redeploying a managed client to one of my workstations from the SEP management console. I found out what the problem was and I'm kicking myself in the tail for not seeing it sooner. You can also upgrade from 12.1.6 MP1 to the latest version of Symantec Endpoint Protection to recognize the ELAM component. Repairing the installation does not accomplish this task.Thanks all, for your replies and suggestions. To allow Symantec Endpoint Protection to recognize ELAM and enable the Symantec Endpoint Protection ELAM component, you must uninstall and reinstall Symantec Endpoint Protection. Your protection level is the same as it was with Windows 7. Therefore, the Symantec Endpoint Protection ELAM component is not enabled, and does not enable after you upgrade to Windows 10 with Symantec Endpoint Protection installed. Windows 7 does not include Early Launch Antimalware (ELAM). Limitations when upgrading from Windows 7 to Windows 10

The following operating system upgrade paths are supported with 12.1.6 MP1 / MP1a or later installed: See Uninstall Symantec Endpoint Protection for more information. The operating system upgrade stops if it detects an earlier version of Symantec Endpoint Protection. You must uninstall earlier versions of Symantec Endpoint Protection. Definitions as of this date include an update to the Eraser engine (115.1.1.10) that is required for Windows 10 compatibility. See Symantec Endpoint Protection support for Windows 10 Anniversary Update for support details.īefore you upgrade Windows, you must ensure that Virus and Spyware Protection definitions are from July 27, 2015, or later.
