my senior exchange dude configured 2007 and 2013, but I noticed that my 2007 users are unable to see 2013 users free busy.

the ews setting right now are:

EWS (Default Web Site)  200701   https://sillywebmail.mydomain.com/ews/exchange.asmx
EWS (Default Web Site)  200702   https://b-webmail.mydomain.com/ews/exchange....
EWS (Exchange Back End) 2013EXCH01
EWS (Default Web Site)  2013EXCH01 https://b-site1.mydomain.com/ews/exchange.asmx
EWS (Exchange Back End) 2013EXCH02
EWS (Exchange Back End) 2013EXCH03
EWS (Exchange Back End) 2013EXCH04
EWS (Default Web Site)  2013EXCH02 https://b-site1.mydomain.com/ews/exchange.asmx
EWS (Default Web Site)  2013EXCH03 https://b-site1.mydomain.com/ews/exchange.asmx
EWS (Default Web Site)  2013EXCH04 https://b-site1.mydomain.com/ews/exchange.asmx

if I put the url in my browser and the login my free/busy then works. I was thinking the authentication is set incorrectly?

also should the backend entries be populated?

and is there a good blog or something I can find to help me understand the virtual directories and authentication?

our dns internally and externally are different

• Edited by totalnet32 Wednesday, May 13, 2015 11:19 PM

Hi,

Basis on your post, I understand that user in Exchange 2007 cannot view the free\busy information for user place in Exchange 2013.
If I misunderstand your concern, please do not hesitate to let me know.

Do you means Exchange 2007 and Exchange 2013 within one single forest? If not, we need create federated trust and configure federated sharing between Exchange organizations. For your reference:
https://technet.microsoft.com/en-us/library/jj657473(v=exchg.150).aspx

If its single forest, please try open OWA to double confirm whether user can view the available information. Please refer to Availability service in Exchange 2013: https://technet.microsoft.com/en-us/library/bb232134(v=exchg.150).aspx
If it only occur in Outlook client, run Outlook and use Test E-mail AutoConfiguration tool to determine whether Outlook can connect to the Autodiscover service, meanwhile run Outlook.exe /cleanfreebusy switch.

Thanks