Coexistance of 2003 DC and 2000 DC


I have four servers. One DC 2000, aother DC 2000, also running SQL 2000 (this one is a DC just for a backup purpose), third a member server running Exchange 2000, fourth a member server running SQL 2000. Our Exchange 2000 server is old and database is near 16GB so the server needs to be replaced with a newer server and Exchange 2003 software. Also our main domain controller is old too, so it would be a good thing to migrate this box to new 2003 server DC. So here are questions

The plan is to 1) Migrate Exchange to 2003 Server/Exchange 2003 server (member server) this will be a first step because of 16gb limitation.
                    2) Replace a 2000 primary DC with 2003 DC (Thus upgrading Active directory to 2003)

So the question is I still have another server wich is our SQl server and also a 2000 DC. Its still a good server and we are currently not planning to upgrade it for at least another two ears. Its running Windows 2000 and SQL 2000 with two apps. Once I have my primary Active Directory Server running windows 2003, and once I demote old Active Directory main DC is it OK to leave SQL server running DC 2000 for next couple of years? Should windows 2003 Domain Controller and windows 2000 Domain Controller coexist just fine till we are ready to migrate off this server, or do we have to uprade that one as well?

Thank you.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Absolutely, this is not a problem.  With 2003, there are 3 modes of AD operation:

Mixed Mode (NT4 Compatible)
2000 Native (when you have NO NT4 BDCs and you DO have 2000 DCs)
2003 Native (when you ONLY have 2003 DCs).

Here's some tips for the migration process:
Here are some links that should get you going for upgrading a 2000 domain to 2003:

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain;en-us;555040

Hotfixes to install before you run adprep /Forestprep on a Windows 2000 domain controller to prepare the Forest and domains for the addition of Windows Server 2003-based domain controllers | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server
Quote from the top of this article: "Several glossy Microsoft presenters have stated that all you need to do to complete a Windows 2003 Domain upgrade is run ADPREP and then upgrade away.  This may work for very small / simple environments but it is definitely not good advice for most companies.  After upgrading five servers in two unrelated domains and installing many fresh copies of 2003 I can say that I personally would not skip a single step in the process I have developed below."

How can I transfer some or all of the FSMO Roles from one DC to another?

How To Create or Move a Global Catalog in Windows 2000

[If you run Exchange 2000] Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers

Windows Server 2003 Upgrade Assistance Center

Migrating Exchange from old hardware to new hardware

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mavrukinAuthor Commented:
Thank you for the responce. There are many way to perform this upgrade and some articles from Microsoft are contradicting one another. Would you upgrade Exchange first and then DC or would you upgrade DC first and then Exchange?
Lee W, MVPTechnology and Business Process AdvisorCommented:
If your going from an old 2000 Exchange Server to a New 2003 Exchange server, I would really recommend reading the last link i posted., Migrating Exchange from old hardware to new hardware.

mavrukinAuthor Commented:
thank you.
Joseph NyaemaIndependednt ConsultantCommented:
Hi Mavrukin...

As the key work is migrating to new hardware,
I restrict my comments to migration.
Most of the the links above deal with upgrading..

obviously you need to be careful systematic in your approach to avoid the
not so obvious pit falls.

Remember this is an migration not an upgrade.

The link
but requires a lot of hardware.

Set aside some time (like the weekend) to perform the final migration of mailboxes
and let everyone know the migration is taking place.

before the actual dday prepare...

1) Install Windows 2003 server with service pack 1 (or R2) on your new hardware
and join the server to the domain.
NB:  JOIN (do not make it a dc) this avoids the mangled attributes issue in exchange server 2000

2) Install Exchange Server 2003 on the new server with Server 2003
joining the allready exising exchange 2000 organisation.
Ignore the error that pops up as this has been taken care of in SP1 and R2

3) Rehome the users to the Exchange 2003 server

4) rehome the public folders, offline addressbook folder, offlien address list server,
  shedule+ free busy folder, organisation forms folder, recipient update servive etc.
 to the exhcnage 2003 server as per;en-us;307917&Product=exch2k.

5)If necessary change router forwarding to reflect the new server as the new SMTP recipient
in the organisation.
May be, what probaly is easier is to give the new server the ip address formerly help by the exchange 2000 server.
Then give the exchange 2000 server a new IP.  Remeber to update DNS records to reflect the change

6)Let the two server run for a couple of days so that clients automatically get the new server
they have been rehomed to.

7)Uninstall Exchange 2000 from the organisation.
Because folders and roles have been rehomed, this should be smooth.

That takes care of exchange

Because no exchange 2000 server exist, we can now install server 20003
without worrying about exchange mangle attributes


make sure all your windows server 2000 server have service pack 4 for windows 2000
and Update Rollup 1 for service pack 4
doing this takes care of most of the updates require before you can run forestprep and adprep.

5)run the windows server 2003 adprep and forest prep on the first windows server 2000 domain controller
assuming it has all the fsmo roles and the schema can be modified.

6) On the other new server install windows server 2003 and make it a member of the 2000 domain.

7) Tranfer the FMSO roles and global catalog to the windows server 2003 dc.

8) install dns server on the 2003 domain controller and make it the primary dns for the site.

That prety much covers it.

May be some duplication with leew's comments but prety much covers it.
Will be glad to assist it you run into problems.

To make sure things run smoothly...
you may want to set up a lab environment first before going live
so that you know what to expect.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.