Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEPM 12.1 Reporting shows incorrect time in Arizona during DST

Created: 24 Apr 2014 | 11 comments

We are located in Arizona, and all servers are set to the 'Arizona' timezone (GMT-7 No Daylight Saving Time).  When the rest of the US switched to DST, the timestamps on reports and notifications show an hour later than the current time, i.e. I receive a system notification at 9:30am that says something happened at 10:30am.

I have verified that prior to the DST change, the times were correct.  It appears that the report system ignores the 'observes DST' flag.  Timestamps in the log files and SEPM UI appear to be correct.

Does anyone have a fix for this?

 

 

Operating Systems:

Comments 11 CommentsJump to latest comment

Rafeeq's picture

 

Symantec Endpoint Protection Manager displays times that are off by one hour

http://www.symantec.com/business/support/index?pag...

.Brian's picture

What version? If 11.x, see here:

http://www.symantec.com/docs/TECH163143

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Tom Luna's picture

Sorry, thought I posted the version.  It's 12.1.4023.4080

Tom

.Brian's picture

This should've been fixed...did this happen again after an upgrade?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Tom Luna's picture

Upgraded to this version prior to DST start (2/24/14) from a prior 12.1 release.  The prior version also had this problem (I found an email from November 1, 2013 with incorrect time, and one from 11/4 that was correct).

Tom

Rafeeq's picture

You are on 12.1 , MP1 has the fix

Daylight Savings Time end date in a report results in inaccurate data
Fix ID: 2613156
Symptom: Specifying a Daylight Savings Time (DST) end date in a report results in start/end times that are offset by one hour. The specified reports, and all subsequent reports, are incorrect until the administrator logs off from SEPM.
Solution: A JavaScript function was modified to correctly support DST time.
 
http://www.symantec.com/business/support/index?page=content&id=TECH187656
Tom Luna's picture

Rafeeq,

Thanks for the response.  Will do the MP update, however the description of the fix doesn't really fit.  We see this issue on the System Event Notification emails generated when a server event occurs, as well as weekly scheduled reports emailed to admins.  The fix provided seems to be for the SEPM gui (ref to javascript, incorrect until user logs off).

Tom

AjinBabu's picture

Hello,

Are you using location awarenes on your enviornment?

Reagrds

Ajin

.Brian's picture

How does this relate to the DST issue?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Tom Luna's picture

No, but probably not relevant to this question.

Tom

Ayman Dais's picture

This issue does indeed exist. I spent over a week recently with Symantec Tech support attempting to address it and I was finally able to prove that the issue is a flaw in the product. It simply does not factor in that Arizona does not observe DST. So even though we are on GMT-7, the timestamps on all reports and alerts are 1 hour ahead of actual time because Arizona does not "spring forward". This issue is causing us a great deal of headache. I believe SEP Manager should use the time on the server it is running on rather than calculating GMT -7 or if not, update the software to not factor DST when the time zone is set to Arizona.