| Author |
Message |
Bryan Jones
Guest
|
 Posted:
Thu Dec 02, 2004 12:21 am Post subject:
Exchange 2000 Cluster, IIS, and OWA SSL port value |
|
|
Whenever IIS is stopped on one of the nodes of our Active/Passive Exchange
2000 cluster (such as when the passive node is rebooted after any type of
application maintenance), the SSL port value of 443 in the website
properties for OWA is lost. Upon failing back to that node, when the
virtual server web site comes back up, you must manually go to IIS and enter
the SSL Port value again.
This is a long-standing issue that I've researched on-and-off for almost 2
years... never found a good solution.
|
|
| Back to top |
|
 |
Bryan Jones
Guest
|
| Posted:
Thu Dec 02, 2004 12:24 am Post subject:
Re: Exchange 2000 Cluster, IIS, and OWA SSL port value |
|
|
By the way - this is the closest possible item I've found, but I'm not
willing to test it yet since it specifically refers to "non-clustered"
exchange.
http://blogs.msdn.com/evand/archive/2004/02/25/79818.aspx
"Bryan Jones" <bryan.jones@findwhat.com> wrote in message
news:%23FkQgK91EHA.3452@TK2MSFTNGP14.phx.gbl...
| Quote: | Whenever IIS is stopped on one of the nodes of our Active/Passive Exchange
2000 cluster (such as when the passive node is rebooted after any type of
application maintenance), the SSL port value of 443 in the website
properties for OWA is lost. Upon failing back to that node, when the
virtual server web site comes back up, you must manually go to IIS and
enter the SSL Port value again.
This is a long-standing issue that I've researched on-and-off for almost 2
years... never found a good solution.
|
|
|
| Back to top |
|
|
Evan Dodds [MSFT]
Guest
|
| Posted:
Thu Dec 02, 2004 7:10 am Post subject:
Re: Exchange 2000 Cluster, IIS, and OWA SSL port value |
|
|
Bryan -
My blog post only refers to non-clustered Exchange at the beginning, in
differentiating the behavior between HTTP VS that are in the Default website
and those that are not. Whether you create the HTTP VS as a secondary VS on
a non-clustered server or whether you're using the default VS created on a
cluster (which is also a secondary VS on the node), the behavior is the same
and should follow the notes in the blog post.
That said, from what I read below your solution is simple. Don't set the SSL
configuration in IIS if it's a secondary HTTP VS. This will never stick, as
the configuration from ESM will overwrite it when DS2MB process runs. All
these changes should be made through ESM GUI.
--
Evan Dodds
Microsoft Exchange Support
****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.
"Bryan Jones" <bryan.jones@findwhat.com> wrote in message
news:e7NoMM91EHA.924@TK2MSFTNGP14.phx.gbl...
| Quote: | By the way - this is the closest possible item I've found, but I'm not
willing to test it yet since it specifically refers to "non-clustered"
exchange.
http://blogs.msdn.com/evand/archive/2004/02/25/79818.aspx
"Bryan Jones" <bryan.jones@findwhat.com> wrote in message
news:%23FkQgK91EHA.3452@TK2MSFTNGP14.phx.gbl...
Whenever IIS is stopped on one of the nodes of our Active/Passive
Exchange 2000 cluster (such as when the passive node is rebooted after
any type of application maintenance), the SSL port value of 443 in the
website properties for OWA is lost. Upon failing back to that node, when
the virtual server web site comes back up, you must manually go to IIS
and enter the SSL Port value again.
This is a long-standing issue that I've researched on-and-off for almost
2 years... never found a good solution.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in