I'm not aware of any issues with Henrik's series in Exchange 2013, but I think 
that federation is a much easier way to get where you want to be.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kelsey, John
Sent: Tuesday, January 17, 2017 8:32 AM
To: '[email protected]'
Subject: [NTSysADM] Cross Forest Exchange Free-Busy Info

Exchange 2007 server running in domain abc.org.
Brand spanking new Exchange 2013 servers running in domain xyz.org
2 way trust between the domains.

Trying to get the free-busy info to work across the environment, but its only 
working in 1 direction.

All user accounts are in domain abc.org
Users with mailboxes on the 2007 CAN see the calendar free/busy info of users 
with mailboxes on the 2013 server
Users with mailboxes on the 2013 server CANNOT see the calendar free/busy info 
of users on the 2007 server (no free/busy information could be retrieved)

We tried making this change to the web.config file
http://www.msexchange.org/articles-tutorials/exchange-server-2010/migration-deployment/deep-dive-into-rich-coexistence-between-exchange-forests-part9.html

However once we did that, our Cisco Unity connection account broke and several 
web mail users reported they could no longer send email so we had to back this 
change out.

Is there something that needs done with Autodiscover to make this work 
correctly or are we missing some other type of configuration?

Thanks all!


***************************************
John C. Kelsey
Penn Highlands Healthcare
*:  814.375.3073
*  :   814.375.4005
*:   [email protected]<mailto:[email protected]>
***************************************
[PHH ESig Logo 150dpi]


This email and any attached files are sensitive in nature and intended solely 
for the intended recipient(s). If you are not the named recipient you should 
not read, distribute, copy or alter this email. Any views or opinions expressed 
in this email are those of the author and do not represent those of Penn 
Highlands Healthcare or its affiliates.. Warning: Although precautions have 
been taken to make sure no viruses are present in this email, the company 
cannot accept responsibility for any loss or damage that arise from the use of 
this email or attachments.

Reply via email to