Go Premium for a chance to win a PS4. Enter to Win

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

CAS Array Issue

Exchange 2010 sp1--Outlook 2010

Problem: Can’t resolve the cas array name while creating a new Outlook profile. I can ping both IP and name of the cas array.
 
After creating the cas array and then a new Mailbox Database (the RpcClientAccessServer attribute of the cas array shows in the new Database), I then moved my mailbox to the new Mailbox Database. Outlook failed to restart. Could there be a an issue with Autodiscover service or the certificate? I have yet to reissue the certificate to include the cas array name.  
0
Anthony K O365
Asked:
Anthony K O365
  • 7
  • 5
1 Solution
 
ctc1900Commented:
Verify autodiscover is working correctly, thys the Test E-mail AutoConfiguration

http://www.addictivetips.com/microsoft-office/outlook-2010-test-email-auto-configuration/

Also, verify the connection status.. shows the right information for the Server name. You can find this option right above the Test E-mail Autonfiguration option
0
 
Anthony K O365Author Commented:
Autodiscover is working find. My client is using the cas server for connection, not the cas array name. However, again, the cas array name does not resolve when creating a new profile.
0
 
ctc1900Commented:
Just to confirm what you originally said, the mailbox database hosting this user does show the right RPCClientAccessServer?

Get-MailboxDatabase "Database_Name" |fl Name,RPCClientAccessServer
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Anthony K O365Author Commented:
Yes. For example, the Mailbox Database RpcClientAccessServer property shows the cas array name. The other mailbox databases shows the name of the cas server. Currently, this user's mailbox is in that mailbox database. When I move the user to the other database in which the RpcClientAccessServer property is the cas array name, I can't resolve the name when creating the profile. One engineer says to check autodiscover which seems to be working. This problem occurs even when manually creating the user profile.
0
 
ctc1900Commented:
That's strange, it is as if the autodiscover does not see the change taking place.  Does the Test E-mail AutoConfiguration for this user show something similar to the following?

Display Name: Name

Protocol: Exchange RPC
Server: CAS Array Name
Login Name: username

0
 
Anthony K O365Author Commented:
Yes, it shows everything except for the Server: which in this case, is the name of the cas server. To have it show the cas array name, I would need a client whose profile shows the cas array name. That is my issue. Again, even if I configure the client manually, by typing in the cas array name (which is an AD object) it does not resolve.
0
 
ctc1900Commented:
What do you get when you run "Get-ClientAccessArray -Identity CasArrayName"? Do you see the proper site location, fqdn, and members?

0
 
Anthony K O365Author Commented:
Yes I do. The setup looks correct. Do you think it has anything to do with certificate or autodiscover?
0
 
ctc1900Commented:
It sounds like autodiscover. One more thing we cuould check is the Autodiscover URL being used if you haven't already done so:

Run the Test-Email AutoConfiguration once more, check the Log and see which Autodiscover URL it successfully connected to.  Then, make sure the the URL resolves to a proper Exchange 2010 SP1 CAS system
0
 
Anthony K O365Author Commented:
I got the casarray to work by doing a Repair in Account Settings in my Outlook 2010 client. Thanks much!
0
 
Anthony K O365Author Commented:
I appreciate the  diagnosis and assistance.
0

Featured Post

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!

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now