Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1182
  • Last Modified:

Exchange 2010 SP3 not showing any members in CAS array

Hi,
I have setup 4 Exchange 2010 SP3 servers all installed on Windows 2008 R2 Enterprise and all using the SP3 build of the software. the servers are configured with the following roles:

mail01 - CAS & HT
mail02 - CAS & HT
mail03 - mailbox with DAG
mail04 - mailbox with DAG

The DAG is configured and working fine, however, when I setup a client access array, the command runs fine but no members are shown as being a part of the array.

My setup was done in the following order:

1. Create a DNS Host A record for mail-cas pointing to the IP address that will be used for the NLB virtual IP.

2. Using the Exchange Powershell command, I created the CAS array,
New-ClientAccessArray -Name mail-cas -Fqdn "mail-cas.domain.local" -Site "Default-First-Site-Name"

3. Check the array with Get-ClientAccessArray
output shows:

Name          Site                         Fqdn                                     Members
----                ----                           ----                                        -------
mail-cas      Default-First-Sit...  mail-cas.domain.local        {}

When I complete the whole NLB setup and assign the mailbox databases to the CAS array, I am still unable to connect to the server via mail-cas.domain.local but I can ping the name and IP address.

I have rebooted and removed, reconfigured this setup several times now, and it continues to have no members in the CAS Array.

Are there any commands that will force the addition of the members in to the CAS Array?

Kind regards,
John V
0
BigBadJV
Asked:
BigBadJV
  • 8
  • 4
  • 2
7 Solutions
 
Alexander KireevIT ArchitectCommented:
0
 
BigBadJVAuthor Commented:
Hi,
I followed the example for the first link you posted to the letter. A screen shot of the NLB manager is attached.

I would have though that the part where I create the CAS would not depend on the NLB being setup, as you can create a single server CAS setup to allow for future proofing.

Regards,
John V
mail-cas.png
0
 
Alexander KireevIT ArchitectCommented:
Why you don't balance the 443 TCP port?

In text and screenshot you have different domaine name. Is it security measures?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
BigBadJVAuthor Commented:
Yes, I was taking out the domain name and using a generic one, just missed that one in the screen shot.

I have tried this setup using all ports allowed in the NLB setup, but that gave the same result.
0
 
Alexander KireevIT ArchitectCommented:
Did you try to readd Client Access Array?
Could you send a screenshot of command "Get-ClientAccessArray | fl"?
0
 
BigBadJVAuthor Commented:
Screen shot of the requested command attached. I have added and re-added the CAS array several times now.
CAS-ScreenShot.png
0
 
BigBadJVAuthor Commented:
Not sure if this is relevant, the Exchange 2010 install is in coexistence with an Exchange 2003 server, the install has been fine in all other ways, and I can move mailboxes in to the new Exchange 2010 servers. Mail flow is also working. Obviously I don't want to move users in to the new Exchange mail store until this issue is resolved.
0
 
Alexander KireevIT ArchitectCommented:
Try to use all ports for balancing (0-65535 Both Multiple) and then Re-add CAS Array.
The DNS works fine? Is fqdn resolve?
0
 
BigBadJVAuthor Commented:
Deleted the NLB config & the CAS array config, setup NLB using all ports and re-added the CAS Array to the mail server, same result no members added to the array.

Pings to the fqdn work as expected, DNS is fine.
0
 
Simon Butler (Sembee)ConsultantCommented:
I would start by removing the WNLB configuration to start with. WNLB is an unreliable piece of junk and is just getting in the way at this time. First rule with load balancing - test it without the load balancer to confirm full functionality.

Just setup the RPC CAS Array DNS entry to point directly to one of the CAS role holders.
Then setup the actual array and then configure the databases to use it. You should then be able to connect to the server using that configuration.
You may have to dismount and remount the databases for the configuration to be picked up.

Simon.
0
 
BigBadJVAuthor Commented:
Hi Simon,
Thanks for the advice, I will try your suggestion about setting the dns to one cas role holder and set the array to use it when I get on site in the morning. I have already tried setting up the cas array without the nlb setup, as I thought that it may be causing a problem. I have rebooted the cas servers several times but the cas servers refuse to show up as members of the cas array.

John.
0
 
Simon Butler (Sembee)ConsultantCommented:
This isn't anything I have seen before. I have setup loads of RPC CAS Arrays in the past and it just works.

Simon.
0
 
BigBadJVAuthor Commented:
Hi Chestor & Simon,
Many thanks for your contributions to my issue, I have now resolved the problem of the CAS servers not being added as members of the CAS Array. I had completely overlooked the fact that there were 2 sites configured in AD one as the "Default-First-Site-Name" and a second called "Manchester" As the company is only a single site I hadn't looked at the configuration, and blindly setup the CAS Array on the "Default-First-Site-Name" which didn't contain any servers, but because it did exist it allowed me to configure the array.

I will accept both answers and give half the share of the points to you each as you were kind enough to offer assistance.

Regards,
John.
0
 
BigBadJVAuthor Commented:
Resolved issue myself by adding servers to correct AD site and creating CAS Array based on the correct site name.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 8
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now