Exchange 2013 outlook connection

Hi Experts,

I'm having an issue where my clients can connect to Exchange 2013 from Outlook 2010, however they frequently get a credentials box asking for Username and Password.

I inherited a SBS2011 server which we have outgrown. It came with Exchange 2010. I wanted to upgrade to Exchange 2013 on a dedicated virtual server 2012. I hired a group who assisted with the migration but now my clients are still having some connectivity issues. Autodiscover seems to work and I got a new Exchange SSL but the clients still have issues with Outlook asking for their username and password as well as get a certificate error having the old domain name in the message. Shared schedules do not seem to work properly either. I have tried recreating the user account in Outlook but that didn't do it, although it did discover the settings and connect to the server. OWA works fine.

I believe the issue is that I need to insert the new certificate into the Autodiscover settings or add it to the clients manually, neither of which I know how to do.

I also want to shut down Exchange 2010 on the SBS but keep the rest of the services running until I have time and resources to move everything else. Will just disabling the Exchange services work?

Rob HoffmanAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
Almost certainly the problem is with the SBS 2011 server being in place.
Shutting down the services on its own is not enough - you need to actually remove the server completely.

What is probably happening is that the clients are hitting both servers for some Autodiscover processes, in effect an Autodiscover "war" between the two servers.

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

I expect the results will be different. Change them so they are the same (both pointing to Exchange 2013) and you should see most of the errors go away.


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
Rob HoffmanAuthor Commented:
Hi Simon,

Thank you for the quick reply. I had not thought of that issue.

I apologize, but I didn't follow what you mean by:
get-clientaccessserver | select identity, autodiscoverserviceinternaluri

Could you give further details?

Hey Rob check out this technet page  it provides some additional details on what Simon was directing you to. That command (if you replace the last with your autodiscover URL) will provide you the details of what your outlook clients are seeing when they autodiscover.
Rob HoffmanAuthor Commented:
Great, Thanks. I'll read up on it.
Rob HoffmanAuthor Commented:
It does look to be the Autodiscover issue with the SBS2011 box. There are some tips to disable the service on the SBS and it should be able to co-exist with the new Exchange server.
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

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.