Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEPM - use local time!

Created: 26 May 2009 | 7 comments
RickJDS's picture
4 Agree
5 Disagree
-1 9 Votes
Login to vote

Please change all reporting, alerts, logs, etc to use the server's local time when an event occurs and not GMT.

Comments

mon_raralio's picture
26
May
2009
1 Vote +1
Login to vote

.

I guess they did that to avoid additional computations, especially for companies using multiple timezones.

“Your most unhappy customers are your greatest source of learning.”

Ghe21's picture
12
Jun
2009
1 Vote +1
Login to vote

hate it if we always

hate it if we always convert.. GMT...

mon_raralio's picture
14
Jun
2009
1 Vote +1
Login to vote

We already tried fooling the

We already tried fooling the server into thinking that it was in GMT by setting the Windows time to +0. But that screwed up the dates on some clients. We were using multiple time zones.

“Your most unhappy customers are your greatest source of learning.”

Nel Ramos's picture
18
Jun
2009
1 Vote +1
Login to vote

better GMT... at least

better GMT... at least synchronized time is attain...

Nel Ramos

she_esteban's picture
18
Jun
2009
0 Votes 0
Login to vote

ITs better to use GMT so that

ITs better to use GMT so that it would be the same timezones.

mon_raralio's picture
20
Jun
2009
0 Votes 0
Login to vote

Why not both?

I'd rather have the local time and have GMT as an option.
Local time for companies whose entire network are in a single timezone. No point in using GMT there.
And then GMT for companies with networks on multiple timezones. But, it would be a little harder or time consuming making conversions everytime you set a timed policy.

“Your most unhappy customers are your greatest source of learning.”

Jobert's picture
21
Jun
2009
0 Votes 0
Login to vote

better have the SEPM

better have the SEPM constant.. to minimize errors please..
thanks