Migrating to Windows 2003 Server

[Allison]

I currently have 3 domain controllers. Two DCs are Windows 2000 Server and
the other DC is Windows 2003 Enterprise Servers. I want to migrate both
Windows 2000 DCs to Windows 2003 DCs, change their IP addresses, and put
them on new hardware. Here is my course of action. Can anyone tell me if
I'm doing this correct.

1. On the 1st new hardware... Install Windows 2003 Enterprise Server with
DNS, configure new IP address, and promote it to a DC.
2. Demote one of the old Windows 2000 Servers and disjoin from domain.
3. On the 2nd new hardware... Install Windows 2003 Enterprise Server with
DNS, configure new IP address, and promote it to a DC.
4. Transfer all FSMO roles over from old Win2k server to new Win2k3 server
along with Global Catalog.
5. Demote the last Windows 2000 Server and disjoin from domain.
6. Add new DNS entries for my XP and Win2k workstations and remove old DNS
entries.

I want to do this properly and not mess up Active Directory and my clients
connectivity to the domain. Will this work or am I forgetting any important
steps?

Thanks

 

[Tomasz Onyszko]

I currently have 3 domain controllers. Two DCs are Windows 2000 Server and
the other DC is Windows 2003 Enterprise Servers. I want to migrate both
Windows 2000 DCs to Windows 2003 DCs, change their IP addresses, and put
them on new hardware. Here is my course of action. Can anyone tell me if
I'm doing this correct.

1. On the 1st new hardware... Install Windows 2003 Enterprise Server with
DNS, configure new IP address, and promote it to a DC.
2. Demote one of the old Windows 2000 Servers and disjoin from domain.
3. On the 2nd new hardware... Install Windows 2003 Enterprise Server with
DNS, configure new IP address, and promote it to a DC.
4. Transfer all FSMO roles over from old Win2k server to new Win2k3 server
along with Global Catalog.
5. Demote the last Windows 2000 Server and disjoin from domain.
6. Add new DNS entries for my XP and Win2k workstations and remove old DNS
entries.

I want to do this properly and not mess up Active Directory and my clients
connectivity to the domain. Will this work or am I forgetting any important
steps?

I will make a little change to Your plan:
1. Move existing FSMO roles from Windows 2000 DCs to existing Windows
2003 DC
2. Install both new DCs and configure its properties, promote them as a
DC. Make them GC if needed.
3. Swith off Windows 2000 boxes (or just stop netlogon service as some
other folk on this newsgroup suggested) and test Your environment if all
is working fine.
4. Remove dc role from windows 2000 boxes and disjoin them from the
domain if needed

 

[Allison]

1. I assume the only thing that happens when you turn off the Netlogon
service is that users cannot authenticate to the DC, correct?

2. If the DC is in this state, can I demote the DC to a member server or do
I have to have the Netlogon service running in order for it to demote
properly?

thanks

 

[Tomasz Onyszko]

1. I assume the only thing that happens when you turn off the Netlogon
service is that users cannot authenticate to the DC, correct?

In general - Yes

2. If the DC is in this state, can I demote the DC to a member server or do
I have to have the Netlogon service running in order for it to demote
properly?

Netlogon should be running - but one of the first steps of dcpromo when
demotation takes place is to stop netlogon

 

[Allison]

thanks for your help Tomasz

In general - Yes


Netlogon should be running - but one of the first steps of dcpromo when
demotation takes place is to stop netlogon