Exchange ActiveSync not working if form based authentication or SSL enabled

Thanks, I've heard that fixed a lot of problems.

Not mine. I actually started over tonight... and removed almost everything according to:
http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permission s-Exchange-2003.html

Once I got everything gone... I configured my setup to include the virual directory, no form based login and my SSL. Also, the new virtual directory does not require the SSL at https://webmail.mycompany.com/OMA

Right now I feel EVERYTHING is perfect according to other posts including yours. Anything else you can suggest.

Does adding a second virtual directory screw up anything with the current OWA setup? I want OWA to still work after I create the second virtual directory.

Simonns wrote:
Does adding a second virtual directory screw up anything with the current OWA setup? I want OWA to still work after I create the second virtual directory.

If you're talking about using the steps in KB 817379, then no, it won't mess up your OWA experience. I personally recommend a combination of following Microsoft KB 883380 then Microsoft KB 817379. Note: you only follow KB 817379 if you have a single server environment. SBS would be considered a single server environment. If you have a front end/back end environment then you don't need to follow KB 817379. This is clearly mentioned in the Method 1 section fo KB 817379.

The URL you provided https://... does require SSL as it has a "s".

Have you tested the server OMA setup with a notebook or desktop ( https://webmail.domain.com/OMA)?
You should receive a login prompt for username & password following by an Inbox listing of messages.

We used this step to verify server setup before configuring an iPhone. Lastly, we made certain that connectivity would work from outside or within our company by doing the following:
1) created A record for webmail.domain.com to a public IP that route through the firewall on 443 to the Exchange server's private IP - this handles external traffice
2) added an internal DNS record for webmail.domain.com to the private IP of the Exchange server.

This ensures that webmail.domain.com sync's to exchange from outside or from within the Enterprise.

FYI, the http://servername/OMA test will not work in Exchange 2007. Exchange ActiveSync (EAS) (In E2K & E2K3) uses the http://servername/microsoft-server-activesync virtual directory. If you test login to http://servername/microsoft-server-activesync you should get an HTTP 501/505 message/error if it's working properly. It's not the best test, but it does give you a fairly good assessment that EAS is working properly.

Message was edited by: ethanm