Questions/Insights:
1. Just to make sure, I have to ask, you did not happen to rename the "Default Web Site"?
to something else. If you did, then your site and certificate is messed up. The owa can only be on "default web site"
2. I am not sure what doc you read "MS site and they say to make sure the default website is not listening on port 443 for SSL"
But SSL does go out over 443. It needs to be listed as the port, or else you will need a url like this https://exchange.domain.com/exchange:port#
I have ours set up for port 80 and 443.
I also set it up so that any one who connects via http get's redirected to https.
But when all is said and done, the requests are going over 443.
3. If you generated your own certificate, THERE WILL be a problem with it. Press yes when presented with that screen. The only way around it is to get an actual cert through a 3rd party. If this is just for your users, don't bother. All you care about is whether or not the passwords are encrypted.
4. Big Suggestion: If you are running thr OWA on the same machine as exchange, DON't. Reason being is for every user who logs on to the OWA, it opens an instance of outlook.
Even the beefiest of servers can get bogged down when trying to deliver mail plus proccess ssl connections and multiple instances of outlook.
Putting the OWA on another server is actually pretty easy. Just use the install disk to install the OWA. It will do the rest. Caveat: users will have to put in
domain\username at the username\password prompt.
good luck