Jump to content

John.From.VT

Members
  • Posts

    26
  • Joined

  • Last visited

About John.From.VT

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I see, so it's just downloaded and waiting. Thank you. Does linking a disabled auto update policy not mean they won't download at all? So I can better control when I'm ready to apply updates?
  2. I have had two domain controller servers automatically update ESET server products and be waiting for a restart (according to the ESET Protect Console). While that Windows Server 2019/2022 server is pending a reboot the domain trust seems to be unavailable. A reboot of the server fixes the problem. One updated yesterday and one today. Not sure if this is coincidence or not but the server needing the ESET update, when rebooted, corrects the issue. I'm still researching and scouring event logs. How do I disable automatic updates? I created an auto updates policy with auto updates disabled. I had put it at the bottom of applied policies for all computers (applied last). Should I instead put it as #1, applied first, before the enabled auto updates policy that ESET created automatically?
  3. So far so good running 10.1.2046. Unfortunately could not collect logs to send along. Time was of the essence to get people working again.
  4. Hey @Jasonleigh no kidding. We've had July updates installed since July 14th and are just seeing this issue this week. HIPS is on. Very interesting. So far today we've been installing 10.1.2046 and seeing the issue being resolved. But tomorrow will tell if the issue continues...
  5. Hi @Jens Holmkvist yes that's exactly what's happening, and so far uninstalling ESET has resolved the issue. I am still trying to get logs but even the ESET Log Collector is having trouble running. Interesting solution, on a PC I can test and dupe the issue with, Edge is currently on Version 115.0.1901.188 but the latest appears to be 117.0.2007.0. By running the update from ESET did you go to 10.1.2046 or are you talking about definition updates, etc?
  6. Thanks @Marcos I will attempt to get some logs if possible when the issue is occurring and will report back.
  7. Is anyone else having issues with PCs today simply dragging? W10 22H2 with the July Windows security updates installed 7/13/23. Trying to rule out a number of changes in our environment from the last week (BIOS updates, Dell Command Update installs, other automated application updates). We have some PCs with ESET email integration in Outlook, others without due to a prior issue which I feel has since been resolved. ESET is just another cog in the wheel so I'm reaching out to see if others are seeing similar issues today.
  8. Is this issue still occurring today? Everything was ok this morning but now about half of our managed computers are reporting functionality problems stating "The ESET Push Notification Service servers cannot be reached"
  9. Hi, thanks for the reply. I can't seem to edit the task name for new custom tasks either, I will probably bring this up when I submit a ticket for my scanning problems.
  10. I can't seem to edit the task name on any new scheduled task created through ESMC 7.1. It's grayed out. Anyone else seen this? Below image is what I see when I click Add. This is a minor gripe, but the reason I've come across it is because I have unexpected repeat on-demand scans running daily and/or hourly even when no schedule like this is set through ESMC or the client itself.
  11. An easy fix that worked for me is right-clicking the Detected Items folder that crashes Outlook and deleting it (then deleting the folder in Deleted Items as well). Not sure why a user or two had duplicates but this corrected it for them. Outlook 2016 MSI using cached Exchange mode and EES 7.2.2055
  12. So I disabled idle-state scanning and decided to also exclude the C:\Windows.old directory from scanning. Doing this stopped the creation of multi-GB log files throughout the day. The only logs created from the scheduled scans or external device scans are much more reasonably sized.
  13. Hmm. On the subject of logs, every idle-state scanning log is about a mile long and has issues in the C:\Windows.old directory (from the OS upgrade). I tried to export one of the logs to see how many lines of errors it has and the XML export ended up being 550MB. This is probably the issue. One line item from the log: C:\Windows.old\ProgramData\Microsoft\Windows\Containers\BaseImages\d8e0d7f1-c4b1-4fcd-a8cf-3900f85d9c2b\Files\Documents and Settings\All Users\Microsoft\Windows\Containers\BaseImages\19444ac6-99e9-4afc-84fc-efb454400ffb\BaseLayer\Files\ProgramData\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\Containers\BaseImages\19444ac6-99e9-4afc-84fc-efb454400ffb\BaseLayer\Files\Users\All Users\Application Data\Application Data\Microsoft\Windows\Containers\BaseImages\19444ac6-99e9-4afc-84fc-efb454400ffb\BaseLayer\Files\ProgramData\Application Data\Microsoft\Windows\Containers\BaseImages\19444ac6-99e9-4afc-84fc-efb454400ffb\BaseLayer\Files\ProgramData\Application Data\Microsoft\Windows\Containers\BaseImages\19444ac6-99e9-4afc-84fc-efb454400ffb\BaseLayer\Files\Windows\System32\LockScreenContent.dll - unable to open [4]
  14. I will throw the couple of computers with the large log files into a new policy where idle state scanning is disabled, see what happens, and report back. Thanks for the idea!
×
×
  • Create New...