Using new computer, existing mailbox user Outlook 2010 Auto-configuration points to the Mailbox Server rather than CAS Array ?

Question

People,
I'm having a problem with the current AD user account & mailbox user where they cannot get the Outlook 2010 automatically configured to point into the CAS array ?
This is happening when the existing user get new computer replaced or login to the Terminal Server where their account never set before, it always points to the Mailbox Server instead of the Client Access Server array virtual name. 
The work around that I provided is typing the Client Access Array address and then specify Outlook.domain.com to match the Windows NLB name (and Get-ClientAccessArray result).
Single AD Domain forest
AD Site DataCenter contains:
Domain Controllers: PRODDC01-VM, PRODDC02-VM, PRODDC03-VM
Exchange Server 2010 SP3 - CAS&HT: PRODMAIL01-VM and PRODMAIL01-VM (Configured with WNLB as outlook.domain.com)
Exchange Server 2010 SP3 - Mailbox: PRODMAILBOX01-VM and PRODMAILBOX01-VM (no DAG is set)
Terminal Server (RDSH 2008 R2): PRODTS01-VM ... PRODTS60-VM (when user logged in to new TS, it got the same error).
AD Site HQ contains - This site has no issue:
Domain Controllers: HQDC01 and HQDC02
Workstations using Outlook 2010 and 2013
AD Site SiteOffice1 contains - This site has problem:
Domain Controllers: none but the majority of the workstations LOGONSERVER is pointing to PRODDC03-VM
Workstations using Outlook 2010 and 2013
All of the Exchange environment here is using Exchange Server 2010 SP3 for all server roles.
Any help would be greatly appreciated.
Thanks
/* Server Support Specialist */

Answer 1

Hi,
Yes, the RPCClientAccessServer should point to the CAS array. What's more, I would like to clarify the following things:
1. Run the Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri cmdlet to make sure that it displays the correct Uri.
2. Run the Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL to ensure that URL for EWS points to the CAS array.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Amy Wang
TechNet Community Support
Here's the result:
[PS] C:\>Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
AutoDiscoverServiceInternalUri : https://PRODMAIL02-VM.domain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceInternalUri : https://PRODMAIL01-VM.domain.com/Autodiscover/Autodiscover.xml
[PS] C:\>Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL
Identity : PRODMAIL01-VM\EWS (Default Web Site)
CertificateAuthentication :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
InternalNLBBypassUrl : https://PRODMAIL01-VM.domain.com/ews/exchange.asmx
InternalUrl : https://PRODMAIL01-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx
Identity : PRODMAIL02-VM\EWS (Default Web Site)
CertificateAuthentication :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
InternalNLBBypassUrl : https://PRODMAIL02-VM.domain.com/ews/exchange.asmx
InternalUrl : https://PRODMAIL02-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx
The IP address of email.domain.com and outlook.domain.com are the same IP address, this IP address is servec by WNLB.
/* Server Support Specialist */