When ever we want to share our Free Busy information with other organization we go for federation and it requires the assistance of Microsoft Federation Gateway server to create a federation trust between the two organizations. This is a pretty straight forward activity when both organizations are using different SMTP Namespace and this will not help us during the period of migration when we acquire another company and share the same SMTP Namespace.
Found this latest post from Exchange MVP Jeff Guillet on his TheEXPTA blog over this topic, where he clearly explains how we can accomplish this task of sharing the free/busy information without using federated delegation using the Add-AvailabilityAddressSpace cmdlet.
This Article is excellent and it clearly describes the difference between Federated delegation and the usage of Add-AvailabilityAddressSpace cmdlet and the steps that are required to be performed in both the organizations to get this feature established successfully.
How to Share Free/Busy Information Without Using Federated Delegation
Read the blog post here : http://www.expta.com/2013/08/how-to-share-freebusy-information.html
Found this latest post from Exchange MVP Jeff Guillet on his TheEXPTA blog over this topic, where he clearly explains how we can accomplish this task of sharing the free/busy information without using federated delegation using the Add-AvailabilityAddressSpace cmdlet.
 |
This Article is excellent and it clearly describes the difference between Federated delegation and the usage of Add-AvailabilityAddressSpace cmdlet and the steps that are required to be performed in both the organizations to get this feature established successfully.
How to Share Free/Busy Information Without Using Federated Delegation
Read the blog post here : http://www.expta.com/2013/08/how-to-share-freebusy-information.html
No comments:
Post a Comment