Replacing Windows 2000 domain controller with new 2003 server

[nf]

I have read very good post on how to perform my migration but i have just a
few more questions on my situation. My old DC server, currently running W2K,
is also the DNS server, DHCP server, print server, and SMTP server (for alert
messaging).

After i add my new server to the domain, prep my old server domain, dcpromo
new server, enable GC, install DNS on new server, install DHCP ....I would
like to be able to rename the new server to the old server's name, including
the same IP address (for other reasons)...is that possible?

[Danny Sanders]

> After i add my new server to the domain, prep my old server domain,
> dcpromo
> new server, enable GC, install DNS on new server, install DHCP ....I would
> like to be able to rename the new server to the old server's name,
> including
> the same IP address (for other reasons)...is that possible?

Do you have a second DC in the domain now?

hth
DDS


"nf" <nf@discussions.microsoft.com> wrote in message
news:F1B2C78E-BFDC-4A6D-AEEA-F993658063D8@microsoft.com...
>I have read very good post on how to perform my migration but i have just a
> few more questions on my situation. My old DC server, currently running
> W2K,
> is also the DNS server, DHCP server, print server, and SMTP server (for
> alert
> messaging).
>
> After i add my new server to the domain, prep my old server domain,
> dcpromo
> new server, enable GC, install DNS on new server, install DHCP ....I would
> like to be able to rename the new server to the old server's name,
> including
> the same IP address (for other reasons)...is that possible?

[David Shen [MSFT]]

Dear Customer,

Thank you for posting in newsgroup.

According to the description, you concern is that if the name of the new
domain controller can be changed to that of the old domain controller. If I
have any misunderstanding, please feel free to let me know.

Before we move on, I would like to confirm some information with you
firstly.

Information Needed:
======================

1. Do you have a second domain controller before you add the new domain
controller to the current domain?

2. How many domain controllers in the domain now? And what is the operation
system of each domain controller?

3. Since you mentioned that you have prepared the old domain controller, I
wonder if you have run "Adprep /forestprep" and "Adprep /domainprep" on the
old domain controller?

4. What is the Schema level of the domain now?

You may verify the Active Directory verify the schema level by using the
Adsiedit.exe or the Ldp.exe to view the objectVersion attribute in the
properties of the cn=schema, cn=configuration, dc= <domain> partition.

The Schema Version ObjectVersion values and corresponding operating system
support level:

13=Microsoft Windows 2000
30=Original release version of Microsoft Windows Server 2003 and Microsoft
Windows Server 2003 Service Pack 1(SP1)
31=Microsoft Windows Server 2003 R2
44=Microsoft Windows Server 2008

Analysis:
===================

If you just want to replace the old domain controller with the new domain
controller, it is possible to rename the new domain controller to that of
the old one.

please note: there couldn't exist 2 domain controllers with the same name
in the domain. In other word, you need to demote the old domain controller
first, and then disjoin it from the domain. Afterwards, you may rename the
new domain controller and the IP address to that of the old one.

Here are some suggestion which may be helpful for you. (assume that the
Schema level is Windows Server 2003 now)

Please note:
The renaming process will cause some downtime of the domain, the domain
controller could be not available for the clients to process the
authentication request during the renaming process. I would like suggest
that you perform the following steps in the spare time.

Suggestion:
===================

1. Please ensure that the new domain controller that you want to rename was
enabled with Global Catalog, all the 5 FSMO roles has been transferred from
the old domain controller to the new one in the domain.

Please refer to:

Enable or disable a global catalog
http://technet2.microsoft.com/window...c-ef32-4b8e-b4
c4-e73910575f611033.mspx?mfr=true

How to view and transfer FSMO roles in the graphical user interface
http://support.microsoft.com/kb/255690

2. Please ensure that all the server roles (ex. DNS, DHCP, Print server,
SMTP) have been transferred to the new domain controller.

3. After that, you may run "dcpromo" on the old domain controller to demote
it to be a member server first, and then you may disjoin the old domain
controller from the current domain if possible.

Please refer to:

