In this article lets have a look at steps to configure cross-forest availability between two exchange forests
By using the Add-AvailabilityAddressSpace commandlet which has been introduced from Exchange 2013 we would be able to share the exchange free busy data between 2 forests.
We need to have a trust relationship between the source forest and target forest to execute this command. Only then the below command will be successful.
If a trust relationship exists between the two forests, run the following commands.
In our example lets think of sharing the freebusy information between domain Exchangequery.com and toybox.com.
In Order to share the free busy info between these 2 forests we need to perform the below steps
In the source forest perform the following tasks : (ExchangeQuery.com)
Add-AvailabilityAddressSpace -ForestName toybox.com -AccessMethod PerUserFB -UseServiceAccount $true
The above command adds the target domain’s address space in source domain to share the free busy information in a secured way.
Below types of access methods can be used.
PerUserFB – used to access the FB data in All Exchange Servers group.
OrgWideFB – used to access the FB data in specific group in the target forest.
InternalProxy – used to proxy the request in the latest version of exchange in the site.
The type of access method can be selected according to our requirement.
Now we need to run the below command in the target domain ( Toybox.com)
Get-Exchangeserver | Add-AdPermission -AccessRights ExtendedRight -ExtendedRights “ms-exch-epi-token-serialization” -User “ExchangeQuery.com\Exchange Servers”
The above command will add required permission for source domain on the target domain Exchange Servers to access the free busy information.
In a trust relationship scenario, run this command in the target forest toybox to export the SCP from the target forest to the source forest :
Export-AutodiscoverConfig –DomainController “LocalForestDomainController” -TargetForestDomainController “(toybox.com)” -TargetForestCredential (Get-Credential) -MultipleExchangeDeployments $true
Type (Toybox\Administrator) password when prompted.
Now we need to perform the same tasks in the target forest toybox.com to share the exchangequery.com address space for sharing the freebusy data.
In the target forest perform the following tasks : (Toybox.com)
Add-AvailabilityAddressSpace -ForestName exchangequery.com – AccessMethod PerUserFB -UseServiceAccount $true
Run the below command in the Source domain ( ExchangeQuery.com)
Get-ClientAccessServer | Add-AdPermission -AccessRights ExtendedRight -ExtendedRights “ms-exch-epi-token-serialization” -User “Toybox.com\Exchange Servers”
Now run this command in the forest Exchangequery.com to export the SCP from the target forest to the source forest:
Export-AutodiscoverConfig –DomainController “LocalForestDomainController” -TargetForestDomainController “exchangequery.com” -TargetForestCredential (Get-Credential) -MultipleExchangeDeployments $true
Type Exchangequery.com\Administrator password when prompted.
Imp Note : This command Add-AvailabilityAddressSpace is available and applicable only for Exchange 2013 servers and Office 365.
The required trust relationship, contacts and address space between the 2 different organizations must be already created and replicated between them.Only then free busy information will be working.
Reference – http://technet.microsoft.com/en-us/library/bb124122(v=exchg.150).aspx
Thanks
Sathish Veerapandian
MVP – Exchange Server
Tagged: Exchange Servers, source domain, trust relationship
Good way of telling, and pleasant paragraph to take
facts about my presentation subject, which i
am going to deliver in college.
LikeLike
I’ve been exploring for a little for any high quality articles or weblog posts in this kind of space .
Exploring in Yahoo I ultimately stumbled upon this website.
Studying this info So i’m satisfied to exhibit that I’ve an incredibly good uncanny feeling I came upon just what I
needed. I most undoubtedly will make sure to do not omit this web site and give it a look on a constant basis.
LikeLike
Thanks for your comments and you are welcome 🙂
LikeLike
Thanks for your comments 🙂
LikeLike
Hi Sathish, is it possible this can be achieved between Exchange 2013 Source and Exchange 2010 Destination/target ? As I have a scenario to carry out migration. Any help or suggestion will be useful,
LikeLike
Hi James,
Unfortunately it will not allow to migrate from higher version to lower version. But regarding sharing the address Space not sure it will work or not. Mostly it will not work on the destination in your case.
LikeLike
hi:
===================================================
Now run this command in the forest Exchangequery.com to export the SCP from the target forest to the source forest:
Export-AutodiscoverConfig –DomainController “LocalForestDomainController” -TargetForestDomainController “exchangequery.com” -TargetForestCredential (Get-Credential) -MultipleExchangeDeployments $true
====================================================
maybe:
Now run this command in the forest Exchangequery.com to export the SCP from the target forest to the source forest:
Export-AutodiscoverConfig –DomainController “(exchangequery.com)DomainController” -TargetForestDomainController “(toybox.com)DomainController” -TargetForestCredential (Get-Credential) -MultipleExchangeDeployments $true
Here : get-Credential: toybox.com(TargetForest)’s administrator
LikeLike