Earlier today we identified an issue with one of the nodes in the ExchangeDefender admin cluster that was set with the wrong clock (wrong timezone configuration) and although the times were in sync across all servers, due to many scripts relying on unix timezone settings to calculate offsets and localized time, some users have experienced timestamps that were off by one hour (-1)
This issue was resolved at roughly 8:30 AM and while it did not pose a huge issue we felt it was important to note for any of you that may have noticed weird times in the admin logs.
Both comments and pings are currently closed.