Exchange 2000 to Exchange 2003
Current environment:
Win2000 domain running in mixed mode due to two NT40 BDC's at remote sites. All other remote sites authenticate here at the corp. office.
OWA running on a FE Win2000 Exch2000 server. Exchange 2000 running on BE Win2000 server.
Exchange 2000 is running on a member server.
Questions:
1) what issues would we encounter if we dont upgrade the NT40 servers prior to upgrading Exchange.
2) is it recommended to upgrade our Win2000 AD server to Win2003 prior to upgrading Exchange
3) do I need to run adprep (pending answer to #2)
4) what is the recommended sequence of upgrading:
- upgrade FE to Exchange 2003
- upgrade FE to Win2003
- upgrade Exchange 2000 server to Exchange 2003
- upgrade this Exchange server to Win2003
5) must you run Exchange 2003 SP1 before going to SP2?
Software/Hardware used:
Software/Hardware used:
ASKED:
August 17, 2006 10:56 AM
UPDATED:
August 18, 2006 2:37 PM
Answer Wiki:
1)How do those 2 remote sites currently configured to receive email?
2)Yes and make sure DNS and AD replication works, before upgrading to EXCH2K3
3)Forestprep and Domainprep
4)Upgrade EXCH2K FE & BE servers to WIN2K3, then to EXCH2K3
5)No just run SP2; it includes SP1
To see all answers submitted to the Answer Wiki: View Answer History.
the NT40 servers point to the Exchange server here at corporate as do all other remote locations. They are the only 2 remote locations that have servers….all other remote locations authenticate back to the corporate office.
the NT40 servers point to the Exchange server here at corporate as do all other remote locations. They are the only 2 remote locations that have servers….all other remote locations authenticate back to the corporate office.
How do the users in those 2 remote sites get their emails? Do they have AD accounts to logon with, to get to their mailboxes?
Is there a trust set up between NT & 2000 AD domains?
the remote locations have AD accounts…there is one domain, one forest….no trust relationship set.
In that case I think that you would be fine, unless you want to go native (mode).
The requirement for that is doing away with your NT4 BDCs. The question is can you remove them, or run upromote and just make them member servers?
What purpose are those BDCs serving?
we plan on replacing these servers (eventually) wih new ones and they will be setup as just plain workstations.
Just one clarification on a previous issue….we have 2 DC in our domain, both run Win2k. Our Exch server is a seperate member server running Win2K/Exch2K. Must our DC’s be upgraded to Win2003?
Yes, if you’re planning on upgrading to EXCH2K3, that requires schema extensions on AD.
You must stand up at least 1 Windows 2003 AD domain controller.
Would you recommended doing both? Any reprocussions if just one is upgraded?
>>Would you recommended doing both? Any reprocussions if just one is upgraded?
If you mean your EXCH servers, yes both need to be upgraded to WIN2K3, otherwise your EXCH FE/BE won’t work.
Even if it works (I’ve never tried this), you may run into email issues, which then you have go around fixing it.
I’m talking about the (2)Win2K DC’s…our Exch server is NOT a DC.
Based on 2) on your original post, I assumed you have 1 WIN2K AD domain controller.
No you don’t need to upgrade them to WIN2K3 now. As long as there is one 1 WIN2K3 domain controller to serve EX2K3 servers, you should be ok.
thanks….sorry about the confusion.
Now another twist…just found out I can replace the old front end server. So, what are the steps to move the current front-end to this new front-end?
So, here is our current environment:
(2) Win2k DC
(1) Exch2k FE server (member server) running Win2k
(1) Exch2k BE server (member server) running Win2k
The goal is to move from Exch2k to Exch2003…keep in mind I have a new server to use for a FE Exch server.