Exchange 2013 mailbox migrations reporting wrong time / timezone

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
mcdonamwIONAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mcdonamwIONAuthor Commented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mcdonamwIONAuthor Commented:
Self-Answered
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.