this is my first post here and I must say I've been through a couple of threads before posting so excuse me if I missed something about my case. Maybe you can hit a link so i can have a look. That being said, i'll try my best to describe my situation. :)
My exchange environment is 2007, Windows 2008 R2 Standard, Hub-CAS-MB server roles. One domain.local and externaly domain.com hosted by another company for the website.
I wanted to implement the Outlook Web Access function which wasn't set before. I don't have a lot of knowledge in MSExchange so I went through a lot of sites like I said to build this up and try to understand what is what.
I issued a UCC Certificate from Starfield Secure. To that certificate I added those SANs: owa.domain.com mxserver.domain.local domain.com domain.local mxserver
Once it's been done, I went to my Certificate MMC (Computer Account) to import it in the Intermediate Certification Auhorities. After that, went in the shell to import-exchangecertificate -path C:\owa.domain.com.crt. Then I enable-exchangecertificate -thumbprint etc...
In the IIS7 console, i went on the Default Web Site and doublecheck the bindings on 443 to make sure it's the right certificate added - correct.
SSL Settings on the DWS are 'Require SSL' and 'Accept'. I added a Redirect to the error 403 on https://owa.domain.com/owa for the users. That works fine.
Long story short, my problem is went users try to have access from their home. They have a certificate warning when entering https://owa.domain.com instead of using the certificate i've issued from Starfield.
I must say that I contact my ISP for adding an A Record in their DNS for pointing to my Firewall's ip address. So the record is owa.domain.com to the firewall's wan port.
In my DNS, I added a forward lookup zone called domain.com and in it there is owa and autodiscover A Record pointing to the server's address locally in the domain.local network.
my problem is went users try to have access from their home. They have a certificate warning when entering https://owa.domain.com instead of using the certificate i've issued from Starfield.
What can I do at this stage?
For those interested, I solved my problem by checking every aspect of the configuration. I'm connected with a reverse proxy which was configured with a SelfSigned certificate. I replaced like an import-exchangecertificate command in the powershell but on the reverse proxy server and then it's working fine. I have to figure out the HTTPS redirection now.
If i figure out to configure the redirection, i'll post my steps. I already did a try with error 403 on file redirection, etc. but it was not a success. I'll try again on some less rushing days.