Exchange 2013 mailbox migrations reporting wrong time / timezone

mcdonamwION
mcdonamwION used Ask the Experts™
on
Out of nowhere my Exchange 2013 environment has changed something which is now causing migration batches to report in a different timezone.  By that I mean if I start a batch it will record that it started 4 hours from now  (I'm in Eastern timezone).  Further if I do a get-migrationbatch | fl *, every property related to a date/time all show the same as their UTC counterparts.  See example below.

It's as if Exchange is configured to report everything in UTC/GMT time but the local servers all report the correct time in the Eastern timezone.  My dev exchange environment does not do this.  Any idea what could cause this and how to change it back?

Example:

CreationDateTime       : 3/27/2017 2:05:44 PM          <------Really 10:05:44 am Eastern, when it was kicked off.
CreationDateTimeUTC    : 3/27/2017 2:05:44 PM
StartDateTime          : 3/27/2017 2:05:44 PM
StartDateTimeUTC       : 3/27/2017 2:05:44 PM
InitialSyncDateTime    : 3/27/2017 2:33:33 PM
InitialSyncDateTimeUTC : 3/27/2017 2:33:33 PM
LastSyncedDateTime     : 3/27/2017 2:31:37 PM
LastSyncedDateTimeUTC  : 3/27/2017 2:31:37 PM
FinalizedDateTime      : 3/27/2017 2:05:44 PM
FinalizedDateTimeUTC   : 3/27/2017 2:05:44 PM

This is my dev environment:

CreationDateTime       : 3/27/2017 10:36:24 AM
CreationDateTimeUTC    : 3/27/2017 2:36:24 PM
StartDateTime          : 3/27/2017 10:36:24 AM
StartDateTimeUTC       : 3/27/2017 2:36:24 PM
InitialSyncDateTime    : 3/27/2017 10:41:40 AM
InitialSyncDateTimeUTC : 3/27/2017 2:41:40 PM
LastSyncedDateTime     : 3/27/2017 10:39:33 AM
LastSyncedDateTimeUTC  : 3/27/2017 2:39:33 PM
FinalizedDateTime      : 3/27/2017 10:36:24 AM
FinalizedDateTimeUTC   : 3/27/2017 2:36:24 PM
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Through my own testing I have found that the regional settings of the mailbox performing the migration is what drives how Exchange records the timestamps.  Setting up a new account (with no mailbox, thus no regional settings are available)  and performing a migration causes the timestamps to report in UTC format.  My colleague uses the same configuration whereas I use an account with a mailbox and my regional settings are set to Eastern timezone.

I find it odd that Exchange would take that into consideration and not just the timezone of the local machine performing the operation.  I also  wonder if this is the same in Exchange 2016.

At any rate question has been self answered.

Author

Commented:
Self-Answered

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial