We have just installed a new exchange system on site B with two HUB/CAS servers and two mailbox servers. Currently I am unable to get OWA to work on site B whilst on the Site A servers it works absolutely fine.
All servers are currently running Exchagne 2010 Service Pack 2 Rollup 1.
I have read up online and tried every combination of using different authentication methods on the new HUB/CAS servers but it does not work for us.
Whilst accessing the OWA page we get the error:
Outlook Web App isn't available. If the problem continues, please contact your helpdesk.
In the event log on the new HUB/CAS we get the error:
Source: MSExchange OWA
Event ID: 41
Task Category: Proxy
Level: Error
Description:
The Client Access server "https://server/owa" attempted to proxy Outlook Web App traffic for mailbox <UserDN>. This failed because no Client Access server with an Outlook Web App virtual directory configured for Kerberos authentication could be found
in the Active Directory site of the mailbox. The simplest way to configure an Outlook Web App virtual directory for Kerberos authentication is to set it to use Integrated Windows authentication by using the Set-OwaVirtualDirectory cmdlet in the Exchange Management
Shell, or by using the Exchange Management Console. If you already have a Client Access server deployed in the target Active Directory site with an Outlook Web App virtual directory configured for Kerberos authentication, the proxying Client Access server
may not be finding that target Client Access server because it does not have an internalUrl parameter configured. You can configure the internalUrl parameter for the Outlook Web App virtual directory on the Client Access server in the target Active Directory
site by using the Set-OwaVirtualDirectory cmdlet.
All help is very much appreciated :)
