pctech1380 0 Posted February 11, 2020 Share Posted February 11, 2020 Hello, We are using ESET Security Management Center (Server), Version 7.1 (7.1.503.0) ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0) and have ~250 machines reporting in. All machines are using the most current security product and the most current agent. Everything has been working well except for sometime around last few days of January, some machines are not reporting an up to date "Last Scan Time". So in my reporting, it is showing more and more each day more machines that have not been scanned in over 7 days. We have logged into the machines in the report that say they have not scanned in over 7 days, BUT per their policy, they have scanned successfully within 24hrs. We are seeing this report in the console show more machines each day that the report says are out of date, but in reality, they are not. Has anyone else had this issue? If so what did you do to resolve it? Link to comment Share on other sites More sharing options...
Most Valued Members ewong 8 Posted February 13, 2020 Most Valued Members Share Posted February 13, 2020 Hi @pctech1380, Yes, I also have encountered this though I haven't quite gotten to figuring out why it's happening. I think the logs might have something to say about it though. Edmund Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted February 13, 2020 ESET Staff Share Posted February 13, 2020 (edited) Unfortunately there is an issue that was reported some time ago. It might result in confusing reporting of last scan time, not only in ERA/ESMC but also in products itself. Issue is already resolved but I am not sure when fixed security products will be available. Edited February 13, 2020 by MartinK Link to comment Share on other sites More sharing options...
pctech1380 0 Posted February 13, 2020 Author Share Posted February 13, 2020 Thank you for the responses - so should I assume that this is just an anomaly with the last scan reporting times and that it will be fixed in some future update? Or is there an action I can take to correct this or something for me to check to ensure its fixed? Link to comment Share on other sites More sharing options...
Recommended Posts