Solved

Cass array on San certificate

Posted on 2011-03-09
4
536 Views
Last Modified: 2012-08-14
Is the name of the Cass array on the SAN supposed to be the internal name or an external name? and if it is the external name does that mean we have to add the Cass to our external DNS?



0
Comment
Question by:iamuser
  • 2
4 Comments
 
LVL 26

Expert Comment

by:e_aravind
Comment Utility
CAS Array:
This is the logical name\object for few CAS servers correct?
We need to have this name visible for both the Internal and External Users\access.

>> On the MBX databases we need to add the same CAS-array name
>> The traffic from the external world (eg. OWA) should reach the CAS-array-name to get the OWA requests completed\fulfilled

Or AM i missing something here in the question
0
 

Author Comment

by:iamuser
Comment Utility
This is the logical name, the issue is that my internal is different to my external. All the examples I've seen are always cas.domain.com

For us though our internal is inside.domain.com. The internal dns will have the array as array.inside.domain.com

So I don't see how array.domain.com is going to resolve to array.inside.domain.com. Or even how this certificate is going to be valid as both fqdn are different
0
 
LVL 49

Accepted Solution

by:
Akhater earned 250 total points
Comment Utility
It doesn't matter for the CAS array name it can be your inside name or an external name you will just need to decide what you want your cas array to be called. basically you can call it anything but of course this name should be in the SAN of your certificate


No you don't need your CAS to be accessed from outside so, no matter what, you cas array name will not figure in your external dns
0
 
LVL 26

Assisted Solution

by:e_aravind
e_aravind earned 250 total points
Comment Utility
Regarding the Autodiscovery for the internal URLs

waht is the answer for the
Get-ClientAccessServer value?

Is that the name in the SAN Certificate?
If needed here, you can have the external-URL\name of the NLB

Reference:
==========
Finally we need to point the Autodiscover Service Internal Uri to the FQDN of the HLB. This can be done using:

Set-ClientAccessServer –Identity <Server Name> -AutoDiscoverServiceInternalUri: https://mail.domain.com/Autodiscover/Autodiscover.xml

http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/load-balancing-exchange-2010-client-access-servers-using-hardware-load-balancer-solution-part2.html
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now