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?
 
Adam FarageConnect With a Mentor Enterprise 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
 
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
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
Adam FarageEnterprise ArchCommented:
Which goofs?
0
 
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
 
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
All Courses

From novice to tech pro — start learning today.