Solved

Exchange 2003 and 2007 Co-Existing

Posted on 2006-11-24
3
368 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 500 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

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In-place Upgrading Dirsync to Azure AD Connect
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

752 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