randyad

Again kindly assist me with creating a dynamic group to exclude a server from policies applying to all computers, I’ve created a policy to allow ports 8080 and 4000 on server but it seems not to work , I think there are other forced policies that’s not allowing this one to work, so I want to create a dynamic group to exclude the server from all applied policies, currently the server is under static group all

Yes I when we disable the whole real-time file system protection down for the wsus server, clients started to communicate and after some days they stopped, but when we bring the whole eset protect down, everything starts working fine

So we disabled the real time file system protection and clients started to communicate with the wsus server but after some days, they all stopped so currently we’ve disable everything which is not advisable, so we want to understand the cause or reasons why eset may be blocking the communication from endpoints to the wsus servers, and yes we disabled network traffic scanner but it didn’t work

I have created a policy to allow ports 8080, 4000 and 443 on a specific server, it seems to me that there’s another forced policy applying to all endpoints that’s not making this new policy work, I want to create a dynamic group and exclude that server from all policies applying to it, how do I go about it and if you have other methods that will be useful I will be glad to hear

we have eset in our network and recently found out that the servers and workstations in our environment are unable to communicate with the wsus server for updates but if you disable all the features including real time file system protection, HIPS, IDS, botnet protection and etc clients are able to fetch update from the wsus, kindly assit