How is it that some some SecureDoc Event Log entries seem to come from the future?
Issue:
We have (had) seen customers complaining that they're getting event log entries in from client machines in ALL Time Zones in North America.
They have some record time-stamp entries from months that haven't happened yet.
Cause:
The reason we get the timestamp from the client is that we need to know when the action took place on the client rather then when it was logged into SES database.
Resolution:
There's nothing to be done about this, though it's entirely possible the system clock/BIOS clock on some of those remote devices may have very strange dates running on them.