How to enable SSL for new Exchange HTTP virtual Server



After created a new HTTP virtual server in exchange system manager for those
user with smtp domain different to the default smtp domain, there isn't
option to add 443 in virtual server property(which is disabled by default).
So manually add in 443 by using IIS manager, but SSL port always drop in a
while by system attendant service. Understanding that there is another
solution to create new virtual directory in the default HTTP virtual server
for different smtp domain, but how about using new HTTP virtual server? Or I
must create this new virtual server using IIS manager but not Exchange
System Manager. Any idea about this? Thx


.



Relevant Pages

  • Re: How can I change virtual server default???
    ... When you go into IIS manager you will see both sites (local computer -> Web ... IIS infecting worms like Code Red walk IP address ranges and ... If all of your virtual servers have host headers ... > How can I change virtual server default??? ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: not able to create new portal
    ... is the topology correct? ... > virtual server in IIS Manager then try again! ... > What is your topology, i.e. what are the boxes that SharePoint is ...
    (microsoft.public.sharepoint.portalserver)
  • SMTP Virtual Server Missing
    ... Got into IIS Manager ... and "Default SMTP Virtual Server" is supposed to be in there, ... The network has a BDC, also 2003 Standard, ...
    (microsoft.public.windows.server.general)
  • Re: Exchange HTTP Virtual Server Instance 100 :The IsAlive check f
    ... replication and the system was fine for almost a week. ... I suggest you remove XOSoft ... Exchange HTTP Virtual Server Instance? ...
    (microsoft.public.windows.server.clustering)
  • Re: Upgraded to Exch2003, OWA2003, but experience is slow
    ... I applied Exch2003 to front-end and now that works. ... > Creating the HTTP Virtual Servers in Exchange System Manager ... > When you create an Exchange Virtual Server, ... > You must create one Exchange HTTP virtual server for each front-end ...
    (microsoft.public.exchange.admin)