Every day or two my OWA will lose the capability to use SSL. If I look in IIS the SSL port is blank. If I fill in the SSL port as 443 HTTPS://my webmail will start to work again. I am not using the default Website for OWA and created a new OWA Virtual server. Any ideas

Jaso

Re: OWA losing SSL port by Evan

Evan
Mon Jan 05 19:36:35 CST 2004

Jason -

Much of the configuration in IIS is pulled from the AD, so if you change it
in IIS manager, it will quickly be overwritten with the information from the
AD. You can configure the AD information through Exchange System Manager. If
you set the secure bindings on your secondary protocol VS in ESM, it should
stick.

--
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.

"Jason Rahl" <anonymous@discussions.microsoft.com> wrote in message
news:20C61305-F8A3-4E35-AA04-203B00A3BFB6@microsoft.com...
> Every day or two my OWA will lose the capability to use SSL. If I look in
IIS the SSL port is blank. If I fill in the SSL port as 443 HTTPS://my
webmail will start to work again. I am not using the default Website for
OWA and created a new OWA Virtual server. Any ideas?
>
> Jason
>
>



Re: OWA losing SSL port by anonymous

anonymous
Tue Jan 06 10:36:14 CST 2004

Evan:

How do I set the secure bindings on my secondary protocol VS?

Thanks

Jason

Re: OWA losing SSL port by Evan

Evan
Fri Jan 09 20:38:53 CST 2004

Jason -

There's not a good interface for it, unfortunately. Setting it through
ADSIedit is probably your best bet. Navigate with ADSIedit to roughly this
location:

CN=<theVS#>,CN=HTTP,CN=Protocols,CN=<yourEVSname>,CN=<yourAGname>,
CN=Administrative Groups,CN=<yourORGname>,CN=Microsoft Exchange,
CN=Services,CN=Configuration,DC=<yourDOMAINname>

Pull up properties on the protocol VS object at this location and inspect
the
attribute "msExchSecureBindings". You want it to be set in the format
"<theEVS-IP#>:443:" so that it will bind to the IP of the EVS. Once you've
set it at this level, it should synchronize back into the metabase on both
nodes and "stick" through future moves.

--
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.

"Jason Rahl" <anonymous@discussions.microsoft.com> wrote in message
news:CDA35A10-0154-4716-8D73-4B7694B52A2A@microsoft.com...
> Evan:
>
> How do I set the secure bindings on my secondary protocol VS?
>
> Thanks
>
> Jason