Announcement

Collapse
No announcement yet.

Including a new Client Acces Server for a CAS Array...what to do next?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Including a new Client Acces Server for a CAS Array...what to do next?

    I have an Exchange 2010 environment, with one HT/CAS server and two mailbox server in a DAG. I would like to build a second CAS server to have a CAS Array. I have already built the CAS array object when I first set-up my Exchange environment. I have installed the second CAS server. I was wondering, in order to continue to configure the CAS Array, what configuration would I need to do on this second CAS...I assume it needs to look exactly like the first CAS....same external/internal FQDNs for OA, OWA, Activesync, Audodiscover? I assume I would add the DNS entries for these FQDNs in DNS just like they are for the first CAS? Would I export the SSL cert from the first CAS to the second CAS? I assume I configure the virtual directories for Activesync, OA, EWS etc. just like I did on the first CAS? In summary, configure the second CAS like the first CAS and then I can proceed with the NLB portion on the configuration?

    Thanks,

    alex

  • #2
    Re: Including a new Client Acces Server for a CAS Array...what to do next?

    The CAS Array is for MAPI traffic only - nothing else.
    It should be unique to that. Web services should have its own host name.
    You can use the same host name on both servers, but that does mean only one server will be used. If you want to use both then you will need load balancers.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Including a new Client Acces Server for a CAS Array...what to do next?

      Can a CAS array be used for HTTP-over-RPC traffic...or strictly MAPI? I have hundreds of OutlookAnywhere clients out there.

      Comment


      • #4
        Re: Including a new Client Acces Server for a CAS Array...what to do next?

        The CAS Array is just MAPI traffic, nothing else.
        If you try and use it for Outlook Anywhere as well, then you will get a lot of problems because Outlook Anywhere depends on the Exchange server's FQDN (so CAS Array) being unresolvable on the internet. It then times out, fails over to the HTTPS traffic flow.

        The CAS Array only does MAPI traffic over TCP, nothing else.

        Don't get it confused with a load balancer address.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment

        Working...
        X