![]() ![]() The policy has been applied to my test W10 VM - but the sluggishness was still there. We did change this through ESET PROTECT Cloud by changing the policy. I did call ESET (Netherlands) and was advised to disable "Network drive scanning" for the client computers. We have had this issue before and that made us decide to roll back to version 7.3. Unfortunately the connectivity (SMB) became sluggish again. During the last update round we decided to upgrade to ESET Server Security 8.0. Running ESET without HIPS is not recommended. We had some modules disabled like HIPS during testing - and left it disabled. However: when we downgrade to ESET File Security 7.3 everything runs fine for weeks - month (up time depends on reboots / updates). When we run ESET Server Security 8.x on the server the connectivity (SMB) becomes sluggish. We did assign 12 GB RAM and 12 cores to this Hyper-V. ![]() When the file server is freshly rebooted everything works absolutely fine. I did run tests from a test VM with Windows 10 and ESET Endpoint Antivirus. Most are connected to access switches at 1 Gigabit. This server is connected to the 10 Gigabit backbone. We are running a file server (details above this line). Server: Windows Server 2019 (1809) DC | ESET Server Security 0.0Ĭlient: Windows 10 (21H1) Pro | ESET Endpoint Antivirus. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |