Exchange Server Forums

Does OWA require its own separate website?

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2010] >> Outlook Web Access >> Does OWA require its own separate website?

Page: [1]

Message

<< Older Topic Newer Topic >>

Does OWA require its own separate website? - 24.Aug.2016 5:32:57 PM

jjtarask

Posts: 1
Joined: 24.Aug.2016
Status: offline

I�m working on upgrading our small Exchange 2003 environment to Exchange 2013, doing a temporary hop to Exchange 2010 to get there. Our 2003 setup is one back-end server and one front-end server that�s also our web server, hosting our company website. There�s something I�m confused about. In Exchange 2003 we have Outlook Web Access as a �subfolder� of this website, requiring only one public IP address for the both of them, like so:

- Company website: www.company.com
- Outlook Web Access: www.company.com/Exchange

But what I�ve read about Exchange versions 2010 & 2013 seems to indicate that they require a whole separate website for client access from the Internet (Outlook Web App, ActiveSync), and thus an additional public IP address:

- Company website: www.company.com
- Outlook Web App: webmail.company.com

Is this really the case, or is there a way to keep the company website and Exchange client access on the same website, thus not having to add an additional public IP address? Could http redirect accomplish this? All of our public IPs are in use and I�d prefer not to have to buy more.