Exchange 2000 in  a 2003 Domain

Posted on 2006-06-01
Last Modified: 2010-03-06
I've got a situation where a company with an Exchange 2000 server in a Windows 2000 Native domain ran forest prep and domain prep for Exchange 2003 and forest and domain prep for domain upgrade to 2003 as well.

Then they installed one Exchange 2003 server and the 2000 exchange server's processor went to 100% and would not come down until the new 2003 exchange server was shut down. None of the domain controllers have been upgraded to 2003. I've done Exchange and domain upgrades before but not like this. I'm surprised that the Exchange 2000 box runs at all.

Is there a way to keep upgrading and get the exchange environment stablized? They do have a good backup from before they ran forest/domain preps.

Question by:Ponthecomputer
    LVL 12

    Accepted Solution

    Please have a look at this Article for more information before you plan your migration path ->
    Overview of operating system and Active Directory requirements for Exchange Server 2003.

    Exchange 2003 is very well supported in Windows 2000 mixed / native domain. The only thing you need to check is that your Windows 2000 machines should be SP3 or above. There are many companies those who have upgraded from Exchange 2000 to Exchange 2003, but dont want to upgrade from Active directory 2000 to Active Directory 2003.

    However, if you will have AD 2003, you can use some additional new features. There can be other reasons for 2k Exchange server's processor going to 100%, your migration path was not at all bad.

    Amit Aggarwal.
    LVL 1

    Author Comment

    Thanks. It was really bad.  I always upgrade the mail servers to 2003 and then remove every exchange 2000 server before I upgrade a domain to 2003.

    This was a case where the upgrade for the domain had been done first and they were having all kinds of trouble with the exchange 2000 servers.

    Every time I ran forest prep for Exch 2003 the 2000 servers would not work. RUS, Queues, and MTA would completely stop working. If services were stopped they would not restart.

    As a last resort I removed the old E2k servers via Adsiedit did a new install of E2k3, created new boxes for the users and restored the boxes with the brick level backups they had. All is working without a problem now.

    I'll award points as I learned that you can run Exchange 2000 on a 2003 domain. Some tweeks are necessary though and not a sure fire way to avoid problems.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Set up iPhone and iPad email signatures to always send in high-quality HTML with this step-by step guide.
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
    In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

    759 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

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now