Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading to Exch2003 - New hardware

Status
Not open for further replies.

Bedpan

MIS
Sep 24, 2003
89
Hey folks... Thanks for taking the time to read/help out!

I have a Win2k AD (2 DC's), and Exch2k running on Windows 2000. I am in the midst of ordering a new Server and Exchange 2003 and I am trying to plan the migration.

As best I can tell the migration will go something like this

1. Setup new hardware with Win2k3 and join domain
2. Install Exchange 2003 and join Exchange 2000 organization
3. Move content to the new server
4. Decomission old server

I was hoping to find some more specific steps on doing this. I know MS had lots of guides along these linds from Exchange 5.5 to 2000, but everything I find for 2000 to 2003 seems to detail an inplace upgrade which I don't want to do.

Any thoughts?

Mike
 
Actually I think it's as easy as you stepped it out. After Exchange 2k3 is installed it's just a matter of moving users and replicating public folders to the new server.
 
Thanks TruBlu... I guess you are right, always nice to see the step by step though to insure things go smooooothly! The only area I am really concerned about would be the decommision of the old server.

Anyways I did find this article.

Covers the majority of it!

Mike
 
I'm doing something very similiar:

I currently have one server running Exchange 2003 SP1 on Windows server 2000 (server1). I have purchased a new server and installed Windows server 2003 and Exchange 2003 SP1 (server2).

I want to move all mailboxes (around 350) and public folders to server2 and take server1 off-line and reformat it; then bring server1 back up as Windows Server 2003 and Exchange 2003 front-end server (OWA).

Few questions:

1.) Does the new Exchange 2003 server (server2) need to be a domain controller or just a member server?

2.) Does server2 need to have DNS installed, running and pointing to itself? Or can I point it (Network Properties setup) at another of my DNS servers?

3.) Does new one (server2) need to be a Global Catalog server? Step 12 on shows that it should be. But that's for Ex2000.

4.) Does it need to have any FSMO roles on it? Step 15 on shows that it should be. But that's for Ex2000.

5.) Both server2 and OWA server1 will be behind a firewall. Should I open ports 25/110 on both and also ports 80 & 443 SSL on the OWA server?

Thanks for your help!

rwilliams3
 
Hey Rw...

Regarding your questions...

1 - 4: Generally it is recommended that you do not install Exchange on a Domain Controller. If your existing Exchange server is also a domain controller you will need to insure that you have another DC up and running before you remove this server. If the Existing Exchange server is not a DC then 1 - 4 do not really apply. FSMO, GC's are for Domain Controllers only and DNS can run on any server but again is recommended for DC's.

5: I am not sure on the exact port config. But here is a document that should walk you through it.

Good luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top