Demote a domain controller
http://technet2.microsoft.com/window...0-552f-4b94-9e
ce-f550388976571033.mspx?mfr=true

4. Please ensure that the computer account of the old domain controller has
been removed from the domain. You may check the "Domain Controller" and
"Computers" containers in "Active Directory Users and Computers" console on
the new domain controller.

5. Please ensure that all the source records (ex. A record and SRV record)
of the old domain controller have been removed in the DNS console.

6. Please ensure that the dynamic updates have been enabled both on the
Forward Lookup Zone and Reverse Lookup Zone in the DNS console of the new
domain controller.

Please refer to:

How to configure DNS dynamic updates in Windows Server 2003
http://support.microsoft.com/kb/816592

7. Then you may begin to rename the new domain controller with System
Properties GUI.

Please note:

To rename a domain controller, you need to logon the new domain controller
with administrative account which is a member of the "Domain Admins" group
or the "Enterprise Admins" group.

Steps to rename a domain controller using System Properties

a. Click Start, and then click Control Panel.
b. In Control Panel, double-click System Properties.
c. On the Computer Name tab, click Change.
d. Click OK to acknowledge that renaming the domain controller may cause it
to become temporarily unavailable to users and computers.
e. Under Computer Name, type the new name.
f. Click OK to close the System Properties dialog box.
g. If you are prompted, provide the user name and password for an account
with Domain Admin or Enterprise Admin credentials.
h. Restart the domain controller.

8. Then you may change the IP address of the new domain controller to that
of the old domain controller. Please note: you need to make "Preferred DNS
server" point to the new domain controller itself.

9. Please run "net stop netlogon" and then "net start netlogon" on the new
domain controller to manually make it register the SRV records in the DNS.

For more Reference:
==================

Rename a domain controller
http://technet2.microsoft.com/window...a-f0d2-47d5-b0
ea-989081ce62be1033.mspx?mfr=true

Renaming a Domain Controller
http://technet2.microsoft.com/window...c-6841-40e0-b9
03-fb3838f6ac261033.mspx?mfr=true

How to Rename a Windows 2000 Domain Controller
http://support.microsoft.com/kb/296592

I look forward to your reply and thank you for your time.

David Shen
Microsoft Online Partner Support

[nf]

Yes, i do. Its also another windows 2000 server.

"Danny Sanders" wrote:

> > After i add my new server to the domain, prep my old server domain,
> > dcpromo
> > new server, enable GC, install DNS on new server, install DHCP ....I would
> > like to be able to rename the new server to the old server's name,
> > including
> > the same IP address (for other reasons)...is that possible?
>
> Do you have a second DC in the domain now?
>
> hth
> DDS
>
>
> "nf" <nf@discussions.microsoft.com> wrote in message
> news:F1B2C78E-BFDC-4A6D-AEEA-F993658063D8@microsoft.com...
> >I have read very good post on how to perform my migration but i have just a
> > few more questions on my situation. My old DC server, currently running
> > W2K,
> > is also the DNS server, DHCP server, print server, and SMTP server (for
> > alert
> > messaging).
> >
> > After i add my new server to the domain, prep my old server domain,
> > dcpromo
> > new server, enable GC, install DNS on new server, install DHCP ....I would
> > like to be able to rename the new server to the old server's name,
> > including
> > the same IP address (for other reasons)...is that possible?
>
>
>

[nf]

1. yes, an additional windows 2000 server
2. 2, both windows 2000 server
3. not yet but plan too, should i run on both domain controlers?
4. Windows 2000 mixed in a windwos 2000 forest

I will look throught he rest of your post today. thanks

"David Shen [MSFT]" wrote:

