2007 Exchange server cannot see 2010 Exchange 2010 free/busy

Posted on 2014-09-09
Medium Priority
Last Modified: 2015-05-07
Single forest multiple domains.   We are in co-existence with Exchange 2003, 2007, and 2010.  2003 and 2010 share a domain and 2007 is in its own domain.  
2010 users can see each other's free/busy as well as 2003 users seeing 2010 free/busy and 2010 sees 2003 free/busy.  However, a 2007 user cannot see a 2010 users free/busy, but the 2007 user can see the 2003 users free/busy.  I know that's extremely convoluted.
Internal EWS URL's are set to the respective external URL's (no FQDN's).  The bypassURL is showing the FQDN.    External EWS URL on 2007 is blank.  External URL on 2010 is the same as the internal.  
Thanks for any help.

Desktop>Get-WebServicesVirtualDirectory | Select name, *url* | fl

Name                 : EWS (Default Web Site)
InternalNLBBypassUrl : https://sv07tumail.xxxxx.local/ews/exchange.asmx
InternalUrl          : https://outlook.xxxxx.com/ews/exchange.asmx
ExternalUrl          :

Name                 : EWS (Default Web Site)
InternalNLBBypassUrl : https://sv18tumail.xxx.local/ews/exchange.asmx
InternalUrl          : https://test.xxx.com/EWS/Exchange.asmx
ExternalUrl          : https://test.xxx.com/EWS/Exchange.asmx
Question by:bfpnaeechange
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
LVL 63

Accepted Solution

Simon Butler (Sembee) earned 1500 total points
ID: 40312407
With 2003 involved you need to have public folders on the other servers and replicate the system folders - including free/busy. Therefore the first thing I would do is check that is setup correctly.
Does the host name on the internal bypass URL appear on the SSL certificate on the server itself? Is the certificate trusted by the clients?


Author Comment

ID: 40312430
Thanks for the comment.  The internal bypass URL is not on the SSL cert since it's a .local.  The system folders are being replicated from 2003 to all the Exchange servers.   However, the issue is strictly with Exchange 2007 users seeing Exchange 2010 free/busy.

Author Comment

ID: 40312446
SV07 is Exchange 2007 and SV18 is Exchange 2010 in the above example.
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40312497
If the internal bypass URL is not on the SSL certificate, then Outlook is going to have problems connecting to it, because it cannot create the trust.
You either need to use a URL that is on the certificate, or stop using SSL for that URL.


Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In-place Upgrading Dirsync to Azure AD Connect
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question