I have exchange deployed on 3 servers in 2 AD sites as follows; AD Site 1 Server 1 Client Access Hub Transport Server 2 MailBox Unified Messaging AD Site 2 Server 3 MailBox Client Access Unified Messaging The design is such that we wanted to have 1 OWA for both sites, but it doesn't seem to work. I get the follow messages when you try to login; Outlook Web Access is not available. If the problem continues, contact technical support for your organization and tell them the following: There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored. Is there something special I need to do in this case? Dave

Dave, did you ever figure this one out? I'm seeing the same thing here.. Can you email me directly? jim.ferguson@REMOVETHISPART.axcelis.com Thanks!

For anybody running into this problem, this KB article resolved the issue for my organization. http://support.microsoft.com/kb/320202/en-us -Adam

I have the same problem too, i tried what they said in the KB, deinstalled, reinstalled IIS, deinstalled and reinstalled Client Access, did the command, nothing new. Same error again.

Zer0 G wrote: For anybody running into this problem, this KB article resolved the issue for my organization. http://support.microsoft.com/kb/320202/en-us -AdamWe found it, this is half the solution.We had to go in our exchange 2007 setup directory. execute:setup.com /prepareADWe had a FAILED that the setup cannot contact with the master schema AD site.We did shutdown our primary DC. rerun setup.com /prepareAD and it worked.After that, we did the deinstall IIS/reinstall IIS, then the Client Access uninstall/install like in the KB Adam posted.Last step in the configuration of the Client Access, the internal URL has to be the same as the server name and in Authentification, we did put Windows Integrated Auth + Basic Auth. Thats on our mailboxses server. We have a "Front End" we left the username/password and it still work.You can do the same with:Set-OwaVirtualDirectory -Identity "owa (Default Web Site)" -WindowsAuthentication $true- Carl

Hi David, regading to your problem, you need to configure your exchange CAS Servers located in the second site to be able to recieve the proxied requestes that comes from the First Internet Facing CAS Server. in order to understand what i am talking about, i advice you to read this section from the Exchange 2007 Help File located under Technet Website: Understanding Proxying and Redirection http://technet.microsoft.com/en-us/library/bb310763.aspx another thing i noticed. for the second Site, and this has nothing to do with your OWA Access problem. in the Server role lists that you provided in your email for the second site, i noticed that you didn't install Exchange 2007 - HUB Server. if this is true, then your users located in the mailbox server in the second site WILL NOTbe able to send or recieve emails to each others or to outside. HUB server is mandatory server role when you have a mailbox server under certain site. you need to have HUB server in the same AD Site of your mailbox server located in the same AD site inorder for the mailbox users located in this AD site to be able to send and recieve emails to each others within thier AD Site, with other users located in other AD Sites, and to outside as well. Regards, Alaa A. Al-Ankar Community: The ProRangers (http://www.prorangers.net) Blog: aalankar.blogspot.com

HI, I hav tried all the options mentioned in this Forum, but stil the problem persists.... "There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored." please help me out guys need it on urgent basis. Scenario: Central Site: 1-HUB & CAS facing the internet 1-Mailbox cluster Secodary Site: HUB CAS MAILBOX I am facing problems for the users in the Mailbox of secondary sites. Central site users are able to access their OWA properly Thank u all in advance, Kiran Babu.............

I had the same issue where OWA said that our clustered mailbox server was not a member of the Exchange site. In our case, the solution came by adding CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=local in ADSIedit under Configuration --> Services --> Microsoft Exchange --> Your Exchange site name --> Administrative Groups --> Your Administrative Group name --> Servers --> Your mailbox server name. Right click on the server name and open properties. Look for the attribute msExchServerSite and add the site information if it is missing. After restarting the cluster and both mailbox servers, OWA worked again.

I'm having a similar roadblock in my Exchange 2007 setup...i have it running in a lab...i've got both AD sites setup in an isolated environment...which is an exact copy of production. Scenario: Site 1: Public facing 2003FE handles all OWA and ActiveSync requests...url is https://owa.domain.com. Setup Exchange 2007 SP2 UR4 with CAS and HT role installed. I want this to handle all internet and device requests similar to my 2003 FE. Name of 2007 box is CAS1. Site 2: Corporate Site...has internet connectivity of course, but none of my exchange servers are accessed directly via the internet. All 2003 BE servers are here including two new Exchange 2007 systems...same SP and UR level. MB1 has CAS, MB, and HT. MB2 has CAS, MB. CAS will be balanced via NLB in future configuration. I set CAS1 to redirect default website level to https://cas1.domain.com/exchange. SSL disabled on default website, enabled an all sub vdirs. Exchange 2003 mailbox users can hit cas1.domain.com and get redirected to https://cas1.domain.com/exchange. They log in fine and get shuttled to their 2003 BE server fine for OWA experience. Test user with mailbox on MB1 goes to same URL. When they log in, they get 403 Forbidden. After tweaking things (undoing redirection, reinstating SSL on default website as setup during Exchange 2007 installation) I get an error stating There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored. I literally cannot get this going. Any ideas?

An Exchange 2007 CAS server will not proxy for Exchange 2003 mailboxes if there is also the mailbox role installed on it. You need a CAS or CAS+HT server without the mailbox role. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Ytsejamer1" wrote in message news:dea51e9e-0274-440f-8db9-900441191317... I'm having a similar roadblock in my Exchange 2007 setup...i have it running in a lab...i've got both AD sites setup in an isolated environment...which is an exact copy of production. Scenario: Site 1: Public facing 2003FE handles all OWA and ActiveSync requests...url is https://owa.domain.com. Setup Exchange 2007 SP2 UR4 with CAS and HT role installed. I want this to handle all internet and device requests similar to my 2003 FE. Name of 2007 box is CAS1. Site 2: Corporate Site...has internet connectivity of course, but none of my exchange servers are accessed directly via the internet. All 2003 BE servers are here including two new Exchange 2007 systems...same SP and UR level. MB1 has CAS, MB, and HT. MB2 has CAS, MB. CAS will be balanced via NLB in future configuration. I set CAS1 to redirect default website level to https://cas1.domain.com/exchange. SSL disabled on default website, enabled an all sub vdirs. Exchange 2003 mailbox users can hit cas1.domain.com and get redirected to https://cas1.domain.com/exchange. They log in fine and get shuttled to their 2003 BE server fine for OWA experience. Test user with mailbox on MB1 goes to same URL. When they log in, they get 403 Forbidden. After tweaking things (undoing redirection, reinstating SSL on default website as setup during Exchange 2007 installation) I get an error stating There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored. I literally cannot get this going. Any ideas? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."