Exchange Server cross-forest mail migration case Sharing (ii)

In this section, let's discuss how to implement a query for free and busy information.

First, we need to establish a relationship between the two systems, the so-called Organization relationship. Second, the level of detail that can be queried for information is also related to the level of ad forest trust between them. If both sides of the ad exist or allow the establishment of two-way trust, then we can do PERUSERFB query more detailed free busy information. If only one-way trusts are allowed (for example, only the resource domain trusts the account domain) or there is no domain trust, then only ORGWIDEFB queries can be done with simple free busy information.

We need to run the command add-availabilityaddressspace, which adds availability Address space information to both systems, equivalent to the "Routing table". When we are in the Outlook client to query the free and busy information of a user of a different Exchange organization, Exchange reads the ad attribute of the TargetAddress object to query, and then matches the domain name information in it to get the target domain name of the object. The corresponding query is then initiated according to the previously set availability Address Space configuration.

So, how does our Exchange Server know the interface address of the Exchange server of the other system? This will use an Exchange-based Autodiscover service. To know what a autodiscover friend is, you can read the following document.

Https://technet.microsoft.com/en-us/library/bb124251%28v=exchg.150%29.aspx

Using Autodiscover to query the other side of the server, generally there are three methods, we hit analysis under the pros and cons.

1. Create and query DNS SVR records. However, this approach is not appropriate for Exchange 2007. For detailed reasons, please consult the following KB. In addition, by June 2015, we do not support the method of using DNS SRV if we do Office365 hybrid cloud mode.

http://technet.microsoft.com/en-us/library/bb125182%28EXCHG.80%29.aspx

2. Create and query the DNS records of the Autodiscover indicated in the targetaddress. Like Autodiscover.source.contoso.com, autodiscover.target.contoso.com. But this requires updating the SSL certificate, which means additional overhead and configuration work.

3. Use Export-autodiscoverconfig to create an SCP record for the other organization in AD. Then manually add the routing Domain Information "domain=xxx.contoso.com" to the keywords attribute. Exchange will then query the ad's SCP record directly to find the interface of the other, without relying on DNS, and without having to alter the existing SSL certificate.

The following is an introduction and resolution of the relevant steps.

1. In the target system, enter:

Set-availabilityconfig-orgwideaccount Freebusysvc-winos

The purpose of this command is to specify a service account for your system (such as Freebusysvc-winos)

2. In the target system, enter:

Add-availabilityaddressspace-forestname Source.contoso.com-accessmethod orgwidefb-credential (Get-Credential)

Attention:

A. Here source.contoso.com Replace the FQDN of your actual source forest

B. In addition, because we use a one-way ad trust in our example, we need to prepare a service account to allow the other person to access their resources. In the command get-credential will jump out of the box let us enter information, here need to enter the source system account and password (that is, Target\freebusysvc-contoso)

3. In the source system, enter:

Set-availabilityconfig-orgwideaccount Freebusysvc-contoso

The purpose of this command is to specify a service account for your system (such as Freebusysvc-contoso)

4. Enter in the source system

Add-availabilityaddressspace-forestname Target.contoso.com-accessmethod orgwidefb-credential (Get-Credential)

Attention:

A. Here target.contoso.com Replace the FQDN of your actual target forest

B. In addition, because we use a one-way ad trust in our example, we need to prepare a service account to allow the other person to access their resources. In the command get-credential will jump out of the box let us enter information, here need to enter the source system account and password (that is, Source\freebusysvc-winos)

The result of the final implementation is as follows. The red flagged William and Alex are the mailboxes of another Exchange system.

Finally, it may cause the query to fail because of the inconsistent schedule of the default free busy information query for Exchange 2007 and 2010/2013. The workaround is to modify the related configuration of IIS on the Exchange 2007 server so that the schedule on both sides are consistent. The steps are as follows:

• 1. Log into the Exchange Client Access Server (CAS)
• 2. Open Internet Information Services (IIS) Manager in Adminstrative Tools
• 3. Navigate to Sites > Default Web Site > EWS
• 4. Double-click Application Settings under the ASP .
• 5. Click Add in the Actions pane and create the following new application setting:
  • Name: maximumqueryintervaldays
  • Value:
• 6. Click OK to set the new value and close IIS Manager
• 7. Repeat for each Exchange-CAS

"Not yet adjourned"

Exchange Server cross-forest mail migration case Sharing (ii)