Redirecting external users to new exchange server

Posted on 2011-09-15
Medium Priority
Last Modified: 2012-05-12
We have Exchange server2003 and exchange 2010 server.
at this stage:
we have some mailboxes that are still in exchange server 2003 and some have been move to exchange 2010. I would like to know how external users can be redirected to exchange server2010 for the ones that have their mailboxes mived to exchange 2010

Stage 2:
when all mailboxes are moved to exchange 2010, how external users will be redirected to exchange 2010, though it sounds like the same as Stage1.

Question by:jskfan
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
LVL 10

Expert Comment

ID: 36547671
LVL 10

Accepted Solution

gaurav05 earned 2000 total points
ID: 36547680

Author Comment

ID: 36558525
I believe this part of the article is talking about what I have asked, but sti;; ambiguous:

<<<When a client connects to Exchange Server 2010, it actually connects to the Exchange Server 2010 Client Access Server and if the mailbox is still on the Exchange Server 2003 Mailbox Server then the client is redirected to the Exchange Server 2003 front-end server. This front-end server then handles the connection request. This automatically means the namespaces of the Exchange environment will change.>>>

Ok, external users use https://webmail.mycompany.com 
to access outlook.
What changes need to be done either in Exch2010 or Exch2003 so that users that have their mailboxes still in Exch2003 will go to Exch2003 and users that have their mailboxes moved to exch2010 wil be redirected to exch2010 ??

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why


Author Comment

ID: 36558559
I see on that article they mentioned the examples below, but I am not sure how would they relate to my case scenario.
https://webmail.inframan.nl – This is used by all Internet clients that connect to the Exchange environment. This name is not different than in the Exchange Server 2003 namespace, but it will now point to the Exchange Server 2010 Client Access Server;
https://autodiscover.inframan.nl – This is used by Outlook 2007 and (Outlook 2010) clients for autodiscover purposes;
https://legacy.inframan.nl – This will be the new namespace for the Exchange Server 2003 front-end server. This automatically means that the namespace for the Exchange Server 2003 front-end server is going to change!
LVL 11

Expert Comment

by:Marc Dekeyser
ID: 36563703
jskfan, that is correct! You cannot avoid having a namespace change for the legacy servers...
LVL 15

Expert Comment

ID: 36564037
we have some mailboxes that are still in exchange server 2003 and some have been move to exchange 2010. I would like to know how external users can be redirected to exchange server2010 for the ones that have their mailboxes mived to exchange 2010

the answer to this stage and to stage two is the same. All services provided to external users must point to Exchange 2010. For example if you have ISA or TMG publishing OWA, ActiveSYnc, OAB, etc, you need to change those rules to point to exchange 2010 cas server.

Then what happens?

Well for all services except OWA Exchange 2010 CAS will PROXY the request internally to Exchange 2003, if the user mailbox resides on 2003.

For OWA you need a different namespace, resolved externally, for example exchange2003.mycompany.com, and you need to create a publishing rule for that namespace. That name also needs to be resolvable from the Internet. And finnaly you need forms based auth enabled on 2003 CAS.
The process will be: your 2003 user types https://webmail.mycompany.com/owa-> authenticates on 2010 forms based auth->gets redirected to https://exchange2003.mycompany.com/exchange
finally on your cas server set the owa~virtual directory exchange2003url parameter to https://exchange2003.mydomain.com/exchange

and DONE :)

Author Closing Comment

ID: 36572186
Thanks a lot
Excellent link!

Featured Post

Enroll in August's Course of the Month

August's CompTIA IT Fundamentals course includes 19 hours of basic computer principle modules and prepares you for the certification exam. It's free for Premium Members, Team Accounts, and Qualified Experts!

Question has a verified solution.

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

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses
Course of the Month7 days, 20 hours left to enroll

765 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