Announcement

Collapse
No announcement yet.

setting up new CAS array "broke" my exchange 2010

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

  • setting up new CAS array "broke" my exchange 2010

    Hey everyone,

    Question for anyone who might have some insight.

    We are opening up a new branch office in a month or so, and I am in the process of trying to get everything ready. Due to site restrictions, I don't yet have access to getting my servers up and going yet, but I figured I would get a head start on some things.

    As of yet, we have never properly set up our AD domain into separate sites. We have three current locations, but they all operate as one AD site. It has worked ok for us, but I have wanted to get things segmented out into proper sites, so I figured I would start with this one.

    I started out by setting up my site and configuring my link in AD. No problem. I figured next I would go ahead and define my CAS array object in exchange 2010, and point my DNS entry at the exchange server when it came up in a few weeks.

    However, in a great "oh shit" moment, as soon as I defined my CAS array object in my new site, I noticed that my client outlook became disconnected in my original site, and quickly verified that it was company wide. Also, MXtoolbox started throwing me alerts that it could not make SMTP connections to my current exchange servers, which really surprised me because I didn't think a CAS array had anything to do with SMTP connections. Undoing the new CAS array object and the new site resolved the problem and everything came up fine.

    I thought that defining a CAS array in a different site would not effect client access in different sites, but clearly I am mistaken or there is an important point I am missing. Anyone have any thoughts? I would greatly appreciate it.

  • #2
    Re: setting up new CAS array "broke" my exchange 2010

    The CAS Array should not have had anything to do with the downtime.

    There are three bits to the CAS Array, and until all three are in place it isn't effective.

    DNS Entry
    CAS Array Object
    Modification to the database.

    Even then, the clients don't use it, as they have to be updated to use the new address.

    However as you haven't said exactly what you have done, it is hard to say much more. The only thing I can think of is that you used a name used for something else. I have configured the RPC CAS array many times and not had a single instance of downtime.

    Did you have an RPC CAS array in place already?
    Have you renamed your Sites, created the new sites etc?

    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: setting up new CAS array "broke" my exchange 2010

      Sorry, let me see if I can be more explicit...

      We have a single site currently set up in AD. It hasn't even been renamed, and is still called Default Site Link (or whatever the name is).

      We do not have an RPC CAS array currently defined for the default site. The autodiscover points directly at a CAS server, exch.domain.local

      The steps I performed are:

      created new site in Sites and Services - siteB
      set up link beween original site and new siteB
      defined subnet that would exist in siteB

      I then opened the Exchange Shell and performed the following command:

      New-ClientAccessArray -Fqdn siteBCAS.domain.local -Site "siteB" -Name "siteBCASname"

      I then was in the process of opening up DNS on a domain controller to specify a DNS entry for siteBCAS.domain.local when I noticed everything was out of commission.

      Since I was unable to quickly determine what happened, I removed the new CAS array with the appropriate Powershell command, and everything came back online.

      Originally posted by Sembee View Post
      The CAS Array should not have had anything to do with the downtime.

      There are three bits to the CAS Array, and until all three are in place it isn't effective.

      DNS Entry
      CAS Array Object
      Modification to the database.

      Even then, the clients don't use it, as they have to be updated to use the new address.

      However as you haven't said exactly what you have done, it is hard to say much more. The only thing I can think of is that you used a name used for something else. I have configured the RPC CAS array many times and not had a single instance of downtime.

      Did you have an RPC CAS array in place already?
      Have you renamed your Sites, created the new sites etc?

      Simon.

      Comment


      • #4
        Re: setting up new CAS array "broke" my exchange 2010

        There is nothing in what you have done that should have caused problems with the Domain. You must have done something else or made an error elsewhere that took time to replicate.

        Personally I would rename the default site (it is just a display name) and have an RPC CAS Array in both AD Sites.

        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


        • #5
          Re: setting up new CAS array "broke" my exchange 2010

          Thanks.

          It is my intention to get a RPC CAS array going with our original site. I have not done it yet for a variety of reasons (not technical, just time).

          The only thing I can think of is maybe since I have no RPC CAS arrays defined anywhere, maybe defining the first one did something wonky. It shouldn't do anything from what I understand, though.

          I will review what I did (and replicate it during non critical hours), and see if I can better sniff out what happened.

          Comment

          Working...
          X