![]() SymDiag has been run and while there are some warnings, like Symantec firewall and the Outlook scanner are not enabled, that is by our design. It started happening a couple days ago on my own laptop (only have the client installed, no remote SEPM management tools or the console), but all the Symantec services are started when I check them. This happened ocassionally on 14.2.770.0000 but is happening far more with the newer version of the client. Restart the Symantec services, and then open Symantec Endpoing Protection." ![]() "Symantec Protection Cannot open because some Symantec services are stopped. This happens on (possibly more than just) Windows 10 clients but, it is happening on dozens of them - both clean Windows 10/SEP installs and when pushing the updated client via SEPM. This seems very much like the issue from last January.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |