II have a predicament: we setup a 3rd party exchange archival system by Mimosa, Nearpoint. All is good except that now I need it to work with OWA. All was simple until I enabled OWA over SSL and got my organization a simple SSL certificate for the IIS; installed it and tested it and is running fine: accessing OWA from public domain recognizes the certificate and communication works as it should over SSL.
However, Mimosa Nearpoint cannot communicate with OWA server because of the internal vs. external naming differences. The certificate is for email.mydomain.org while the netbios internal name is server (simplified for here only). So the connection is refused.
Now I tried with the CA to get a multi domain certificate& to make it short, after some misdirection, IIS over Windows 2003 and Exchange 2003 do not support UCC. So I am back to the only possible solution I can think of: setup a 2nd OWA website on the same server with its own internal SSL Cert.
Is this possible? Any one now of an article for that (I was not able to locate one on MS/KB).
(BTW: it behooves me that Mimosa cannot solve this& still trying with them as well.)