Jump to content

Skynet

Members
  • Content Count

    21
  • Joined

  • Last visited

Everything posted by Skynet

  1. Okay, today it starts again... you got a message with a download link from our Onedrive.
  2. Hi Peter Randziak, At the weekend 9th/10th Feb. I've installed the latest V7, directly on Monday 11th the termsrv went up in massive cpu usage so I had to uninstall it again. Last weekwend 16th/17th I've installed the latest File Security V6.5, until now it performs well. I'm pretty sure it is an issue with V7, cause nothing else changed. I would like to help troubleshooting but if I install V7 again, we will have a lot of employee that can't work for hours until all data is collected and of course I can't say when it happen so waiting for technical assistance in that case is very time critical. So any idea?
  3. Hi Marcos, the amount of logins is no problem, we only have a maximum of 22 remote users, approx. 10-15 logged in during the working hours. If you ask for logins per minute it would be something under 1 (I still have checked the event log for suspicious logins). Sorry, can't say someting about the "startup file check task", I had to uninstall eset. I might give the old V6 file security a try and see how it performs.
  4. Hi, haven't found anyone else with these problems, but maybe eset can confirm? We are using a Windows 2016 Server DC v1607 (all updates installed) with remote desktop services aka terminalserver and Eset V7. ESET Security Management Center (Server), Version 7.0 (7.0.577.0) ESET Security Management Center (Web-Konsole), Version 7.0 (7.0.429.0) ESET File Security 7.0.12014.0 / 7.0.12016.0 (I think I've tested both) The "Remotedesktopservices" / termsrv generates a massive amount of cpu usage, I saw it using over 40% on a VM with 10x 2,6Ghz! It is impossible to work on the Server anymore. Once the Server is restarted everything works fine for some hours until "the bug" starts again. I've still uninstalled, reinstalled, used different policies and followed esets guidance for policies on terminalserver, nothing helped. I've done some tests over the last 2 weeks without eset and everyting was fine, last week I decided to install eset file security again and give it a try and today we've got the same problem again. I have to leave it uninstalled, so don't ask me for any traces! Maybe you can confirm a known bug or test it on your own.
×
×
  • Create New...