Hi, In middle of a 2007/2010 co-existence environment where mailboxes will reside on both versions of Exchange for a week or two. Setup: Exchange 2007 SP3 in a CAS Array Exchange 2010 SP2 Update Rollup 3 in a CAS Array After changing the local host file on a test machine to point to 2010 CAS array. I try and access a mailbox in the 2007 environment. The 2010 CAS manages to find the 2007 servers but redirects to 'https://server.domain.local/owa/auth/owaauth.dll' and throws a HTTP 400 error. Authentication on both Exchange versions is FBA. The cert which exists on the 2007 CAS also exists on the 2010 CAS so not sure if this is cert related. The cert is a SAN with the following sub domains. webmail.domain.com legacy.domain.com autodiscover.domain.com Within Exchange 2007 ECP my internal OWA URL is https://CASserver1.domain.local/owa Within Exchange 2010 ECP my internal OWA URL is https://webmail.domain.com I have tried various combinations of URLs in the above of which all fail. Help would be much appreciated! Thanks

You've posted to the Compliance forum, which isn't really appropriate for your question, which would be better posted in Admin, General or Deploy. You have a cert issue if Exchange is redirecting to CASServer1 since that isn't in the cert on the Exchange 2007 server. Change the internalURL on the Exchange 2007 virtual directories (all of them!) to legacy instead of CASserver1.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

You've posted to the Compliance forum, which isn't really appropriate for your question, which would be better posted in Admin, General or Deploy. You have a cert issue if Exchange is redirecting to CASServer1 since that isn't in the cert on the Exchange 2007 server. Change the internalURL on the Exchange 2007 virtual directories (all of them!) to legacy instead of CASserver1.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Sorry..I tried changing the forum type but it didnt let me. Oddly enough I placed the legacy url as a parameter for internal but got the same 400 error as before https://legacy.domain.local/owa/auth/owaauth.dll

Hi, Sorry..I tried changing the forum type but it didnt let me. Oddly enough I placed the legacy url as a parameter for internal but got the same 400 error as before https://legacy.domain.local/owa/auth/owaauth.dll

When you run (where E2K7SERVER is the name of your Exchange 2007 server): Get-OwaVirtualDirectory -Server E2K7SERVER | FL Server,*URL What do you see?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

When you run (where E2K7SERVER is the name of your Exchange 2007 server): Get-OwaVirtualDirectory -Server E2K7SERVER | FL Server,*URL What do you see?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

hi, Please check your iis log on both exchange 2010 and exchange 2007 hope can help you thanks,CastinLu TechNet Community Support

hi, Please check your iis log on both exchange 2010 and exchange 2007 hope can help you thanks,CastinLu TechNet Community Support

Hi, Here is what I get if I run it against both servers... --------------------- Server : FrontEnd01 Url : {} InternalUrl : https://legacy.domain.com/owa ExternalUrl : -------------------- --------------------- Server : FrontEnd02 Url : {} InternalUrl : https://legacy.domain.com/owa ExternalUrl : --------------------

Hi, Here is what I get if I run it against both servers... --------------------- Server : FrontEnd01 Url : {} InternalUrl : https://legacy.domain.com/owa ExternalUrl : -------------------- --------------------- Server : FrontEnd02 Url : {} InternalUrl : https://legacy.domain.com/owa ExternalUrl : --------------------

Looks like you forgot to set the externalURL, this needs to be set to legacy.domain.com Ensure that the ExternalURL value is populated and the InternalURL value is set to $NULL for the OWA virtual directory on the Exchange Server 2007 CAS that is the target of the redirect. If necessary, use the following command to set this: Set-OwaVirtualDirectory -Identity "CAS_Server_Name\OWA (Default Web Site)" -ExternalURL https://legacy.company.com/owa -InternalURL $NULL. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Looks like you forgot to set the externalURL, this needs to be set to legacy.domain.com Ensure that the ExternalURL value is populated and the InternalURL value is set to $NULL for the OWA virtual directory on the Exchange Server 2007 CAS that is the target of the redirect. If necessary, use the following command to set this: Set-OwaVirtualDirectory -Identity "CAS_Server_Name\OWA (Default Web Site)" -ExternalURL https://legacy.company.com/owa -InternalURL $NULL. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

hi, any update? thanks,CastinLu TechNet Community Support

hi, any update? thanks,CastinLu TechNet Community Support

Hi, It turned out that the EWS directory on 2007 servers needed to point to https://legacy.company.com. Shame this isnt documented and I'm surprised it hasnt cought more people out! Thanks

Hi, It turned out that the EWS directory on 2007 servers needed to point to https://legacy.company.com. Shame this isnt documented and I'm surprised it hasnt cought more people out! Thanks