Endpoint Protection

Hi,
I have SEPM installed on a Windows 2008 Server R2.  The Symantec version is 11.0.6005.562.  I have a scheduled report configured to email me supposedly at 6:30am every morning but when I configure it and I am done it shows that the report is scheduled to run everyday and below that it says that the report has never run.  Great.  But then two minutes later I receive the scheduled report by email and then the scheduled report details shows it is now supposed to run at whatever time it is when it sent the report.  I go into edit the report and the scheduled time shows the correct time that I really want the report to run at.

I saw a kb article that said that RU6 was supposed to fix this problem but it obviously didn't since I am on Ru6a.

Any ideas?

seems like its fixed
please delete the report and create a new once and check

Symantec Endpoint Protection Manager Scheduled Reports do not consistently run as scheduled
Fix ID: 1711164
Symptom: Symantec Endpoint Protection Manager Scheduled Reports are set to run hourly, however the reports run sporadically.
Solution: Updated to PHP 5.3.1 to resolve this issue

Dear Rafeeq.
Having to recreate the report is an unproductive use of my time. I do not get paid to recreate reports. I've got 50+ scheduled reports going out to different recipients.

Not fun!

This fix should be applied retro-actively onto all reports

On a fresh install using 11.0.6 MP1, the first and only scheduled report created does not run at all.

So I agree, this issue doesn't seem to be fixed.  That or I'm completely missing something on how to create a report.
I used this as a resource, along with common sense.
Link:  http://service1.symantec.com/support/ent-security.nsf/docid/2009101503441148

I've had to re-create some reports as well. Yep, not productive but I need the reports.

please delete the report and create a new once.

All reports have been deleted and recreated.  Still no change.

Not sure if this will help anyone... but I found a solution for my issue.

I had to create a scheduled job using the built-in filter, not a custom filter.  After that, any job I created using the built-in or custom filters worked perfectly.

I went one step furthur since this was a new install, I removed all custom filters and re-created them after testing an hourly scheduled job using the built-in filter.