Background - Ex2010 / 2 Datacenters / 1 DAG / 1 client site in a different region where users are accessing 2010 via the Internet (even though they have a local office where a server can be deployed)<o:p></o:p>
Planning to deploy 2013 to take advantage of forcing proxy option for OA/OWA/ActiveSync etc. due to network architecture/limitations in one region (read as internal corp network has much
better latency/bandwidth as opposed to
users connecting via Internet directly to the main datacenters)<o:p></o:p>
We have users in one region (CN) where we want to force users to use a local CAS (no mailbox servers there) and have that CAS proxy (on internal network) to the mailbox servers. We plan to do
this via 2013 cas and having them to proxy to 2010
mailbox servers and eventually proxy to 2013 mailbox servers.<o:p></o:p>
Questions:<o:p></o:p>
Can we deploy single namespace with a local cas server in the region - have smart dns or local hosts file in that region to point to the local region CAS server with no mailboxes / it will proxy to 2013/10 ?<o:p></o:p>
If we deploy region specific name space (ex. cn.infra.com) with no mailboxes in that region
and all mailboxes are in the main datacenter in a different region (and different AD Site and with a different name space like na.infra.com) / How can we force users to use that region specific name space with no mailbox servers
in that AD site? / Is there any way we can force name space based on their user attributes as opposed to autodiscover doing the <GUID>@infra.com logic ?<o:p></o:p>
TIA
Prakash