> Dear Customer,
>
> Thank you for posting in newsgroup.
>
> According to the description, you concern is that if the name of the new
> domain controller can be changed to that of the old domain controller. If I
> have any misunderstanding, please feel free to let me know.
>
> Before we move on, I would like to confirm some information with you
> firstly.
>
> Information Needed:
> ======================
>
> 1. Do you have a second domain controller before you add the new domain
> controller to the current domain?
>
> 2. How many domain controllers in the domain now? And what is the operation
> system of each domain controller?
>
> 3. Since you mentioned that you have prepared the old domain controller, I
> wonder if you have run "Adprep /forestprep" and "Adprep /domainprep" on the
> old domain controller?
>
> 4. What is the Schema level of the domain now?
>
> You may verify the Active Directory verify the schema level by using the
> Adsiedit.exe or the Ldp.exe to view the objectVersion attribute in the
> properties of the cn=schema, cn=configuration, dc= <domain> partition.
>
> The Schema Version ObjectVersion values and corresponding operating system
> support level:
>
> 13=Microsoft Windows 2000
> 30=Original release version of Microsoft Windows Server 2003 and Microsoft
> Windows Server 2003 Service Pack 1(SP1)
> 31=Microsoft Windows Server 2003 R2
> 44=Microsoft Windows Server 2008
>
> Analysis:
> ===================
>
> If you just want to replace the old domain controller with the new domain
> controller, it is possible to rename the new domain controller to that of
> the old one.
>
> please note: there couldn't exist 2 domain controllers with the same name
> in the domain. In other word, you need to demote the old domain controller
> first, and then disjoin it from the domain. Afterwards, you may rename the
> new domain controller and the IP address to that of the old one.
>
> Here are some suggestion which may be helpful for you. (assume that the
> Schema level is Windows Server 2003 now)
>
> Please note:
> The renaming process will cause some downtime of the domain, the domain
> controller could be not available for the clients to process the
> authentication request during the renaming process. I would like suggest
> that you perform the following steps in the spare time.
>
> Suggestion:
> ===================
>
> 1. Please ensure that the new domain controller that you want to rename was
> enabled with Global Catalog, all the 5 FSMO roles has been transferred from
> the old domain controller to the new one in the domain.
>
> Please refer to:
>
> Enable or disable a global catalog
> http://technet2.microsoft.com/window...c-ef32-4b8e-b4
> c4-e73910575f611033.mspx?mfr=true
>
> How to view and transfer FSMO roles in the graphical user interface
> http://support.microsoft.com/kb/255690
>
> 2. Please ensure that all the server roles (ex. DNS, DHCP, Print server,
> SMTP) have been transferred to the new domain controller.
>
> 3. After that, you may run "dcpromo" on the old domain controller to demote
> it to be a member server first, and then you may disjoin the old domain
> controller from the current domain if possible.
>
> Please refer to:
>
> Demote a domain controller
> http://technet2.microsoft.com/window...0-552f-4b94-9e
> ce-f550388976571033.mspx?mfr=true
>
> 4. Please ensure that the computer account of the old domain controller has
> been removed from the domain. You may check the "Domain Controller" and
> "Computers" containers in "Active Directory Users and Computers" console on
> the new domain controller.
>
> 5. Please ensure that all the source records (ex. A record and SRV record)
> of the old domain controller have been removed in the DNS console.
>
> 6. Please ensure that the dynamic updates have been enabled both on the
> Forward Lookup Zone and Reverse Lookup Zone in the DNS console of the new
> domain controller.
>
> Please refer to:
>
> How to configure DNS dynamic updates in Windows Server 2003
> http://support.microsoft.com/kb/816592
>
> 7. Then you may begin to rename the new domain controller with System
> Properties GUI.
>
> Please note:
>
> To rename a domain controller, you need to logon the new domain controller
> with administrative account which is a member of the "Domain Admins" group
> or the "Enterprise Admins" group.
>
> Steps to rename a domain controller using System Properties
>
> a. Click Start, and then click Control Panel.
> b. In Control Panel, double-click System Properties.
> c. On the Computer Name tab, click Change.
> d. Click OK to acknowledge that renaming the domain controller may cause it
> to become temporarily unavailable to users and computers.
> e. Under Computer Name, type the new name.
> f. Click OK to close the System Properties dialog box.
> g. If you are prompted, provide the user name and password for an account
> with Domain Admin or Enterprise Admin credentials.
> h. Restart the domain controller.
>
> 8. Then you may change the IP address of the new domain controller to that
> of the old domain controller. Please note: you need to make "Preferred DNS
> server" point to the new domain controller itself.
>
> 9. Please run "net stop netlogon" and then "net start netlogon" on the new
> domain controller to manually make it register the SRV records in the DNS.
>
> For more Reference:
> ==================
>
> Rename a domain controller
> http://technet2.microsoft.com/window...a-f0d2-47d5-b0
> ea-989081ce62be1033.mspx?mfr=true
>
> Renaming a Domain Controller
> http://technet2.microsoft.com/window...c-6841-40e0-b9
> 03-fb3838f6ac261033.mspx?mfr=true
>
> How to Rename a Windows 2000 Domain Controller
> http://support.microsoft.com/kb/296592
>
> I look forward to your reply and thank you for your time.
>
> David Shen
> Microsoft Online Partner Support
>
>

