Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2003 and 2007 Co-Existing

Posted on 2006-11-24
3
Medium Priority
?
370 Views
Last Modified: 2010-03-06
Hello,
I have a fully functional Microsoft Exchange 2003 SP2 Front End/Back End Clustered non production environment. People use RPC/HTTP, OWA and ActiveSync to access their mail. I’ve recently installed an Exchange 2007 Server in this organization to take this non production network to the next level of testing. Email can be sent and received from mailboxes on the 2007 server. My question is how to make OWA and ActiveSync available on both the 2003 and 2007 Exchange Servers. I currently have a rule on my SonicWALL 2040 directing port 443 to my 2003 Front End Server. Please let me know if you have any suggestions.
Thanks
Jeff
0
Comment
Question by:fluffyfrog
[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 104

Expert Comment

by:Sembee
ID: 18008699
Simple.
You need to replace the Exchange 2003 frontend with an Exchange 2007 equivalent. They are backwards compatible.
Remember the golden rule with frontends - it should always be the same or higher than the backends that it is serving.

Simon.
0
 

Author Comment

by:fluffyfrog
ID: 18008775
Thanks for your response. I just want to make sure tha I completey understand the solution.
If I replace my existing Exchange 2003 Front End Server with an Exchange 2007 Edge Tranport Server it will serve OWA and ActiveSync for both the 2003 and 2007 Back End Servers. And, there 'may' be no more network changes to make. (it just sounds too simple)  :)

Thanks

Jeff
0
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 18008793
That is the theory. I haven't done it myself as I just haven't had the time to spend with Exchange 2007. It is still a BETA product and the changes are significant enough that the skills in the community will take time to come up to speed.

The basic principle will stay the same, but the actual setup and configuration could change. I understand that there are significant changes between the last public BETA and the RTM version - which is partly why I am waiting before getting stuck in with Exchange 2007. Three versions of Exchange in my head, plus service pack differences is quite enough without having to learn two variants of Exchange 2007.

Simon.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

704 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