We just started the upgrading from NT4 and Exchange 5.5 process. We have one PDC and one BDC. I have successfully...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
upgraded the PDC to Windows 2003 DC AD with DNS and DHCP, but have not touched the DBC as it hosts the Exchange 5.5. We are doing an "in-place" upgrade since there is no new hardware involved. Could you recommend steps that allow for the upgrade of the BDC which must go up to the 2003 version, along with the upgrade of Exchange from 5.5 to Exchange 2003? Unfortunately, you are going to have to change your plans, as you cannot do an in-place upgrade from NT4/Exchange 5.5 to Windows 2003/Exchange 2003. One way you could go would be to upgrade the OS from NT4 to Windows 2000. Then, upgrade Exchange 5.5 to Exchange 2000. Then, upgrade Exchange 2000 to Exchange 2003. Finally, upgrade Windows 2000 to Windows 2003. There are two primary reasons why you can only do it this way:
1. You cannot do an in-place upgrade of Exchange 5.5 to Exchange 2003.
2. Exchange 2003 is the ONLY version of Exchange that can run on Windows 2003.
To upgrade from Exchange Server 5.5 to Exchange Server 2003, you must first introduce an Exchange 2003 Server into the Exchange 5.5 site, and then move Exchange resources such as mailboxes and public folders to the Exchange 2003 server. You can use the Exchange Server Deployment Tools to migrate from Exchange 5.5 to Exchange 2003.
I also strongly recommend against running Exchange on a domain controller. First, both Active Directory and Exchange are resource-intensive applications. Putting them both on the same box means that they will likely fight each other for resources. Second, it means that your Exchange admins now need to have local administrative rights on your domain controllers, which effectively makes them domain admins (and gives them a much higher level of privileges than they actually need). Third, a security bug that compromises Exchange could put your Active Directory at risk (if I compromise an application running on a DC, there is a good chance I will be able to compromise the DC, too).
Related Q&A from SearchExchange Staff
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.