Hi,
I have inherited (something all techs say when the current organisation is not perfect) a Windows 2000 Server network, with 4 sites. There are four servers in total and some 100 machines.
The AD is a mess, and there are problems left right and centre with the existing setup.
We have purchased all new equipment to replace everything!
It's a massive task to upgrade all 4 sites (with 3 additional satellite offices) at once and we do not have the manpower to do it. Downtime is frowned upon.
What I was thinking of doing is either starting an entire new AD and slowly migrating services, or adding the new Win2003 servers one by one, migrating respective services at each site. Has anyone done the latter? How would you go about it?
Am I better off joining to existing (troubled) AD or creating a new one and somehow slowly migrating users/services...
- Follow via:
- RSS
- Email Alert
Question
0
Votes
Migrating 2000 AD to 2003 Enterprise, side by side
18th Jan 2007
Answers (1)
0
Votes
Migrating from 2000 to 2003
Leave the current 2000 AD in place and join the new 2003 server to the current environment as a BDC. The new 2003 will inherit all the permissions and users and services from the 2000 server. You can then promote the 2003 to DC and then decommission the 2000 Server.
23rd Jan 2007
Replies
We are upgrading from a mixed NT/W2K domain to W2K3 domain using a W2K AD in between the two. We created a new domain for the new servers and OS's to live on and created a trust between the two domains and run them in parallel. Now we are migrating the other W2K servers to the new domain (the OS upgrade will come later) and replacing the NT servers with upgraded W2K3 servers and doing so at a controlled rate. There have been some issues, but by keeping the old domain intact, users can "fall back" to it if needed. This has allowed for a relatively smooth transition from old to new. Not quite the answer you were looking for but a new domain would allow you to correct what you inherited.
tundraroamer
23rd Jan 2007
Thanks - this is what I suspected I should do... It will allow for a gradual transition on low manpower...
Thanks again.
Thanks again.
amerfilipovic
30th Jan 2007
This is exactly what I want to do. I have a 2003 server on order which will replace a 2000 server. Is there anywhere I can find step-by-step instructions on how to promote a server from BDC to PDC? Since you can have only one PDC per domain, this must involve demoting the old PDC first (to just a member server maybe), then promoting the new one, or ... ??
ctdak
23rd Jan 2007
only in NT is there only 1 PDC. In W2K Active Directory each DC is a peer. Roles can be assigned to DCs to scale for infrastructure requirements.
CG IT
23rd Jan 2007
My original training was in NT and I didn't know this change in DCs with 2000 since I only have a single server network. Thanks for the correction to my thinking.
One of the answers to the original question of this thread said to install the 2003 server as a BDC and then make it the DC once everything is migrated. So there are apparently still BDCs in 2000/2003. How do you make a new (2003) server a BDC in the first place? Then what procedure to you follow in promoting it to a DC?
One of the answers to the original question of this thread said to install the 2003 server as a BDC and then make it the DC once everything is migrated. So there are apparently still BDCs in 2000/2003. How do you make a new (2003) server a BDC in the first place? Then what procedure to you follow in promoting it to a DC?
ctdak
30th Jan 2007
PDC & BDC are no longer a part of W2K and newer versions. Drop those words when talking about newer OS's.
It's now Domain Controller DC. There is no "primary" or "main" DC. You can have more than one DC but they will be equal and have the ability to back each other up in case one fails. This is the same premises that the PDC/BDC were set up for in NT, now it is just made easier. A parallel might be PDC=DC but it does more than that.
I think there is some information at Microsoft that you should look at. You might start here: http://support.microsoft.com/kb/298107/en-us
It's now Domain Controller DC. There is no "primary" or "main" DC. You can have more than one DC but they will be equal and have the ability to back each other up in case one fails. This is the same premises that the PDC/BDC were set up for in NT, now it is just made easier. A parallel might be PDC=DC but it does more than that.
I think there is some information at Microsoft that you should look at. You might start here: http://support.microsoft.com/kb/298107/en-us
tundraroamer
30th Jan 2007
Do you happen to know any white paper/Article explaining migration from 2000 to 2003. I have 2003 Ent 64x ready. I have to joing it to 2000 doamin but wnated to know little more before I go further.
rsahni@...
4th Apr 2007
I recently joined a new Win 2003 DC to a Win 2000 domain. I discovered that before joining the 2003 server you have to run some Active Directory utilities to prepare the 2000 forest and domain to make it work with 2003. Here is a helpful website explaining this.
http://www.petri.co.il/windows_2003_adprep.htm
http://www.petri.co.il/windows_2003_adprep.htm
ctdak
4th Apr 2007
