Exchange 2010 client configuration is simple when dealing with a single site
or when every site in the directory contains and Exchange 2010 Client Access
Server (CAS). However, things get a little more complicated when dealing with
multisite environments.
When a client is placed into an active directory site that does not contain a
CAS, a query is sent to the directory looking for an available client access
server that is closest to the client computer. This server then returns URLs and
configuration information of a CAS that is closest to the user’s mailbox. This
built in process does not always guarantee communications that are optimized for
your particular environment. To help streamline this process, use the following
PowerShell command to specify which Sites will cover sites that do not contain
Exchange Servers.
Set-ClientAccessServer -Identity CASServerName -AutoDiscoverSiteScope
“Sitename-1″, “SiteName-2″
This command will allow you better align communications in your environment
with your WAN. Don’t forget when running this command to include the desired
remotes sites and the site the CAS server is installed in.
Tweet or when every site in the directory contains and Exchange 2010 Client Access
Server (CAS). However, things get a little more complicated when dealing with
multisite environments.
When a client is placed into an active directory site that does not contain a
CAS, a query is sent to the directory looking for an available client access
server that is closest to the client computer. This server then returns URLs and
configuration information of a CAS that is closest to the user’s mailbox. This
built in process does not always guarantee communications that are optimized for
your particular environment. To help streamline this process, use the following
PowerShell command to specify which Sites will cover sites that do not contain
Exchange Servers.
Set-ClientAccessServer -Identity CASServerName -AutoDiscoverSiteScope
“Sitename-1″, “SiteName-2″
This command will allow you better align communications in your environment
with your WAN. Don’t forget when running this command to include the desired
remotes sites and the site the CAS server is installed in.