How to point Outlook Anywhere and OWA to a site other than Default Web Site in IIS7

I have an Exchange 2007 SP1 Rollup 8 server that houses all of the roles. The OS is Server 2008. I have two Web Sites in IIS with two certificates.  The first certificate bound to the Default Web Site is a self signed certificate with the internal server name (Server-Name.InternalDomain.com).  The certificate bound to the second web site is a third party certificate with the outside domain name (Mail.Domain.com).   Due to the internal domain being owned externally by another company a Unified Communications Certificate is not possible.  The server was migrated from a 2003 server where their were two web sites in IIS.  The additional Web Site held the Rpc, RpcWithCert, and OWA virtual directories with the third party cert bound to its address while the Default Web Site housed the rest with Self Signed Certificate bound to it.  I cannot get Outlook Anywhere to point to the second web site.  I also recreated the OWA virtual Directories on the second web site but Exchange still looks to the Default Web Site.  The main goal of this is of course to make it so their are no certificate warnings for internal, OWA, or Outlook Anywhere users.
LVL 4
advserverAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MesthaCommented:
The fact that your domain is owned by someone else does not mean you cannot have everything on a single server, unless you are using the UC role. It is perfectly possible with some URL manipulation to have everything running on the single site, with the certificate holding the server's NETBIOS name, autodiscover.example.com and mail.example.com (or whatever address you want to use for remote access) on the certificate. The only name you can't have is the server's FQDN.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
advserverAuthor Commented:
Thank you Simon for your quick response! This appears to be the solution I am looking for.  I will close this question and open another if I have a problem implementing the solution.  Thank you again!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.