[nf]

Dave,

Just to let you know, I ran ldp.exe on that server and came up with the
following. No mention of the 13 value though.

ld = ldap_open("ntserver2", 389);
Established connection to ntserver2.
Retrieving base DSA information...
Result <0>: (null)
Matched DNs:
Getting 1 entries:
>> Dn:
1> currentTime: 3/20/2008 7:46:27 Eastern Standard Time Eastern Daylight
Time;
1> subschemaSubentry:
CN=Aggregate,CN=Schema,CN=Configuration,DC=brahminoffice,DC=com;
1> dsServiceName: CN=NTDS
Settings,CN=NTSERVER2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=brahminoffice,DC=com;
3> namingContexts: CN=Schema,CN=Configuration,DC=brahminoffice,DC=com;
CN=Configuration,DC=brahminoffice,DC=com; DC=brahminoffice,DC=com;
1> defaultNamingContext: DC=brahminoffice,DC=com;
1> schemaNamingContext: CN=Schema,CN=Configuration,DC=brahminoffice,DC=com;
1> configurationNamingContext: CN=Configuration,DC=brahminoffice,DC=com;
1> rootDomainNamingContext: DC=brahminoffice,DC=com;
16> supportedControl: 1.2.840.113556.1.4.319; 1.2.840.113556.1.4.801;
1.2.840.113556.1.4.473; 1.2.840.113556.1.4.528; 1.2.840.113556.1.4.417;
1.2.840.113556.1.4.619; 1.2.840.113556.1.4.841; 1.2.840.113556.1.4.529;
1.2.840.113556.1.4.805; 1.2.840.113556.1.4.521; 1.2.840.113556.1.4.970;
1.2.840.113556.1.4.1338; 1.2.840.113556.1.4.474; 1.2.840.113556.1.4.1339;
1.2.840.113556.1.4.1340; 1.2.840.113556.1.4.1413;
2> supportedLDAPVersion: 3; 2;
12> supportedLDAPPolicies: MaxPoolThreads; MaxDatagramRecv;
MaxReceiveBuffer; InitRecvTimeout; MaxConnections; MaxConnIdleTime;
MaxActiveQueries; MaxPageSize; MaxQueryDuration; MaxTempTableSize;
MaxResultSetSize; MaxNotificationPerConn;
1> highestCommittedUSN: 1437282;
2> supportedSASLMechanisms: GSSAPI; GSS-SPNEGO;
1> dnsHostName: ntserver2.brahminoffice.com;
1> ldapServiceName: brahminoffice.com:ntserver2$@BRAHMINOFFICE.COM;
1> serverName:
CN=NTSERVER2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=brahminoffice,DC=com;
2> supportedCapabilities: 1.2.840.113556.1.4.800; 1.2.840.113556.1.4.1791;
1> isSynchronized: TRUE;
1> isGlobalCatalogReady: TRUE;
-----------

"David Shen [MSFT]" wrote:

