Solved

Exchange 2003 in 2 sites - Best way to configure OWA

Posted on 2011-03-17
3
350 Views
Last Modified: 2012-05-11
I have (2) Exchange 2003 servers in (2) sites, separated by a PPP link.  The servers talk back and forth to each other, and each server is running OWA, (1) single storage group each with a PRIV database and a PUB database.

We recently introduced the 2nd server into a single server environment, and the MX record for the organization lands email on SITE A, which then routes email across the PPP link to recipients that are in SITE B.  Everything flows fine.

When it comes to OWA, however, when users at SITE B sign into OWA over the internet at SITE A like they always did, after they sign in, their URL is changed to "http://EXCHANGE02.myorg.local" from "http://mail.myorg.com".

I do NOT have any other servers to dedicated as a frontend server for this situation.

My question is:  Can I just check the box on the original Exchange server at SITE A to make that server a FRONTEND SERVER, leaving the mailboxes that are on it there, and expect OWA to now service not only the local server at SITE A, but also to service the local server at SITE B. ?  I'm not sure if changing the server to a FRONTEND SERVER will actually PREVENT the store front working.  I know it's not a best practice to do this, but as I said, we CANNOT dedicate a 2nd server at this time to being a Frontend ONLY server.

Thanks!
0
Comment
Question by:jkeegan123
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 31

Accepted Solution

by:
Justin Owens earned 500 total points
ID: 35157610
If you check that box you will remove mailbox access rights on that server (I have actually made that mistake in production...  Was not a fun moment for me).  Front End servers really cannot have mailboxes on them and work properly.
0
 
LVL 5

Author Comment

by:jkeegan123
ID: 35157778
So other than creating a separate OWA address through the firewall of the other site, utilizing a different host name in the DNS zone on the internet, is there any way besides dedicating access via a stand alone front end server?
0
 
LVL 31

Expert Comment

by:Justin Owens
ID: 35157839
Unfortunately, no.
0

Featured Post

Increase Agility with Enabled Toolchains

Connect your existing build, deployment, management, monitoring, and collaboration platforms. From Puppet to Chef, HipChat to Slack, ServiceNow to JIRA, Splunk to New Relic and beyond, hand off data between systems to engage the right people.

Connect with xMatters.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question