Endpoint Protection

Hi,

I have one client running SEP MR2 MP1 (backend MR4 MP1a).  My policy schedules a monthly scan.  The SEP GUI shows that the client knows that a scan occurs once a month.  However the GUI says the scan never ran (machine was initially imaged 4 months ago).  The client is communicating with SEPM (see green dot, entries in SEPM logs).  The SEPM logs show that only scan to ever run was a job kicked off by user 4 days ago.  Other machines are reporting scheduled scans.  I am looking for a suggestion for troubleshooting.  I couldn't find a relevant KB article or port in the forum.

Thanks in advance for your help.

Bob

I can't seem to find a solution to this problem either. It might be good to call and make a case for support. Just one question (although I don't think this applies in your case). Are your scans scheduled to take place on the 29, 30, or 31 days each month? There was a small problem with scans scheduled for these days, but in this problem the scans just took place on the 28th instead, so this is probably not your issue otherwise you would have seen a scan take place on the 28th. I will keep researching your problem.

Thanks,
Grant

Can you verify that the policies defined are assgined correctly to target computers?

 The scans took place on the 28th instead of 29/30 or 31 of that month? I have weekly scans scheduled, and one time or the other we have scanned during those days of the month. I have never seen any issues around it before. I need to check on this the next time this happend. Also, as Paul mentioned, we need to verify if the right policies were pushed to the right group. Maybe you should try pushing policies again and see if it works. I believe it should.

Hi everyone,

I confirmed that the machine was in the right group, and the gui shows that it received the policy to run the scheduled scan.  In my case, the scans are scheduled for the 10th.  Unfortunately all I have to work with is a screen shot showing that the month scan is visible in the GUI (machine is in the field).  I suggested trying a reinstall or an upgrade of the client before we spend too many cycles on this.  This problem was only reported on one client so far.  

Bob