Setting up coexistance between Ex 2k and Ex 2k7
I would like to introduce Exchange 2007 servers to two sites in our domain that currently have one exchange in each city. City A and City B.
I wanted to setup Clustering on each end with EDGE roles on the DMZ of each site and Mailbox Roles in each site.
Looking for any documentation that will assist in correctly introducing an exchange server in each site then building it to clustering - then moving our users and public folders gradually.
January 22nd, 2008 4:41pm
Other than the subject line, you don't explain anything about your Exchange 2000 toploogy.
Here are some links to get you started, but if you'd like to post back with more specific details, we may be able to help further.
Coexisting with Exchange Server 2003 and Exchange 2000 Server
http://technet.microsoft.com/en-us/library/aa998604.aspx
Exchange Server 2007 and 2000/2003 systems management co-existence
http://msexchangeteam.com/archive/2006/10/09/429135.aspx
Outlook Web Access and Exchange 2007, Exchange 2003, and Exchange 2000 Coexistence
http://technet.microsoft.com/en-us/library/bb885041.aspx
Moving public folder replicas from Exchange 2000 to Exchange 2007
http://msexchangeteam.com/archive/2007/10/30/447339.aspx
How to Remove the Last Legacy Exchange Server from an Organization
http://technet.microsoft.com/en-us/library/bb288905.aspx
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2008 7:55pm
Setup: Mix of 2000 servers and 2003 Servers - with Exchange Server 2000 SP3 (Native Mode) Front and Backend Servers.
Domain:
1 Domain - Domain.pvt (fake)
Single Forest - Setup
Active Directory:
2000 mixed mode to support some NT legacy systems being removed prior to EX 2007 / Srv 2003 Roll Out
Exhange Servers:
3Servers - 1 Front End and2 Back End server all Exchange SP3 (Native Mode)
Site connector from City 1 (GROUP1) to City 2 (GROUP2)
City 1:
2 Active Directory 2000 Servers SP4 - Global Catalogues
1 Windows 2000 Server SP4 - Exchange Server
Exchange Server 2000 SP3 (Native Mode)
Administrative Group GROUP1
Conference Management Software - Book Conference rooms 3rd party
IIS - Web and FTP
DHCP - GROUP1
2 Windows 2003 Servers SP2 - Utility Backup Servers
HP EVA, Tape Tools
EMULEX
Double Take
Symatec Backup Exec 11d
SYmantec Enterprise Vault
Symantec Backup Exec Recovery
SQL 2005
1 Windows 2000 Server SP4 hosing RAS 2000,
2000 Certificate Services
RSA Services 6.1
FACSys Service (faxing)
1 Windows 2000 BES Server
BlackBerry Ent 4.1.4.16
Exchange 2000 Admin Tools
MS SQL Server standard
City 2:
1 Windows 2000 Server SP4 (AD and Exchange Server)
Active Directory 2000, Global Catalogue
Exchange Server 2000 SP3 (Native Mode)
Administrative Group GROUP2
IIS Web, FTP
DNS, WINS
DHCP - GROUP2
Remote Bride to DC1 - CITY1
Smart Host to DC1 - mail.domain.pvt
Service is forwarding mail via smart host
DMZ:
1 Windows 2000 Server SP4 with Exchange2000 ServerSP3
OWA 2000 Services only
IIS Web Services
1 Windows 2003 Server SP2
Mail Marshal Services
DNS Services External
FTP Services
City 2 forwards mail to Primay Exchange Server in CITY 1 that routes mail out to DMZ Utility server hosting MAIL Marshal for mail filtering in and out.
>>>>
My idea is to setup a 2003 ENT Server R2 SP1 into each city and DMZ and bring them online into AD - (Reading up on this for coexistence)
Then I want to introduce Exchange 2007 Servers with Clustering in both cities and to introduce High Availability in the future for fail over in case of 1 site going down or unavailable (we are working with ISP and other parties for this fail over design)
DMZ would host EDGE Services (would create another DMZ in city 2 for EDGE)
Each city would have the same configuration for full fail over services and high availability.
I am still researching correct hardware and number of servers required for roles knowing that I will have to quadruple the hardware for Clustering and High Availability fail over.
Thats pretty much my goal now trying to go about introducing the servers Exchange and 2003 Servers into AD while working with small groups of users to test and roll over
Key issue Public folders got over 200 of them
Free Busy, Schedule + and Conference board management and FACSys services.
January 22nd, 2008 10:32pm
Sounds like a fun project. You didn't mention routing groups. The site connectors have no effect on mail flow in exchange 2000 or 2003. If you dont have these in place, its probably too late now, but this would improve mail flow between sites. Keep in mind that 2007 creates a new routing group for only 2007 servers. It can get kinda tricky controlling mail flow.
If you want to cluster your email, you need two servers to do this. This could mean 4 with the two sites, but exchange 2007 is very robust and could likely house all your mailbox needs in one cluster, assuming the link to location #2 could support the rpc traffic (and you trust the link)
Youll want to have two CAS and two Hub transport for full fault tolerance. This makes 4 servers so far if you choose to install hub transport and cas on the same machines. Double this for the 2nd site if you must.
More info on combining cas and hub transport with NLB
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1443144&SiteID=17
Public folders are supported with exchange 2007. When you deploy you should jump right to sp1, as new tools are added to manage them.
Read msexchangeteam.org for any of your needs before you get lost in technet. They speak clearly and casually. Often easier to learn there first, and get technical bits later.
And feel free to w/b with any specific questions!
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2008 9:21am
Routing Groups are as follows:
ADministrative Groups:
CITY1 GROUP
Routing Groups (EXCH1 Server)
CITY1
Connectors
FACSys SMTP Connector (Primary Ex Server - EXCH1)
Intersite MAIL Connector - (Connects to Routing Group CITY2)
CITY1 SMTP Service
Members:
FE Server (Exchange)
EXCH1 (Primary Exchange Server)
CITY2 GROUP
Routing Groups (EXCH2 Server)
CITY2
Connectors
Intersite MAIL Connector - (Connects to Routing Group CITY1) -remote bridge head EXCH1
CITY2 SMTP Service (Forwards all mail to "Smart Host Address" - mail.domain.pvt)
Members:
EXCH2 (2nd Exchange Server on domain for CITY2)
SINGLE FOREST setup to move to SINGLE FOREST Exchange 2007
Does this info help?
January 23rd, 2008 6:38pm
Mike,
Thanks for your previous feedback,
My last post is just to fill in that gap you asked on routing groups.
---
I appreciate all the feedback and will review the posted link you provided and go to msexchangeteam.org for more info on my project.
Much thanks again.
Eric
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2008 6:45pm