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

x
?
Solved

Multiple Exchange Server versions on same domain - best way to configure

Posted on 2006-11-29
3
Medium Priority
?
259 Views
Last Modified: 2008-02-01
Currently running Exchange server 2000 on a w2k server.  the w2k server is the domain controller.  also have two windows 2003 servers, and want to install exchange server 2003 on one of them.  only a couple of the users will use this exchange server; the rest will stay will the 2000 server.  if necessary, can set up the windows 2003 server as a separate domain.

the reason for this is to test exchange 2003 with some handhelds vs. blackberry and goodlink, which are currently running with the exchange 2000 server.  Do not want to disrupt anything as everything is working well.

What is the best way to do this?  
0
Comment
Question by:RBECKMN
[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: 18038698
Exchange 2003 will quite happily coexist. If you are using a BES, then it will have to be in the same domain, due to the way that the BES operates.

The only issue you would get is if you have an Exchange 2000 frontend. You cannot have an Exchange 2000 frontend with Exchange 2003 backends, so the frontend would have to be upgraded.

Simon.
0
 

Author Comment

by:RBECKMN
ID: 18038724
Sorry, i don't know what you mean by an exchange 2000 front-end.  do  you mean Outlook 2000?

I asked this question because when I started to install Exchange 2003, it asked me to modify the active directory structure for the domain, and I wasn't sure what impact this might have.  do you know if there is any?
0
 
LVL 104

Accepted Solution

by:
Sembee earned 1000 total points
ID: 18038870
Frontend server is an Exchange server that does not host mailboxes, but provides a single point of entry for multiple backend servers. It is not Outlook.

You have to forest prep and domain prep for Exchange 2003. It doesn't impact the domain so I would go ahead and do it.
To try and get the live users working on another forest and domain (it would have to be both) along with co-existing with your existing forest and domain will be very complex.

You basically have two choices.

1. Bite the bullet and install Exchange 2003 on the production site so that the users can test the handhelds with live data.
2. Build a test lab with a separate forest and domain and have test accounts and test data.

This scenario only allows you to do one of the above two.

Simon.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

New style of hardware planning for Microsoft Exchange server.
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.
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…
how to add IIS SMTP to handle application/Scanner relays into office 365.

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