Quantcast
Viewing all articles
Browse latest Browse all 7129

Exchange 2013 with application request routing

We have a domain that's been used for 2007 mail services, also handling our CAS OWA services. That server also hosts another application, on the same server with the same hostname, but a different virtual directory for the application.

Now I need to split them apart.  I have no hostnames for each server, on brand new segregated servers.  I've been asked however to put up a web server to route the old hostname to each new server if someone hits the old hostname.

So for example mail1.mydomain.com/owa routes to server1 at mail2.mydomain.com/owa and mail1.mydomain.com/app1 routes to server2 at app1.mydomain.com/app1

I've been told that IIS application request routing can accomplish this.  After reading over it, seems plausible.  I'm unsure however how the exchange services like outlookanywhere, EWS, OAB, etc will work in this scenario.  I would think yes, since it's just an http port 80 call to a hostname.

Does anyone know if this will work?


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>