By default, when you require an SSL certificate in IIS on an Exchange server, if users hit the page without providing an https:// in front they will get an error. Rather than require certificates, it’s better in most cases to redirect unsecured traffic to a secured login page. In order to do so, first configure the redirect. To do so, open IIS Manager and click on the Default Web Site. At the bottom of the pane for the Default Web Site, click Features View if not already selected. Then open HTTP Redirect. Here, check the box for “Redirect requests to this destination” and provide the path to the owa virtual directory (e.g.…
-
-
Kerio and Entourage
Kerio leverages the OWA aspect of Entourage so if you open up OWA on the firewall then Entourage will be able to work over port 80 (or 443).
-
Exchange 2007: OWA Virtual Directories from PowerShell
Get a list of all of your virtual directories from PowerShell using this command: Get-OwaVirtualDirectory If you are having an issue with a specific virtual directory then you can delete it using this command: Remove-OwaVirtualDirectory “owa (Default Web Site)†In the above command we used owa but we could have also used Exchange, Public, Exchweb or Exadmin. To recreate the directory use the following command (again replacing owa in the “” portion of the command with the specified virtual directory you are recreating: New-OwaVirtualDirectory -OwaVersion “Exchange2007″ -Name “owa (Default Web Site)†Because Exchange, Public, Exchweb and Exadmin are not native to Echange 2007 then you would actually replace Exchange2007 with Exchange2003or2000.…
-
WAF: Web Application Firewall
Web Application Firewalls, or WAFs, are firewalls for web application. They monitor web traffic and decide whether to allow or deny specific requests. IIS web servers (OWA), Apache, WebObjects, Lasso and other web servers will likely end up working with them, although I’ve only tested IIS and Apache at this point.