Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 263
  • Last Modified:

Redirecting external users to new exchange server

We have Exchange server2003 and exchange 2010 server.
at this stage:
Stage1:
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.

Thanks
0
jskfan
Asked:
jskfan
1 Solution
 
gaurav05Commented:
0
 
gaurav05Commented:
0
 
jskfanAuthor Commented:
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 ??

Thanks
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
jskfanAuthor Commented:
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!
0
 
Marc DekeyserSr Premier Field EngineerCommented:
jskfan, that is correct! You cannot avoid having a namespace change for the legacy servers...
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Stage1:
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 :)
0
 
jskfanAuthor Commented:
Thanks a lot
Excellent link!
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now