> Dear Customer,
>
> Thank you for posting in newsgroup.
>
> According to the description, you concern is that if the name of the new
> domain controller can be changed to that of the old domain controller. If I
> have any misunderstanding, please feel free to let me know.
>
> Before we move on, I would like to confirm some information with you
> firstly.
>
> Information Needed:
> ======================
>
> 1. Do you have a second domain controller before you add the new domain
> controller to the current domain?
>
> 2. How many domain controllers in the domain now? And what is the operation
> system of each domain controller?
>
> 3. Since you mentioned that you have prepared the old domain controller, I
> wonder if you have run "Adprep /forestprep" and "Adprep /domainprep" on the
> old domain controller?
>
> 4. What is the Schema level of the domain now?
>
> You may verify the Active Directory verify the schema level by using the
> Adsiedit.exe or the Ldp.exe to view the objectVersion attribute in the
> properties of the cn=schema, cn=configuration, dc= <domain> partition.
>
> The Schema Version ObjectVersion values and corresponding operating system
> support level:
>
> 13=Microsoft Windows 2000
> 30=Original release version of Microsoft Windows Server 2003 and Microsoft
> Windows Server 2003 Service Pack 1(SP1)
> 31=Microsoft Windows Server 2003 R2
> 44=Microsoft Windows Server 2008
>
> Analysis:
> ===================
>
> If you just want to replace the old domain controller with the new domain
> controller, it is possible to rename the new domain controller to that of
> the old one.
>
> please note: there couldn't exist 2 domain controllers with the same name
> in the domain. In other word, you need to demote the old domain controller
> first, and then disjoin it from the domain. Afterwards, you may rename the
> new domain controller and the IP address to that of the old one.
>
> Here are some suggestion which may be helpful for you. (assume that the
> Schema level is Windows Server 2003 now)
>
> Please note:
> The renaming process will cause some downtime of the domain, the domain
> controller could be not available for the clients to process the
> authentication request during the renaming process. I would like suggest
> that you perform the following steps in the spare time.
>
> Suggestion:
> ===================
>
> 1. Please ensure that the new domain controller that you want to rename was
> enabled with Global Catalog, all the 5 FSMO roles has been transferred from
> the old domain controller to the new one in the domain.
>
> Please refer to:
>
> Enable or disable a global catalog
> http://technet2.microsoft.com/window...c-ef32-4b8e-b4
> c4-e73910575f611033.mspx?mfr=true
>
> How to view and transfer FSMO roles in the graphical user interface
> http://support.microsoft.com/kb/255690
>
> 2. Please ensure that all the server roles (ex. DNS, DHCP, Print server,
> SMTP) have been transferred to the new domain controller.
>
> 3. After that, you may run "dcpromo" on the old domain controller to demote
> it to be a member server first, and then you may disjoin the old domain
> controller from the current domain if possible.
>
> Please refer to:
>
> Demote a domain controller
> http://technet2.microsoft.com/window...0-552f-4b94-9e
> ce-f550388976571033.mspx?mfr=true
>
> 4. Please ensure that the computer account of the old domain controller has
> been removed from the domain. You may check the "Domain Controller" and
> "Computers" containers in "Active Directory Users and Computers" console on
> the new domain controller.
>
> 5. Please ensure that all the source records (ex. A record and SRV record)
> of the old domain controller have been removed in the DNS console.
>
> 6. Please ensure that the dynamic updates have been enabled both on the
> Forward Lookup Zone and Reverse Lookup Zone in the DNS console of the new
> domain controller.
>
> Please refer to:
>
> How to configure DNS dynamic updates in Windows Server 2003
> http://support.microsoft.com/kb/816592
>
> 7. Then you may begin to rename the new domain controller with System
> Properties GUI.
>
> Please note:
>
> To rename a domain controller, you need to logon the new domain controller
> with administrative account which is a member of the "Domain Admins" group
> or the "Enterprise Admins" group.
>
> Steps to rename a domain controller using System Properties
>
> a. Click Start, and then click Control Panel.
> b. In Control Panel, double-click System Properties.
> c. On the Computer Name tab, click Change.
> d. Click OK to acknowledge that renaming the domain controller may cause it
> to become temporarily unavailable to users and computers.
> e. Under Computer Name, type the new name.
> f. Click OK to close the System Properties dialog box.
> g. If you are prompted, provide the user name and password for an account
> with Domain Admin or Enterprise Admin credentials.
> h. Restart the domain controller.
>
> 8. Then you may change the IP address of the new domain controller to that
> of the old domain controller. Please note: you need to make "Preferred DNS
> server" point to the new domain controller itself.
>
> 9. Please run "net stop netlogon" and then "net start netlogon" on the new
> domain controller to manually make it register the SRV records in the DNS.
>
> For more Reference:
> ==================
>
> Rename a domain controller
> http://technet2.microsoft.com/window...a-f0d2-47d5-b0
> ea-989081ce62be1033.mspx?mfr=true
>
> Renaming a Domain Controller
> http://technet2.microsoft.com/window...c-6841-40e0-b9
> 03-fb3838f6ac261033.mspx?mfr=true
>
> How to Rename a Windows 2000 Domain Controller
> http://support.microsoft.com/kb/296592
>
> I look forward to your reply and thank you for your time.
>
> David Shen
> Microsoft Online Partner Support
>
>

