Tuesday, November 4, 2008

How To: Recreate OWA Virtual Directory - Exchange 2007

How To: Recreate OWA Virtual Directory - Exchange 2007. So many times I heard that OWA doesn’t work on Exchange 2007 server. There would be many reason behind it, like permission configuration, missing files, not able to load properly, .net errors etc…

There are different solutions base on various reasons but no one works then you may try by recreating OWA virtual directory which is giving problem.

Check and note the settings of directory in EMC before recreating it, like InternalURL, ExternalURL, Forms-Based Authentication settings ect..

Exchange server

Procedure:

  • First step is to identify the directory which is giving the problem.

You can use Get-OwaVirtualDirectory to get the list of virtual directories.

Exchange 2007

  • Now let’s say I have problem while accessing owa directory. Remove it with below command.

Remove-OwaVirtualDirectory “owa (Default Web Site)”

Exchange server 2007

  • Now create it again with below command.

New-OwaVirtualDirectory -OwaVersion “Exchange2007″ -Name “owa (Default Web Site)”

image

Note: if you are recreating other than owa directory which are legacy Exchange directories then you need to use “Exchange2003or2000″ in OWAVersion switch instead of “Exchange2007″

  • Now configure the “owa” virtual directory settings like InternalURL, ExternalURL, Forms-Based Authentications etc… & check the OWA by logging with some test users.
Source: exchangeshare.wordpress.com/2008/07/16/how-to-recreate-owa-virtual-directory-exchange-2007

2 comments:

vishal said...

Its a good news for the internet radio listeners, now you can listen your favourite internet radio through this web site, we provide unlimited music 24/7, so go a head click here to rock.....


Enjoy your music,

Thank you.

Alexis said...

To my humble opinion one of the worst troubles is MS Exchange's problems. Because of I had nearly some dozens problems. Fortunately several days ago I came across one software, which might solve this problem not worse than mine - fix microsoft exchange.