Outlook Wont Connect to replacement Exchange Server

Experts,

I'm not sure what i'm missing here, but we changed over to a replacement exchange server. For some reason, outlook is trying to resolve and connect to the old server, even though the mailboxes, and the roles are all configured on the new one.  Everything else seems to be OK.  Mail is moving, ActiveSync is working, but Outlook wont connect to Exchange.  What am I missing here?

Thanks!
cocosysengAsked:
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.

Adam FarageEnterprise ArchCommented:
Internal or External? I take it is most likely internal..

Make sure the SCP (Service Connection Point) for AutoDiscover is pointed to either the replacement CAS, or a namespace that points to the CAS (autodiscover.company.com, then have an A record in the forward lookup zone (DNS) that points to the CAS).  This is most likely the reason for this.

Here is how to view the SCP: http://theucguy.net/service-connection-point-scp-in/
0
cocosysengAuthor Commented:
OK, per that doc, there were a couple goofs in there.  Should I go ahead and make the corrections?
0
Adam FarageEnterprise ArchCommented:
Which goofs?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

cocosysengAuthor Commented:
Well for the binding, it only had https://servername.local instead of https://servername.domain.local.  And the keyword attrribute had a bunch of numbers in there, instead of the site=default first site key.
0
Adam FarageEnterprise ArchCommented:
The SCP you can fix easily... If there is a single server in the environment, just change it to the proper server. Multiple servers is a tad bit different.

Before changing the keyword context, confirm the site name within AD sites and services..
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
cocosysengAuthor Commented:
That I did.  And I wound up calling Microsoft on it.  That was part of it, and also that the RPC was not assigned to the databases on the new server.  After running that command, the outlook clients fired right up.  So we're good! :)

Thank you for the help!  Much appreciated!!
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.

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.