Exchange 2010 Multiple OWA Sites

Greetings. We've got an entity within our organization which would like a different OWA logon page (I've customized the default one for the larger organization).  Our UCC cert does have the smaller organization's fqdn in it and the mx record in dns for "mail.other_entity.org" gets them to our OWA page.

I've read that a second OWA virtual directory can be created.

Do I need a second IP / NIC on the mail server to make this happen ?  If so, could someone direct me to some detailed procedures ?

Thanks much.
-Stephen
lapavoniAsked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
You don't need a second NIC.
You will need a second IP address, both internally and externally.
That is because SSL is a 1:1 binding to IP addresses.

So setup the second IP address to Exchange. Then change the default web site to be bound to the first address specifically (it will be on "any" by default).
Create a second web site in IIS and adjust the bindings, including SSL for it.

Then create new virtual directories. You will need OWA, ECP and EWS for it to work correctly. OAB and Outlook Anywhere can stay on the default (the end users will not see that), as can ActiveSync, as that can cause problems outside of the default.

Simon.
0
 
lapavoniAuthor Commented:
I've got two NICs that are teamed on the server.  Will that be an issue ?  Just add a second IP to the team ?

Also, it's bound to 127.0.0.1  Does loopback apply to all addresses or just the first one ?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Simon Butler (Sembee)ConsultantCommented:
What is bound to 127.0.0.1 ? The second web site?
It needs to be bound to a specific address, not the loopback address. Don't touch the default site, other than to change the * to the specific address.

Being a team means nothing - as you have a virtual NIC which holds the address.

Simon.
0
 
lapavoniAuthor Commented:
The first website is bound to 127.0.0.1  .... not to *
0
 
Simon Butler (Sembee)ConsultantCommented:
The only binding you have to change is the http 80 *, no others.
You should have two bound to port 80, 127.0.0.1 and *.

There will then be one, maybe two bound to HTTPS. You will need to change any of those to a specific address.

Simon.
0
 
hecgomrecCommented:
I disagree with Simon on this one.

I have mail.mycompany.net, webmail.mycompany.net on my ISP DNS pointing to the same IP.

On my IIS I have a redirect from either to the virtual directory of owa.  This was for legacy purposes when the company was not using autodiscover for their exchange server and the "webmail" was use for OWA only.


Now, in your case you can have a name for the other organization, copy all OWA virtual directory onto a new directory of your choice (lets called "branch" for now) and add it to the default web site.  Modify your logon and logoff .aspx files.  When you want the main owa just use mail.maincompany.org and for the other one you could use mail.branchcompany.org.

So when user type in their browser mail.maincompany.org they will get to the main OWA and the other organization users will use mail.branchcompany.org/branch to get their OWA.

As you can see this works the same way your actual services do (mail.maincompay.org/ecp, mail.maincompany.org/oab, mail.maincompany.org/owa)
0
 
Simon Butler (Sembee)ConsultantCommented:
Except that isn't a supported method.
The only supported route is to use a different web site and use new-owavirtualdirectory

Simon.
0
 
lapavoniAuthor Commented:
I will read up on the alternative solution, but the supported one is always preferable.  Thank you again, Simon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.