[Danny Sanders]

I would do this on a Friday evening:
Run dcpromo on the server you want to replace, to remove AD
Rename and change the IP address of this server.
Let this change replicate. If you set up the down time with the users you
can do the rest Saturday morning.
Next rename and change the IP address of the new server to match the old and
run dcpromo. Setup DNS, DHCP, and make it a global catalog and you should be
done.


hth
DDS

"nf" <nf@discussions.microsoft.com> wrote in message
news:BA06FCF9-EA69-41CE-B2A5-B88B9D575978@microsoft.com...
> Yes, i do. Its also another windows 2000 server.
>
> "Danny Sanders" wrote:
>
>> > After i add my new server to the domain, prep my old server domain,
>> > dcpromo
>> > new server, enable GC, install DNS on new server, install DHCP ....I
>> > would
>> > like to be able to rename the new server to the old server's name,
>> > including
>> > the same IP address (for other reasons)...is that possible?
>>
>> Do you have a second DC in the domain now?
>>
>> hth
>> DDS
>>
>>
>> "nf" <nf@discussions.microsoft.com> wrote in message
>> news:F1B2C78E-BFDC-4A6D-AEEA-F993658063D8@microsoft.com...
>> >I have read very good post on how to perform my migration but i have
>> >just a
>> > few more questions on my situation. My old DC server, currently running
>> > W2K,
>> > is also the DNS server, DHCP server, print server, and SMTP server (for
>> > alert
>> > messaging).
>> >
>> > After i add my new server to the domain, prep my old server domain,
>> > dcpromo
>> > new server, enable GC, install DNS on new server, install DHCP ....I
>> > would
>> > like to be able to rename the new server to the old server's name,
>> > including
>> > the same IP address (for other reasons)...is that possible?
>>
>>
>>

[nf]

thank you for the info

"Danny Sanders" wrote:

> I would do this on a Friday evening:
> Run dcpromo on the server you want to replace, to remove AD
> Rename and change the IP address of this server.
> Let this change replicate. If you set up the down time with the users you
> can do the rest Saturday morning.
> Next rename and change the IP address of the new server to match the old and
> run dcpromo. Setup DNS, DHCP, and make it a global catalog and you should be
> done.
>
>
> hth
> DDS
>
> "nf" <nf@discussions.microsoft.com> wrote in message
> news:BA06FCF9-EA69-41CE-B2A5-B88B9D575978@microsoft.com...
> > Yes, i do. Its also another windows 2000 server.
> >
> > "Danny Sanders" wrote:
> >
> >> > After i add my new server to the domain, prep my old server domain,
> >> > dcpromo
> >> > new server, enable GC, install DNS on new server, install DHCP ....I
> >> > would
> >> > like to be able to rename the new server to the old server's name,
> >> > including
> >> > the same IP address (for other reasons)...is that possible?
> >>
> >> Do you have a second DC in the domain now?
> >>
> >> hth
> >> DDS
> >>
> >>
> >> "nf" <nf@discussions.microsoft.com> wrote in message
> >> news:F1B2C78E-BFDC-4A6D-AEEA-F993658063D8@microsoft.com...
> >> >I have read very good post on how to perform my migration but i have
> >> >just a
> >> > few more questions on my situation. My old DC server, currently running
> >> > W2K,
> >> > is also the DNS server, DHCP server, print server, and SMTP server (for
> >> > alert
> >> > messaging).
> >> >
> >> > After i add my new server to the domain, prep my old server domain,
> >> > dcpromo
> >> > new server, enable GC, install DNS on new server, install DHCP ....I
> >> > would
> >> > like to be able to rename the new server to the old server's name,
> >> > including
> >> > the same IP address (for other reasons)...is that possible?
> >>
> >>
> >>
>
>
>

