Exchange 2007 Sp3 w/ru1. I have a development server that cannot be reached (intentionally) because of a firewall is preventing access. The problem is that clients are timing out trying to get to this server for free/busy information. I tried to change the AutoDiscoverSiteScope to $null but that didn’t seem to make a difference. The other CAS servers are registering an event 4002 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:443 Is there a way to prevent this server from being a candidate for the availability service so the clients don't time out trying to get to it?

The easiest way might be to simply set the AutoDiscoverServiceInternalUri of the server to a accessible CAS rather than to itself with the set-clientaccessserver command http://technet.microsoft.com/en-us/library/bb125157.aspx Set-ClientAccessServer This will at least point the clients to other CAS for autodiscover. You could also put it in a different AD site. (THere are also other ways that require manipulation of the config in AD, but probably not supported)

Andy, I forgot to mention, I do have the AutoDiscoverSericeInternalURi set to a reachable CAS server. I thought putting the AutoDiscoverSiteScope to $null would be the same as putting in a "different" AD site, but that didn't work either. Thank you.

Hello, You need to exclude all the web services on that server by setting the internal url for Null: Set-WebServicesVirtualDirectory -server xxx - InternalUrl $null Set-OABVirtualDirectory -server xxx - InternalUrl $null Thanks, Simon