Verify that Mailbox Database Points to the FQDN of the CAS Server Array, if CAS is Used
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2010-08-20
The Microsoft Exchange Best Practices Analyzer Tool performs the following tasks:
Determines whether a CAS Array exists in the site
If a CAS Array exists, collects all databases that are hosted on servers in the site
Determines whether any databases point to an out-of-site CAS array
Determines whether any databases point directly at a CAS server instead of at an array
During the transition from standalone CAS servers to a CAS array, a mailbox database might continue to point to a specific CAS server instead of pointing to the FQDN of the array.
To resolve this issue, use the Set-mailboxdatabase cmdlet to change the RPCClientAccessServer attribute on the mailbox database to the name of the array.
Change the RPCClientAccessServer attribute on the mailbox database to the name of the array
Start Exchange Management Shell.
Type the following cmdlet, and then press ENTER:
set-mailboxdatabase –rpcclientaccessserver <DNS FQDN of the Array>.
For more information about the Set-mailboxdatabase cmdlet, see Set-MailboxDatabase.