• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 960
  • Last Modified:

Exchange 2007 OWA Redirection

My Google skills have apparently left me this morning. We are having a problem with a clients Exchange 2007 OWA. We migrated the bulk of mailboxes from 2003 over the weekend, but there appears to be a problem with OWA login. Users are used to using the /exchange in the url which should be fine, as if their mailbox is on the new server it should forward the user to the /owa directory. This works, albeit that it actually forwards them to /owa/exchange. If you remove the /exchange of course it works, but for some reason the redirection is doing this funky addition. We are using HTTP redirection in IIS7 on the default web site to forward users to the correct OWA address (https://***.co.uk/owa). I can see that as a result the /exchange, /exchweb and /public folders have for some reason inherited that HTTP redirection. Could this be the cause?

Users that have their mailbox on the 2003 server are proxied correctly. Public folder access works fine (the public folders haven't been copied across to the new server yet).

Any ideas?

Many Thanks
0
ITProtocol
Asked:
ITProtocol
  • 2
  • 2
  • 2
1 Solution
 
mvgeertruyenCommented:
I had some issues with the redirect (apparently a bug; after a while it crashes IIS...)
I think there are better ways then using the IIS redirect; a number of really good articles for your scenario can be found on the exchange team website:
http://msexchangeteam.com/archive/2007/02/07/434523.aspx
0
 
v-9sousoCommented:
hi,
please remove all the redirections from the default website under IIS 7
remove all the virtual directories
Type the following commands. Press ENTER after you type each command.
Note These commands are case-sensitive.
Remove-OwaVirtualDirectory "exchange (default web site)"
Remove-OwaVirtualDirectory "public (default web site)"
Remove-OwaVirtualDirectory "exchweb (default web site)"
Remove-OwaVirtualDirectory "owa (default web site)"

recreate virtual directories
New-OwaVirtualDirectory "exchange" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Mailboxes -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "public" -OwaVersion Exchange2003or2000 -VirtualDirectoryType PublicFolders -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "exchweb" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Exchweb -WebSiteName "Default Web Site"
New-OwaVirtualDirectory -name "owa" -OwaVersion Exchange2007 -WebSiteName "Default Web Site"

now please go to exchange management console
under server configuration go to client access
under the properties of the OWA virtual directory you will find internal URL please specify the FQDN name of the server there (Ex. https://Exchange.domain.com/owa)
please let me know if you if this resolves
0
 
ITProtocolAuthor Commented:
I have recreated the virtual directories in the past and as I recall it solved the problem then, however, we still want to redirect users who only type email.***.co.uk to https://email.***.co.uk/owa and I figured the best way was to use HTTP redirection in IIS7 on the default website as I've never been able to rely on forwarding from an HTML page, be it ASP, Javascript etc.
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
ITProtocolAuthor Commented:
Forget all that I have solved the problem with a cunning idea. In the IIS7 redirection I changed the redirection behaviour to "Redirect all requests to exact destination (instead of relative to destination". This solved the issue and 2007 users now get forwarded correctly to /owa instead of /owa/exchange.

Thanks for the advice anyway guys.
0
 
mvgeertruyenCommented:
It sounds like a good solution (if you don't have the bug I had http://blogs.technet.com/mblant/archive/2008/08/29/exchange-2007-owa-crash-issue-on-windows-2008-server-iis7.aspx). Just putting a redirect in the page has always worked for me as well.

(<meta HTTP-EQUIV="REFRESH" content="0; url=/OWAl">)
0
 
v-9sousoCommented:
Create the following file in Notepad and save it to drive:\inetpub\wwwroot as SSLRedirect.htm, replacing <server name> with the name of your Client Access server:

 Copy Code
<html>
<head>
<title>HTML Redirection to https:</title>
<META HTTP-EQUIV="Refresh"
CONTENT="1; URL=https://<servername>/exchange">
</head>
<body>
This page is attempting to redirect you to <a href="https:// <servername>/exchange/">https:// <servername>/exchange</a><br>
If you are not redirected within a few seconds, please click the link above to access Outlook Web Access.
</body></html>Open IIS Manager, and then navigate to Web Sites/Default Web Site. Right-click Default Web Site, and then click Properties.

Click the Home Directory tab, and then select A redirection to a URL.

In Redirect to, enter /Exchange.

Select The client will be sent to: A directory below the URL entered above.

Click the Custom Errors tab, and then find HTTP Error 403;4 in the table. Click 403;4 to select it, and then click Edit.

Click Browse to locate the file that you created at the start of this procedure.

Click OK to save your changes.

Open a Command Prompt window, and then type iisreset /noforce to restart IIS.


this is another opetion which you can use for redirection
i am glad that it has resolved your issue
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now