Problem
You’ve created your ClientAccessArray object in your Exchange 2010 organization with the cmdlets:
New-ClientAccessArray
http://technet.microsoft.com/en-us/library/dd351149(v=exchg.141).aspx
Set-ClientAccessArray
http://technet.microsoft.com/en-us/library/dd351174(v=exchg.141).aspx
… and confirmed that the object is created properly with:
Get-ClientAccessArray
… but noticed that the autodiscover configuration for the Microsoft Exchange server field in Outlook is still pointing to one of the CAS servers you have configured in a Windows NLB cluster:
Solution
The reason why you may see this behavior is because the RpcClientAccessServer setting for the mailbox database the user is connecting to hasn’t been changed to use the ClientAccessArray object. To determine this, use the following cmdlet:
Get-MailboxDatabase “Bermuda Mailbox Database” | FL Name,RpcClientAccessServer
To change this, use the following cmdlet:
Set-MailboxDatabase “Bermuda Mailbox Database” -RpcClientAccessServer casarray.domain.com
Once this property of the mailbox database has been set properly, Outlook clients configured with autodiscover should now use the ClientAccessArray object:
Note that existing clients already configured prior to this change will not be updated.
One Response
Thanks for sharing such a great piece of information with us. Class 3 digital signature