Forum Discussion

Andy_2570's avatar
Andy_2570
Icon for Nimbostratus rankNimbostratus
Dec 15, 2009

OWA irule

I'm a somewhat new user still so forgive me if this is an easy fix that i'm overlooking..

 

 

Currenlty i'm using

 

when HTTP_REQUEST {

 

if { not ([HTTP::uri] starts_with "/owa") } {

 

HTTP::uri "https://[HTTP::host]/owa[HTTP::uri]"

 

}

 

}

 

 

to send user to the owa login.. Works great.. My exchange admin needs me to point to

 

 

when HTTP_REQUEST {

 

if { not ([HTTP::uri] starts_with "/exchange") } {

 

HTTP::uri "https://[HTTP::host]/exchange[HTTP::uri]"

 

}

 

}

 

 

in order to allow '03 and '07 owa logon.. When i use the /exchange the page bombs out. When I looked at the OWA server I do notice that instead of an .asp page there is a web.config that launches the session.

 

 

So my question is has anyone gotten \exchange to work in their environment? My investigation makes it seem like an issue on the exchange server and not the F5 as it's working fine for my original target..

 

 

Any insight is great appreciated.

 

 

Thanks,

 

Andy

7 Replies

  • Hi Andy,

    Is this for two different webmail VIPs or multiple hostnames on the same HTTP VIP? For the older version, can you just redirect the client to /exchange from /? Or try preending /exchange if it's not there already?

      
      when HTTP_REQUEST {  
        
         if { not ([HTTP::path] eq "/exchange") }{  
        
             Redirect client to same host with /exchange prepended  
            HTTP::redirect "https://[HTTP::host]/exchange  
         }  
      }  
      

      
      when HTTP_REQUEST {  
        
         if { not ([HTTP::path] starts_with "/exchange") }{  
        
             Prepend /exchange to the path  
            HTTP::path "/exchange[HTTP::path]"  
         }  
      }  
      

    Aaron
  • Hey Aaron,

     

     

    Sorry shouldn't have been more specific.. It's a single URL. The /owa and /exchange are both seperate virtual directories that are running on the owa server. Pretty much out of the box Microsoft setup. With just extremely different results when I call them.

     

     

    Thanks,

     

    Andy
  • Isn't /owa for 2007 and /exchange for 2003? If so, how do you know whether a request for / is for 2003 or 2007?

     

     

    Thanks,

     

    Aaron
  • "Supposedly" that where the \exchange comes in. My Exchange admin is telling me if that people hit that directory it will figure it out for them via AD credentials.. it seems this is more of an Exchange issue than an F5, as my orginial setup works just fine. i'm going to kick this back to him..

     

     

    Thanks for your help!!
  • Sorry, I'm confused--I've only worked with OWA 2003--not 2007. Can you clarify what your overall goal is? What are you trying to do with the /exchange directory? If someone accesses that URI directly, are they able to log into the app?

     

     

    Thanks,

     

    Aaron
  • No worries... I need to have users get to both owa 2007 and 2003 via the F5. My admin is telling me that if I can get users to the \exchange directory it will work. He sent the attached article but as I re-read it it makes it seem like it's not possible..

     

     

    http://docs.google.com/Doc?docid=dkj3jt7_81g6x5smqv&hl=en

     

  • That doc seems to show how you can redefine the virtual directory in OWA 2007 if you wanted to reset it or change it from the default of /owa.

     

     

    This MS technote seems to indicate that you need two virtual hosts to support OWA 2003 and 2007:

     

     

     

    http://technet.microsoft.com/en-us/library/bb885041%28EXCHG.80%29.aspx

     

     

    Consider the following as you plan the deployment of Outlook Web Access in your environment:

     

     

    * If your organization will include Exchange 2007, Exchange 2003, and Exchange 2000 computers, we recommend that you install the Exchange 2007 Client Access server role and the Exchange 2007 Mailbox server role on separate computers. However, if you want to combine the Client Access server role and the Mailbox server role on a single computer while still maintaining Exchange 2003 and Exchange 2000 computers, you must expose two URLs, as follows:

     

    o One URL goes to the Exchange 2007 computer. For example, https://.contoso.com/owa.

     

    o The other URL goes to the Exchange 2003 or Exchange 2000 computer. For example, https://.contoso.com/exchange.

     

     

     

     

    Though maybe that's not the exact scenario you have. If/when you do figure out what you'd like to do with an iRule please let us know.

     

     

    Aaron