Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 746
  • Last Modified:

How to configure IIS/DNS to redirect to OWA virtual directory

My company is running Win2K3 with Exchange 2003 installed.  This machine is also hosting our certificate services for exchange/https mail download.  OWA is also running on this machine as well.

Basically when users go to access OWA from the web they have to type in https://servername1.companyname.com/exchange.  I want to shorten this down to just https://mail.companyname.com.  My ISP DNS is setup with a single A record for 'servername' pointing to my external IP.  

Can anyone tell me what the easiest way to accomplish this is without any disruptions or downtime?

0
jmtoman
Asked:
jmtoman
  • 5
  • 4
2 Solutions
 
page1985Commented:
Absolutely.  You'll want to do three things:
  1. In your ISP's DNS  for your domain name, you will want to create another A record pointing mail.companyname.com to the same address as servername1.companyname.com
  2. On your OWA server, you'll need to check the properties of the HTTP virutal server that OWA is running on to make sure either you don't have host names specified, or that you add mail.companyname.com to the listener list.
  3. You will want to enable the .NET Framework on your virtual server and create a file in the root of the site (usually C:\Inetpub\wwwroot) named Default.aspx with the following contents:
<%
     Response.Redirect("https://mail.companyname.com/exchange")
%>

Open in new window

0
 
jmtomanAuthor Commented:
Ok that sounds simple enough, the other thing I just throught of is roughly half my users are getting exchange via http download.  When I'm setting up the Outlook profile I only specify mailserver.company.com and not mailserver.company.com/exchange, will this redirection have any effect on those users?
0
 
jmtomanAuthor Commented:
Ok I added the default.aspx page and when I try https://mailserver.company.com it redirects to the /exchange directory, but ONLY internally.
0
Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

 
MesthaCommented:
This is how I do it:
http://www.amset.info/exchange/owa-defaultpage.asp

Doesn't matter how the server is referenced, so it could be http://server or http://192.168.1.1/ or https://something.example.com/ it will redirect to the /exchange virtual directory.

Simon.
0
 
jmtomanAuthor Commented:
Ok so I've used both methods to redirect my default website to my /exchange directory and it ONLY works internally.  I'm a little bit confused?  Anyone have any ideas?
0
 
MesthaCommented:
Are you going through anything else between the internet and the server?
What happens when you hit the root of the site? It shouldn't matter if it is inside or outside because Exchange simply doesn't care. It is just inbound traffic.

Simon.
0
 
jmtomanAuthor Commented:
ISA server between internet and server.  When I hit the root of the site it goes to owa fine.  Would it make any difference if my /exchange directory is set to use integrated windows authenticated and my default site is not?
0
 
MesthaCommented:
The /exchange virtual directory needs to use integrated, so that is fine.
However as you are using ISA, I would be looking at that as the cause of the problem. If it works internally then it isn't an Exchange configuration issue.

Simon.
0
 
jmtomanAuthor Commented:
You were right on the money, it looks like we had some errors in our web publishing rule on isa server.  So now when i go to https://mailserver.companyname.com it is redirecting me correctly.

I added a cname record with my isp for mail.companyname.com but here is the kicker now, when i go to the website it will give me the error message for being an untrusted certificate but when i click continue anyway it just gives me a 403.  
0
 
MesthaCommented:
A CNAME doesn't redirect you, so if you don't have mail.example.com in the certificate then you would get an error. I don't have much to do with ISA server, but I do know that ISA can store a copy of the certificate as well as the Exchange server. If your SSL certificate does contain the name then I would check if ISA is using the right certificate.

Simon.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now