[David Shen [MSFT]]

Hello NF,

Thanks for your reply.

According to the feedback, it seems that you want to add a new domain
controller into the current Windows 2000 domain, and then replace the old
domain controller with the new one. You concern is that if the "Adprep"
need to be run on the domain controllers. And you didn't find the Schema
ObjectVesion number with LDP.exe utility.

If there is any misunderstanding, please feel free to let me know.

Based on the research, here is some information which may be helpful for
you.

Analysis and Suggestion:
======================

1. Although there exist 2 Windows 2000 domain controllers in the current
domain now, there is no need to run "Adprep /forestprep" and "Adprep
/domainprep" on both of the 2 domain controllers. To extend the Windows
2000 forest and domain schema with the adprep utility, you just run "Adprep
/forestprep" and "Adprep /domainprep" on the domain controller which holds
the Schema master and the infrastructure master role (generally it is the
first domain controller in the domain). After that, all the update
information will be replicated to the other domain controller with the
Active Directory Replication.

You may refer to the following KB to identify which domain controller holds
the FSMO roles.

How to view and transfer FSMO roles in the graphical user interface
http://support.microsoft.com/kb/255690

Please note: ADPREP command-line tool is in Windows Server 2003
installation disc (X:\I386\ADPREP.EXE).

It is better for you to wait for some time since the it cost time to
replicate the update Schema information to another domain controller, the
time will be decided by the network bandwidth and the network utilization.

2. After preparing the schema of the domain, I would like to give you some
suggestion that you use the LDP.exe utility to verify the Schema level of
the Active Directory. Please view the "ObjectVersion" attribute in the
properties of the "CN=schema, CN=configuration, DC= <domain>, DC=<com>"
partition.

Steps:

a. Start -> Run -> ldp.exe -> open the Ldp console
b. Click Connection, and then click Connect.
c. Type the server name of the domain controller that you want to connect
to, and the port (389).
d. Click Connection, and then click Bind.
e. Type the user name, password, and domain, and then click OK. (you may
use domain administrator credential to bind.)
f. Click View, and then click Tree.
g. In the "BaseDN" list box, select
"CN=Schema,CN=Configuration,DC=<domain>,DC=<com>", and click OK.
h. Check the objectVersion value from the output on the right side window.

Hope all the information will be helpful.

Thanks for your time.

David Shen
Microsoft Online Partner Support

[David Shen [MSFT]]

Hello NF,

I'd like to check how things are going. Did you have the chance to try the
troubleshooting steps? If you have any other questions, please do not
hesitate to let me know. I look forward to your further updates.

David Shen
Microsoft Online Partner Support

[nf]

Not yet David, I have had other issues to deal with for the next few weeks. I
just wanted to be prepared for this migration ahead of time.

Thank you for the information though

"David Shen [MSFT]" wrote:

> Hello NF,
>
> I'd like to check how things are going. Did you have the chance to try the
> troubleshooting steps? If you have any other questions, please do not
> hesitate to let me know. I look forward to your further updates.
>
> David Shen
> Microsoft Online Partner Support
>
>

