AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Symantec endpoint protection v148/30/2023 ![]() ![]() I've made some internal DNS changes round about that time so the next couple of days I've spent playing with those. But when I reverted to the original setting issue remained. I then CleanWiped my computer and issue was gone! Reinstalled SEP Client, issue returned. Then I tried custom installing SEP client, removing component by component to determine which one was responsible. That took me couple of days again, as issue does not happen immediately after reboot. Sometimes among all that slugishness you get half an hour of uninterrupted operation, but this is rare. Usually when this behaviour starts computer is pretty much unusable.Ĭustom, component by component, installation did not point to the cause. Even with firewall component only computer was unusable after a while. Typical installation, everything there and with unmanaged client computer was running the whole day like it was brand new! As soon as I SylinkDrop it and connect to SEPM, responsiveness drops dramatically. I then thought there may be something wrong with my rules, but the problem happens even when client is connected to the group with default rules only. Nothing out of the ordinary in SEP client logs.įew days after I started troubleshooting procedure other users started complaining as well. #SYMANTEC ENDPOINT PROTECTION 14 END OF LIFE WINDOWS#Īs these were all 32-bit Win 7 users I thought that was something to look at, but then complaints started to come from some others as well.#SYMANTEC ENDPOINT PROTECTION 14 END OF LIFE WINDOWS 10#. ![]()
0 Comments
Read More
Leave a Reply. |