• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 675
  • Last Modified:

Exchange 2013 , Exchange 2007 RPC over HTTP issues during coexistance

I am in the process of cutting over From exchange 2007 to exchange 2013.
I have configured all the exchange 2007 Virtual directories with the legacy namespace
I have set the external URL for activesync directory on 2007 to $Null.
Outlook anywhere is configured and enabled on 2007 and 2013.

on 2013 all Virtual directories are configured with the external name webmail.domain.com
on 2013 I have configured the 2003url to legacy.domain.com

for the outlook provider the server and EXPR are set to webmail.domain.com

when I move services to 2013 OWA, ActiveSync, work for both 2007 and 2013 users.
RPC and autodiscover update and work for all internal computers on the domain.

the issue I am having is for 2007 users that connect over RPC over HTTPS once services are moved to 2013.

users running both outlook 2007sp3 and outlook 2010 get error that cannot connect to server webmail.domain.com.  or exchange server is unavailable.

now ping responds correct, owa works on the machines just not RPC
  • 4
  • 3
1 Solution
Simon Butler (Sembee)ConsultantCommented:
"on 2013 I have configured the 2003url to legacy.domain.com"

You don't need that setting.

How is Outlook Anywhere configured on the Exchange 2007 server? External URL set? Which authentication setting is in place?

mndthegap1Author Commented:
thank you for the reply.

the Virtual directories for 2007

Owa  external: legacy.domain.com  internal: legacy.domain.com
oab   external: legacy.domain.com  internal: legacy.domain.com
WS    external: legacy.domain.com  internal: legacy.domain.com
AS     external:                                     internal: legacy.domain.com
UM    external: legacy.domain.com  internal: legacy.domain.com

Outlook Anywhere   external webmail.domain.com   ssl offloading:  OFF

virtal directories for 2013

owa  external: webmail.domain.com  internal: webmail.domain.com
oab   external: webmail.domain.com  internal: webmail.domain.com
WS    external: webmail.domain.com  internal: webmail.domain.com
AS     external:     webmail.domain.com internal: webmail.domain.com
UM    external: webmail.domain.com  internal: webmail.domain.com

outlook anywhere:  external: webmail.domain.com  internal: webmail.domain.com


2007 Cas server

external  Basic    Internal NTLM   IIS Basic,NTLM

2013 CAS server

external Basic  Internal NTLM  IIS  Basic, NTLM, Negotate
Simon Butler (Sembee)ConsultantCommented:
Are you aware of this article:

Change the Outlook Anywhere configuration on Exchange 2007 to NTLM only.

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

mndthegap1Author Commented:
THank you for the link. No I wasn't aware of that.  

I verified that IPV6 is disabled on the 2007 CAS server.
so that wont be it, so just switch to NTLM for all 3
Simon Butler (Sembee)ConsultantCommented:
If you make the switch, don't forget to run IISRESET so the change is written to IIS correctly.

mndthegap1Author Commented:
thanks again.

just to confirm,  I am change the client auth,  IIS auth ?  or am I just doing this on IIS ?
Simon Butler (Sembee)ConsultantCommented:
No, change it in Outlook Anywhere configuration within Exchange.

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.

Join & Write a Comment

Featured Post

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.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now