Hi,Did anyone face a situation where, when you try to install Exchange 2007 SP2 on a CCR nodes which span across multiple sites. Am getting following error when am trying to run setup.exe /m:upgrade on my passive node which is located in my Site A. My configuration as follows Site A consist of 1 Domain Controller and CCR Node A ( IP subnet 192.168.1.x) Site B consist of 1 Domain Controller and CCR Node B ( IP subnet 192.168.2.x) all servers are on windows 2008 SP2CCR node on Site B is the currant passive node and ma running the above command on that server, I have made the schema changes on domain controllers running setup.exe /prepairAD. And it went well. Am getting following Error when I try to upgrade the passive CCR node. This cluster spans multiple Active Directory sites. Exchange Server 2007 cannot be installed. Detected Active Directory sites: SiteA, SiteB. Any idea why this is happening and workarounds to install SP2 ----Cheerspadman

I hope that you have seen the articles below: Mailbox servers in a geographically dispersed cluster require that a single AD site be stretched between the datacenters because all nodes in the cluster must be members of the same site. However, there is no requirement that any other servers in both datacenters be on the same subnet or in the same AD site --------- Refer to Planning for Cluster Continuous Replication All nodes in an SCC or CCR environment must be in the same Active Directory site. Although Windows Server 2008 failover clusters introduce support for cluster nodes to be members of different Active Directory sites, this configuration is not supported by Exchange 2007 --------- Refer to New High Availability Features in Exchange 2007 SP1 I dont know how you managed to deploy CCR in the different AD sites. The nodes of the cluster can be in different subnet, but they should be in the same Active Directory site. Exchange 2007 still requires AD site spanning, because of the manner in which it utilizes AD sites for mail flow And, the error This cluster spans multiple Active Directory sites. Exchange Server 2007 cannot be installed is the indication for it

As james suggestedWindows 2008 allows for multi subnetted CMS nodes, however the caveat is that both nodes must be in the SAME AD SITE.http://technet.microsoft.com/en-us/library/bb124521.aspxMy Suggestion but not a answer.....There could be a possibility that After installation of CCR nodes (Geo Clustering) in to different subnets, your AD Team may have configured Sites and splitted the subnets in AD sites and services...Check the Functaniolity of CCR server, does the nodes functioning properly...Also post a detailed Architecture of your setup (CCR in 2 different Subnets) and also post us information on DC's with IP's

HI, Thank youll for inputs, I was fully aware that CCR nodes required to be in the same AD site or if its in 2 different IP subnets AD site has to be stretched. I did this configuration purposely to see the possibility of putting CCR on different AD sites. When I was configuring CCR , I had only one AD site and then after installing i created 2 AD sites and move the subnets accordingly, until the SP 2 installation it was working fine and I did tested the failover and it worked without any issue. Now am trying to figure out what the problems can occur with this setup. Except the SP2 installation Site A (IP subnet 192.168.1.x) Site B (IP subnet 192.168.2.x) Site A consist of DC,CCR Node, HT/CAS Site B consist of DC,CCR Node, HT/CAS all Servers are on windows 2008 SP2Email flow was working perfectly and all the clients (OWA/outlook anywhere/MAPI) access works fine. Did test the failover and it works perfectly. Now my question is what the reason it said that CCR does not supported this configuration. -----CheersPadman De Silva

HI,I asked from one of the Exchange team people and I have mentioned his update below.Microsoft doesnt support that because on a move or failover, only the clustered mailbox server would change AD site. The User, the CAS and HUB boxes, etc.., would not change sites and would thus be out-of-site after a failover and that might be the reason to break mail flow. According to your second post, it may appear to work, but its not supported and tested configuration by Microsoft. Resources Planning for Cluster Continuous Replication Regards

HI,Thank you for your input, am working with Exchange Product Team to see the possible issues i would face with this configuration,for your information there wear no issues with mail flow or the client access after failover. my configuration here is bit complex and am sharing that information with Exchange team to see why this configuration is not suppoted---CheersPadman De Silva

Thanks for the sharing from one of my friends, I noticed one of the reason that the CCR can’t be stretched to different sites, which is Transport Dumpster. “When a failover is experienced that is not lossless, the clustered mailbox server automatically requests every Hub Transport server in the Active Directory site to resubmit mail from the transport dumpster queue” ------------Refer to <New High Availability Features in Exchange 2007 SP1> Per my knowledge, the dumpster would fail if the nodes are in the different sites, as the MBX server will only request the Hub in its local site Resources: How the Transport Dumpster works with a CCR cluster