I have followed several articles RE configuring CAS Array with Static Ports (SP1 registry fix also) as I am using a hardware load balancer; the setup looks ok and the ports are binding but I can't get internal users connected to the Cas Array DNS name - external users seem to resolve and work ok.
I'm guessing its an internal url setting? My internal urls for owa and ecp point to the servers FQDN as per
External users do not connect to a CAS Array, we may be mixing up some terminology here. CAS Array objects as defined through New-ClientAccessArray are used only for MAPI/RPC connections. You can have a pool of CAS servers balanced with WNLB or a HWLB for EAS/AutoD/OWA/EWS, but that does not by definition make it a CAS Array.
So what protocol are your internal users trying to use and having trouble with? That'll help define the troubleshooting path.
External users are connecting with Outlook Anywhere and do resolve the cas array fqdn; my issue internally is that the Outlook client is not connecting to the cas array - it connects to the cas server.
Steps I have used (in brief)
configured cas and mbox servers with static ports (55000 and 55001)
FQDN created for outlook.domain.com
new-clientaccessarray created and pointing to outlook.domain.com
Set-MailboxDatabase <name of DB> -RpcClientAccessServer “outlook.domain.com”
Is there any other setting required; i.e. do any of the cas internal urls need modified and point to outlook.domain.com (HWLB) OR should it just work based on the fact that Outlook points to outlook.domain.com which is the HWLB and the necessary ports being opened are forwarded?
Did you enable the static port for the Address Book Service?
To set a static port for the Exchange Address Book service after installing sp1, you need to create a new REG_SZ registry key named “RpcTcpPort” under: