We have an Exchange 2003 Server - Fully patched. A lot of our Linux and remote users use OWA and are happy enough with it. The OWA is setup to use SSL with a certificate we purchased from Thawte. Again this works fine - all users know that they have to access the server via https:// and if they attempt to access via http:// they are soon told that SSL is required. Just recently some of our Linux users have started creating meetings & appointments via the OWA. Because they aren't using Outlook they get sent an email with a link which takes them into the OWA and I'm assuming allows them to accept or deny the appointment/meeting request. The problem is that all of these requests arrive with an http:// URL and not an https:// one. If the user manually changes the URL in the email message then it works fine, however it means that a user cannot simply click on the link or even do a simple copy & paste - they need to manually change the URL. Why is Exchange doing this? Exchange is correctly configured to use SSL, however something it generating these URLs with an http:// start rather than https:// Thanks.
Paulr wrote: > We have an Exchange 2003 Server - Fully patched. > > A lot of our Linux and remote users use OWA and are happy enough with > it. The OWA is setup to use SSL with a certificate we purchased from > Thawte. Again this works fine - all users know that they have to > access the server via https:// and if they attempt to access via > http:// they are soon told that SSL is required. > > Just recently some of our Linux users have started creating meetings & > appointments via the OWA. > Because they aren't using Outlook they get sent an email with a link > which takes them into the OWA and I'm assuming allows them to accept > or deny the appointment/meeting request. > > The problem is that all of these requests arrive with an http:// URL > and not an https:// one. > If the user manually changes the URL in the email message then it > works fine, however it means that a user cannot simply click on the > link or even do a simple copy & paste - they need to manually change > the URL. > Why is Exchange doing this? > Exchange is correctly configured to use SSL, however something it > generating these URLs with an http:// start rather than https:// > > Thanks. I'm not sure, but I think this may be normal. I suggest you look into setting up a redirect... http://support.microsoft.com/kb/839357
