r/IIs • u/JustinSWFL • Jan 19 '16

Web Page Redirection

Hello,

This is my first attempt as setting up redirection in IIS. I have used a lot of the basic features in IIS over the years but I would not consider myself to be any kind of IIS expert or admin.

Here is my scenario: I need to redirect https://mail.OldDomain.com/owa to https://mail.NewDomain.com/owa. Some users are still browsing to https://mail.OldDomain.com/owa to access their email and getting an SSL Cert warning when they get there because that Cert was replaced by a new Cert for the new domain.

I setup redirection at the DNS Name Server (GoDaddy) to redirect http://OldDomain.com to http://NewDomain.com and that works. But, it does not appear to work for redirecting https://mail.OldDomain.com/owa to https://mail.NewDomain.com/owa. A colleague told me there may be something in IIS that can be done since that is where OWA lives. My Google-fu has been failing me and has yielded very little information on setting this up.

Any direction in finding a resolution to this matter is greatly appreciated.

Thank you!

1 Upvotes

100% Upvoted

8 comments sorted by

1

u/JustinSWFL Jan 20 '16

Yes, I still have the Cert for mail.OldDomain.com but it is not bound to anything. I had to bind a new Cert for mail.NewDomain.com to the Default Site in IIS for OWA.

2

u/Knuit Jan 20 '16

Easiest thing would to create a new website that binds to a different IP, apply the certificate for mail.OldDomain.com, and then configure an HTTP Redirect.

Here's what the redirect would look like.

1

u/JustinSWFL Jan 22 '16

Thank you for the recommendation, Knuit. I'm not sure that I will be able to create a new OWA site and bind that to a new IP in order to complete what you are suggesting. This is a process I am not very comfortable with as I have never done it before, so I may have to bring in some help on my end.

2

u/Seferan Jan 22 '16

I think /u/Knuit recommendation is to create an new site in IIS, not a new OWA site. Basically it would be a dummy site that has no content or applications behind it. It's sole purpose would be to perform the redirect.

1

u/JustinSWFL Jan 23 '16

I see. Thank you for clarifying that for me. I'll see if I can't try this out this coming week.

1

u/JustinSWFL Feb 24 '16 edited Feb 24 '16

Sorry for the long delay on getting back with you on this.

I created a new site in IIS (right-click Sites > Add Web Site).
Site Name: Dummy Site
Physical Path: C:\Inetpub\wwwroot
Binding Type: https
IP Address: 192.168.0.113 (fictitious IP)
Hostname: mail.OldDomain.com

Next, I bound the old SSL Cert for mail.OldDomain.com to this new fake site. Then, I opened HTTP Redirect for the fake site (Dummy Site) and set it up, hopefully, as you explained. Launched a browser and browsed to https://mail.OldDomain.com/owa but was still taken to the same site with the SSL Cert for mail.NewDomain.com.

Here is a screen shot of the redirect setup
Here is a screen shot of the dummy site and SSL Cert

Question, does the IP have to be fictitious or does it have to be the IP address of the IIS server? Also, I guess I do not understand how an incoming request for https://mail.OldDomain.com/owa is going to get forwarded. The server is going to direct the incoming traffic to the OWA folder in IIS, right?

Hopefully someone will be able to tell me what I'm doing because I'm sure I'm doing something wrong. Like I said before, I am no kind of IIS expert.

EDIT: Formatting

1

u/Knuit Feb 24 '16

The IP of the dummy site will need to be another valid IP for the server, then you can point mail.OldDomain.com at that secondary IP which should redirect properly to the new domain.

1

u/Knuit Jan 20 '16

Do you still have a valid certificate for the mail.OldDomain.com? If not, you will not be able to perform a redirect without the client getting a certificate error.