admindt

Thank you, I now understand what and how I need to apply the policies. Have a great day!

Really? So the lightning does not even have to be enabled - this is great, but like you said it will be inherited - it is a bit harder to grasp the concept, at least for me because I am afraid that one settings of the stricter policy will overwrite our softer policy. However this cannot happen, because they don't exist in the same groups. But if I would, lets say theoretically, apply both policies to "all" then I am thinking that the forced lighting options would be needed, because the two policy clash. This is how it looks like, I have a strict policy for "NB", "WKS" because there are all of our machines.

Hi Ufoto, thank you for your answer. Just want to confirm something, "Just make sure that the conflicting settings are enabled by clicking on the blue dot next to the setting. Don't use the yellow lightning for the restrictive policy as this will prevent inheritance breaking. " So the software policy which would be used for all windows clients has the blue dot on most of the settings, lets called it a "Strict policy". The "soft policy" for us in IT has lighting on most of the settings, and it is applied only to the "IT Department" group which I created in the console and there are our three machines. Is this ok? Cheers

This is solved, the issue was in this external DNS that we are using. They said that the problem was not on their side, but after I reported the problem they must have done something. Now I am seeing that my test clients have a green dot near every machine, before this was only on couple of them. Thanks for the support!

Hi, for some unknown reason I do not see the e-mail notification when you answer in this topic. Setting in profile are set to e-mail. We do have something like that yes, I wrote the e-mail to them and am waiting for an answer. I also notified our network guy.

To be honest, we are having some problems with our DNS, this is waiting to be solved. But the issues are not so serious that we cannot work as a company. You will probably ask that are the problems, well it had to do with us wanting to have Veeam as a backup solution for clients - this did not work very well because the mobile devices (laptops) are changing the IP too quickly for Veeam to catch-up with the correct IP (company-homeoffice-company or company-external client-company). We then did some adjustments in DNS like shrinking the non-refresh and refresh intervals to 4 hours. Now it is back to 1 day. We also use some protection external DNS - i will ask the company right away if the external dns which is used to sniff suspicious traffic is causing this. Will report back.

Hi, we have three clients (by clients I mean laptops) who are in IT department. The three laptops are inside of a AD group called "NB". The "NB" group also has every other laptop from various departments in our company including our three. If I apply a stricter policy where the recognized threat would be auto-deleted and want a softer policy for us in IT, and our three laptops WITHOUT MOVING them to a new "IT" OU - how would I accomplish this? Is there an option to EXCLUDE couple of clients from the policy? I did not find it. Cheers

Hi Martin, thank you. This does not seem to work, the machines connect but sporadically. Do we have to create an entry in DNS Manager?

At 8:44 the log was all green, and the client connected at 8:34 last time. I refresh the window and it is 1min later and again the same error like I have sent you in the status.txt/html. What is going on here.

additional trace.log file trace.log

Hi Marcos, thank you for your quick response, much appreciate it. The client did report in the morning today but still an error message is in the html file. I am attaching it here like you instructed me to do. I had to change it to .txt so just revert to .html. Cheers status.txt

Hi, I have a broad question with little details as I am not sure what to provide with the first post. I am testing ESET Protect Cloud, and have 15 machines in test, today all of a sudden 3 machines stopped reporting since 13:36, at the time of writing this post it is 16:41. I did not change the firewall settings, I tried with the wake-up command, reseting the machine (it is mine and I am working on it all day). The only thing I did was to disable the wi-fi in Windows 10, because of our dns which likes to take our Wi-Fi adapter address rather than the ethernet connection. In the DNS the change is done and the IP matches the one in the console, 192.168.0.79. The machine is in the domain, everything fine and dandy except it isnt. What could be the reason and where can I start troubleshooting. Cheers