How to solve this Exchange 2010 issue?
The is using a MS Exchange Server 2010 Organisation. There are altogether 5 Exch servers, located in 2 different countries (separate ad sites).
There are 4 exch servers located at site A, and only 1 at located Site B. Please see the roles assigned:
aexch1 - hub, MB
aexch2 - CAS
aexch3 - hub, MB
aexch4 - CAS
bexch1 - cas, hub, mb
Both aexch2 and 4 formed the client Access Array using MS NLB, with fqdn - external.abc.com; Although bexch1 also holds the cas role, it didn't form the CAS array due to dissimilar in site. Its fqdn is - externalb.abc.com. As you may aware, both fqdn IPs are in the entirely different public IP range. There are DAGs formed among aexch1 and 3, and also aexch1, 3 , and bexch1.
Recently, an active DB was allocated to bexch1 (DAG between aexch1, 3 , and bexch1). In the past, this db always allocated to either aexch1 or 3. Now, user with mailbox located in this DB can't access external.abc.com any more for OWA, mobile, etc. But, if they access externalb.abc.com, owa, mobile, works as per normal. What should be done to resolve the problem? form CAS array not possible, right. I heard about the "rpcclientaccessserver" settings in set-mailboxdatabase, will that work for different site CAS server?
Thanks in advance.
There are 4 exch servers located at site A, and only 1 at located Site B. Please see the roles assigned:
aexch1 - hub, MB
aexch2 - CAS
aexch3 - hub, MB
aexch4 - CAS
bexch1 - cas, hub, mb
Both aexch2 and 4 formed the client Access Array using MS NLB, with fqdn - external.abc.com; Although bexch1 also holds the cas role, it didn't form the CAS array due to dissimilar in site. Its fqdn is - externalb.abc.com. As you may aware, both fqdn IPs are in the entirely different public IP range. There are DAGs formed among aexch1 and 3, and also aexch1, 3 , and bexch1.
Recently, an active DB was allocated to bexch1 (DAG between aexch1, 3 , and bexch1). In the past, this db always allocated to either aexch1 or 3. Now, user with mailbox located in this DB can't access external.abc.com any more for OWA, mobile, etc. But, if they access externalb.abc.com, owa, mobile, works as per normal. What should be done to resolve the problem? form CAS array not possible, right. I heard about the "rpcclientaccessserver" settings in set-mailboxdatabase, will that work for different site CAS server?
Thanks in advance.
Keep in mind that if there are already DBs in the second site, the CAS Array Object may not apply (see the article I reference in my last post). It describes the symptom. Now this is all for Outlook.
For OWA and ActiveSync you need to have a look at your External and Internal virtual directories
Download: https://gallery.technet.microsoft.com/scriptcenter/Exchange-Virtual-Directory-93839d75
Rename it to: get-virdirinfo.ps1
Run from Exchange PowerShell these two exact lines (notice the two periods - and create a scripts directory):
Please post results redacted.
For OWA and ActiveSync you need to have a look at your External and Internal virtual directories
Download: https://gallery.technet.microsoft.com/scriptcenter/Exchange-Virtual-Directory-93839d75
Rename it to: get-virdirinfo.ps1
Run from Exchange PowerShell these two exact lines (notice the two periods - and create a scripts directory):
. .\get-virdirinfo.ps1
get-virdirinfo -filepath c:\scriptsPlease post results redacted.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi all,
Let me have more time to read through all of the suggested articles first.
Let me have more time to read through all of the suggested articles first.
Any updates?
ASKER
Thanks for expert - K B, in providing a detailed suggestions. Finally, I got the issue resolved.
This is the defacto standard article on CAS Arrays:
https://blogs.technet.microsoft.com/exchange/2012/03/23/demystifying-the-cas-array-object-part-1/
https://blogs.technet.microsoft.com/exchange/2012/03/28/demystifying-the-cas-array-object-part-2/
Side Note: Neither of the CAS Array Objects should be resolvable by Public DNS - Only internal DNS.