OWA and Client Access FAQs

This FAQ page is devoted to OWA and Client Access Server topics (primarily moved from Ask a Question page).

Q: Can you have multiple virtual directories for OWA in Exchange 2007? I want to have a couple of different URLs available on CAS. Is this possible?
A: You can have multiple Virtual directories for OWA in Exchange 2007. However, they have to be in their own website. So, by default, we have “Default Web Site (OWA)” to represent owa Vdir under “Default Web Site” in IIS. If you want to create a new vdir for OWA, you have to create a separate web site and create the owa vdir under that web site. Not sure what you mean by couple of different URLs available on CAS – can you please re-phrase?  
   
Q: How do you reset Outlook Web Access (OWA) Virtual Directories? (i.e., /exadmin folder)
A: Remove the Client Access role from the server, remove IIS, remove the INETPUB directory and the ClientAccess directory, reboot and reinstall both. Be very careful of making changes to OWA through IIS, try to make any changes (such as integrated authentication) through the Exchange Management Console.  

Q: Is it possible to increase the OWA signature size for Exchange 2007? The Exchange 2003 registry key is located in a completely different section. (Apoc)
A. Nope it is not possible to increase the size. Max Html + text signature size = 8kb.  

Q: I am configuring a 2 Node Single Copy Cluster with Exchange 2007 and a SAN. I need to place OWA into the DMZ but this is not possible. I heard that I can use reverse proxy to achieve this. Are there any white papers or links that explain this?
A: You are correct seperating the CAS and Mailbox server with a firewall is not supported. You would want to put a ISA server (or other reverse proxy) in front of the CAS servers and allow access to the ISA server from the internet. More information can be found here: http://www.microsoft.com/technet/isa/2006/deployment/exchange.mspx or Setup OWA With ISA.

 Q: Has anyone used to ISA 2006 with Exchange 2007 to publish Pop3 and Imap4?  I got OWA published but Pop3 is not working.
A: First, are you sure POP/IMAP work internally? POP and IMAP pubishing is very different than HTTP (web) publishing.  You have to use server publishing (mail server) rules.  It does not 'proxy' similar to the web publishing.   Some things to watch for:

• Make sure you have the correct network type set (routed or NAT)
• Make sure you set the packets appear from the source or client address correctly (there is no one 'correct' answer - it depends on the network relationship type)
• If you are doing secure POP/IMAP, make sure the certificates are valid, etc.

Q: I have a server with the Hub & CAS role together. We found out that pop & IMAP by default use +/- 150 MB of RAM. In one month the microsoft.exchange.pop3.exe service run over 4 GB of RAM! We started the service and it did release the memory. We have 2000+ accounts but only 40 of them are POP3. Has anyone else seen an issue like this? If so, please let me know if there is something to fix it other than installing SP1. Any one else using POP3 please check your usage.  
A: Your best bet would be to install the latest pre-SP1 rollup, or Service Pack 1 as there have been a number of fixes in both ASP.NET and the POP/IMAP services since RTM.