[David Shen [MSFT]]

Hello NF,

Thanks for your reply.

I hope all the information that I have provided will be helpful for the
migration. If you have any question about it, please just feel free let me
know.

David Shen
Microsoft Online Partner Support

[nf]

David,

Just started get back into this project. I have gone as far as getting the
new server to the point where its a domain controller now. Should I move the
DHCP and Print services to this server prior to me changing the name to match
the old server its replacing or wait till the rename?

"David Shen [MSFT]" wrote:

> Hello NF,
>
> Thanks for your reply.
>
> I hope all the information that I have provided will be helpful for the
> migration. If you have any question about it, please just feel free let me
> know.
>
> David Shen
> Microsoft Online Partner Support
>
>

[David Shen [MSFT]]

Hello NF,

Thanks for your reply.

For the further concern about the migration project, here is some
information just for your reference.

Analysis and Suggestion:
=====================

Q: Should I move the DHCP and Print services to this server prior to me
changing the name to match the old server its replacing or wait till the
rename?

A: I assume that you have add the new Windows Server 2003 based DC to be
additional DC in the domain. And you have enable GC on the new DC and
transferred all the 5 FSMO role to the new DC. If so, I would like to
suggest that you first migrate the DHCP and Printer services from the old
Windows 2000 DC to the new Windows Server 2003 based DC, and then demote
the old Windows 2000 DC to be a member server, and then rename the old DC
to another one and change its IP address to another one in the same LAN.
Afterwards, you may simply rename the new Windows Server 2003 based DC to
the original name of the Old Windows 2000 DC and change the IP address to
the old Server's original IP address.

Additional Suggestion:
To make the all the domain users be unaware of the migration of the DHCP
and Printer services, if possible, it is better to migrate them during
spare time(not at the rush hour). Also, I would like to suggest that you
perform a full backup of the old Windows 2000 DC before you migrate the
DHCP and Printer services for the disaster recovery.

Reference:
=============

Guidelines for Using ASR
http://technet2.microsoft.com/window...5-22b0-4f01-83
e7-171bc4cbdf041033.mspx?mfr=true

Hope the issue will be resolved.

Thanks for your time.

David Shen
Microsoft Online Partner Support

[nf]

Thank you for your help so far. If i enable GC and transfer the roles, will
there be a problem when i change the name and address later on (say in a week
or so once i have had the time to move DHCP and printing)?

"David Shen [MSFT]" wrote:

> Hello NF,
>
> Thanks for your reply.
>
> For the further concern about the migration project, here is some
> information just for your reference.
>
> Analysis and Suggestion:
> =====================
>
> Q: Should I move the DHCP and Print services to this server prior to me
> changing the name to match the old server its replacing or wait till the
> rename?
>
> A: I assume that you have add the new Windows Server 2003 based DC to be
> additional DC in the domain. And you have enable GC on the new DC and
> transferred all the 5 FSMO role to the new DC. If so, I would like to
> suggest that you first migrate the DHCP and Printer services from the old
> Windows 2000 DC to the new Windows Server 2003 based DC, and then demote
> the old Windows 2000 DC to be a member server, and then rename the old DC
> to another one and change its IP address to another one in the same LAN.
> Afterwards, you may simply rename the new Windows Server 2003 based DC to
> the original name of the Old Windows 2000 DC and change the IP address to
> the old Server's original IP address.
>
> Additional Suggestion:
> To make the all the domain users be unaware of the migration of the DHCP
> and Printer services, if possible, it is better to migrate them during
> spare time(not at the rush hour). Also, I would like to suggest that you
> perform a full backup of the old Windows 2000 DC before you migrate the
> DHCP and Printer services for the disaster recovery.
>
> Reference:
> =============
>
> Guidelines for Using ASR
> http://technet2.microsoft.com/window...5-22b0-4f01-83
> e7-171bc4cbdf041033.mspx?mfr=true
>
> Hope the issue will be resolved.
>
> Thanks for your time.
>
> David Shen
> Microsoft Online Partner Support
>
>