Exchange 2010 to 2016 Migration

Hallo All,

I am carrying out a migration from Exchange 2010 Standard to Exchange 2016 Standard and all was going well until recently I noticed getting the error attached. Can anybody assist me with the same.

Thank you,
Screen-Shot-2017-03-10-at-14.44.43.jpg
LVL 3
Gurvinder BharyaDirectorAsked:
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.

systechadminConsultantCommented:
is this the error when you open EMS?
0
Gurvinder BharyaDirectorAuthor Commented:
Yes Gaurav. This is the error when EMS is opened.
0
systechadminConsultantCommented:
Please check the IIS, Default Backend Site, if the certificate is assigned to that or not.
Also make sure that you are opening EMS as administrator with domain account
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Gurvinder BharyaDirectorAuthor Commented:
Thanks Gaurav,

I have indeed done this and still experience the same issue. It tries to connect to the new server, but after receiving this error, it connects to the old server successfully. Seeing that I shall decommission the old server, I would like for the installation to be perfect.
0
systechadminConsultantCommented:
can you check the event logs on the server for any error?
0
Gurvinder BharyaDirectorAuthor Commented:
The common error that I am noticing that might be connected to Exchange Server is:

Inbound authentication failed with error UnexpectedExchangeAuthBlobCheckForClockSkew for Receive connector Default Mailbox Delivery ABCExc. The authentication mechanism is ExchangeAuth.
0
aravind ancheWindows/Vmware Commented:
0
Gurvinder BharyaDirectorAuthor Commented:
I managed to figure out the issue. A difference in time between the two servers was causing the issue. Once I had corrected the issue, all worked well. Would be nice if microsoft provided a better error reporting on the same.
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
Gurvinder BharyaDirectorAuthor Commented:
I manage to resolve the issue on my side. Neither of the comments was as close to my solution therefore I shall not award any points to anyone else.
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.