What is the proper way to redirect http to https on the CAS and still have OWA work whether the user's mailbox is on a 2007 Exchange server or 2003?
My redirect is working fine for users on the 2003 BE server but when a 2007 mailbox user logs onto OWA they receive the following error in IE: "%1 is not a valid Win32 application."
If I replace /exchange with /owa then OWA will continue to log them in and then they can access their mailbox, etc. Any ideas?
I think you have that backwards. I've read that /exchange can redirect to both. But how should I have CAS configured initially in IIS so that it redirects to https? Right now I have a default document that redirects to http://URL/exchange.
Well, my home directory within the default web site is set to /exchange with the option "a directory below URL entered". I have a separate web site that has a default page redirecting to https://URL
Not sure why it ended up being that way, I wasn't ever able to get my custom error 403;4 redirection page to https://URL/exchange
Could someone please tell me how IIS should be set up so a user has to be redirected to https and both 2003 and 2007 mailboxes can be accessible?
When I follow the directions in the link you provided. The only thing that is displayed in IE is the code that was put into owahttps.asp
Also, these directions were written before Exchange 2007, so the ExchangeApplicationPool was not an option. I tried MSExchangeOWAAppPool but that did not work. Any suggestions?
Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
My personal preference is to not even open port 80 on the firewall at all. I don't want anonymous traffic anywhere near the Exchange server. Make the users put https in to the URL. They learn very quickly.
The instructions for Exchange 2003 work the same for Exchange 2007 - as long as you have asp support enabled in IIS. It sounds like you don't. Asp is not asp.net support - they are two different things. Although they are slightly different if the HOST is Windows 2008, not Windows 2003. You haven't said which version of Windows it is installed on.
Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
You have all of the instructions required to do that. You create a default page in the web site to pick up anything that hits the root of the site, and the asp page which replaces the require SSL error page. Redirect to /exchange and not /owa which will provide support for both formats.
If you are seeing the actual code displayed in IE. Its a sure bet that ASP is not being executed. If the file ends in .asp, make sure that Active Server Pages is enabled under web extensions. Outside of any other problems that's why your initial redirect isn't working.