After introducting Exchange 2013 to an Exchange 2010 environment: "Your mailbox appears to be unavailable" in OWA.

Hello,

I am in the process of migrating from Exchange 2010 to Exchange 2013.  On Wednesday I installed Exchange 2013 on two separate new servers on the network (One CAS and one Mailbox).

I did not see any issues on client workstations, so I did not run the following command to set the CAS:
Set-ClientAccessServer -Identity <Exchange 2013 CAS Name> -AutoDiscoverServiceInternalURI https://webmail.domain.com/autodiscover/autodiscover.xml

However, following a weekend reboot of all servers, we are seeing the following symptoms:
1. Users are prompted for credentials when they launch Outlook.  They then have to enter their Active Directory credentials in order to access Outlook.

2. More importantly, OWA does not seem to be working anymore.  When users try to login, they receive the following error:
Your mailbox appears to be unavailable.  Try to access it again in 10 seconds.  If you see this error again, contact your helpdesk.

Experts - I would imagine this is related.  Should I run the command?  If yes, should it be run on the new Exchange servers (2013) or the old ones (2010)?

Alternately, could this be unrelated and what should I do?  Any suggestions would be greatly welcome.

Regards,
Real-Time
Your-mailbox-appears-to-be-unavailab.JPG
realtimerAsked:
Who is Participating?
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.

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Can you see any error  in Exchange2013 server

Did you set URLs in Exchange2013?

Did you try moving a single mailbox and try?

Do you have a CAS Array before in Exchange2010?
0
realtimerAuthor Commented:
Thanks.  Due to the urgency, I had to proceed with a phone support case with Microsoft.  Turns out that this was not an issue with the upgrade path.

Following Windows Updates, the CAS was no longer able to ping the MBX server by host name.  This was addressed by temporarily adding a record in the hosts file.  All is good now.

Thank you!!
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
realtimerAuthor Commented:
Issue addressed with Microsoft phone support.
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
Outlook

From novice to tech pro — start learning today.