Jump to content

merckxist

Members
  • Posts

    9
  • Joined

  • Last visited

Reputation

0 Neutral

Profile Information

  • Location
    NorCal
  1. Scheduled scan ran on time for several days after reboot. Next tried making a slight change to the start time using settings panel but no reboot. Scheduled scan no longer ran. After a couple of days of no scanning, I rebooted without modifying any settings. Within a few minutes of the system coming back up, the scheduled scan started, perhaps because there was some recognition that the last scheduled scan was missed by more than the number of hours in the advanced scan settings. Hard to be certain because the feature is so poorly documented in the user guide. After the scan finished, the dashboard showed the next scheduled scan was 24 hours later from the system (re)boot time, rather than the configured time in settings. However, the next day's scan did run at the settings time rather than than the time originally shown in the dashboard. Now the dashboard and the settings time are now in sync. This feature seems to be both poorly coded and documented. No documentation that any scheduled scan change requires a reboot to work; and no warning shows up on the dashboard settings when a change is actually made. And why would anyone who's used Windows Task Scheduler think that was SOP since Windows itself does not require a reboot for making scheduled task changes. I haven't bothered with the 3.05 patch since the release notes did not include any mention of fixes for the scheduled task known issues in the 3.04 release.
  2. Thanks for additional info. I thought I'd try one idea at a time, so I started with a reboot. Next scheduled scan ran on time,so that's progress! I'll let that go a day or two just to be sure, then try making some changes. It would be nice if the product needs to have a reboot to make features work correctly, that the installer would note that fact when it terminates.
  3. @YE3YF, you are not alone. Same issue for me, so I'm interested in how your test went. I've had a scan scheduled for 2 days and it still hasn't run. This "feature" has been problematic since the 1.75 days. At least back then there was a command line interface you could call from a windows bat file and get a scan to run reliably via the windows scheduler, The developers took out the command line with v2 and they haven't gotten their internal scheduler code to work "as documented" since then. Right now, the known problems list includes a point about the scheduler GUI not being completely effective in changing date/time, but there seems to be more to it than that since the date/time fields look ok, but my scans still don't happen.
  4. You should be able to turn this off with FF site permissions. When you are connected to the site, there should be an "i"nformation icon at the left side of the address bar. If you click that it brings up a box with the site name and a permissions setting for "receive notifications". You get a drop-down with several choices like "block", "always ask" and "allow". Just pick your preference. New feature with FF 44. I didn't see this suggestion in the previous solution.
  5. Would this activity impact the ability to get updates to the database at the client side? The last couple of days I've been getting errors connecting to database server with "bad md5 or size" comments in the daily log file. Or is this a separate issue for its own topic?
  6. Short response: Thanks! Long (TLDR) response: Ahh, the old "known issue, eventual fix solution". Must be on the "newbie dev" calendar where low priority issues go to die. Hey, who wants to solve an issue that doesn't get one promoted to the high priority Malware-solution dev group. Unfortunately, the old command-line options from v 1.75 also ended up there (eventual fix, but don't hold your breath) or I'd still be using the script I wrote to run scheduled tasks that used the OS scheduler to run at a consistent, set it and forget it, time. And its not just this vendor. My anti-virus developer has the same kind of priorities. They have a known (for many versions) issue with displaying "status" pop-ups after (coincidentally?) a scheduled scan runs even though the custom settings are set NOT to open results after the scan finishes but it happens anyway. So the customer is left with a faith-based decision of should I go (how can I trust their malware defense if they can't get scheduling to work accurately) or should I stay (since they apparently focus on the malware and let the non-malware bugs go on indefinitely).
  7. I have two scheduled tasks, a scan and an update check, that had their start times modified to an hour later in the day after the computer clock was auto adjusted for Daylight Saving Time. Any one else notice this behavior?
  8. Thanks for the quick reply on a non-critical post! Hope you weren't working late, maybe just on an off shift. I'm a retired sys admin so I'm not responsible for a business/enterprise evironment anymore, just used to setting up my own systems that way. Parsing out the log file will refresh my perl script skills, so that's a good tradeoff.
  9. I found the 7xx exit codes for mbam internal errors in the FAQ, but would like to know if there is a list of codes for "/scan" operations with normal completion when malicious items are detected. I would like to run mbam in scheduled scripts that post basic pass/fail results that tell the admin to go look at the logs next time he/she checks the system and finds a fail (detected items) condition. Or will I need the script to parse the logs to look for "detections"?
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.