Moving DC to new Server

  • Thread starter Thread starter Enrique
  • Start date Start date
E

Enrique

Does anyone know of article or have the steps necessary to move a main
domain controller (running Windows 2000 Server) that's running both DNS and
WINS to a new server with the same OS?
 
Hi Enrique,

Thank you for your question. Technically, you can try the following steps
to move the functionality from the old server to the new one:

1. Install Windows 2000 Server to the new server.

2. Join this Windows 2002 server into the Windows 2000 domain and promote
this new server as the second DC of this domain.

3. Make this new server a global catalog server

- NOTE: Please read the following article before this section.

246303 XGEN: Global Catalog Searches and Related TCP Ports
http://support.microsoft.com/?id=246303

a. Open AD Sites and Services

b. Expand Sites, Default First Site, Servers, Select the new DC server
and right click NTDS settings and select properties.

c. On the General tab put a check mark in the Global Catalog check box.

4. Transfer the FSMO roles.

255690 HOW TO: View and Transfer FSMO Roles in the Graphical User
Interface
http://support.microsoft.com/?id=255690

255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
Controller
http://support.microsoft.com/?id=255504

5. Verify roles have been seized/transferred.

a. Open a Command Prompt on the secondary DC. Run "NTDSUTIL".

b. Type "roles" (without the quotation marks).

c. Type "connections" (without the quotation marks).

d. Type "Connect to Server [ServerName]" (without the quotation marks)
where [ServerName] is the Name of the Domain Controller you would like to
view.

e. Type "Quit" (without the quotation marks).

f. Type "Select Operation Target" (without the quotation marks).

g. Type "List Roles for Connected Server" (without the quotation marks).

6. Take the old Windows 2000 server offline for test. You can perform some
tests to see if it is working properly.

7. After the new Windows 2002 server is able to function in this domain,
run DCPromo on the original DC to demote it. (you can keep it offline as
well)

8. Move DNS database to the new Windows 2000 server.

280061 HOW TO: Move Windows 2000 DNS Zones to Another Windows 2000-based
Server
http://support.microsoft.com/?id=280061

301192 HOW TO: Migrate an Existing Domain Name System Infrastructure
from a
http://support.microsoft.com/?id=301192

9. Move WINS database.

244810 Restoring a Windows 2000 WINS Database from Other Backup Sources
http://support.microsoft.com/?id=244810

300473 HOW TO: Migrate a WINS Database from Windows NT 4 Server to
Windows 2000
http://support.microsoft.com/?id=300473
- This article is for NT 4 but Windows 2000 can use it as well.

Please let me know if this solves this issue or if you need further
assistance. I look forward to hearing from you.

Regards,

Eric Shen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure! - www.microsoft.com/security
 
Thank you! I think this will take care of me for the most part. As I was
reading through this, I realized that I needed to change DNS and WINS
addresses on all my computers accessing this server. How can I make this IP
Address change for DNS and WINS? I look but I didn't see an option in Group
Policy that would allow me to push out this through that method.

Any help is greatly appreciated,

Enrique

"Eric Shen [MSFT]" said:
Hi Enrique,

Thank you for your question. Technically, you can try the following steps
to move the functionality from the old server to the new one:

1. Install Windows 2000 Server to the new server.

2. Join this Windows 2002 server into the Windows 2000 domain and promote
this new server as the second DC of this domain.

3. Make this new server a global catalog server

- NOTE: Please read the following article before this section.

246303 XGEN: Global Catalog Searches and Related TCP Ports
http://support.microsoft.com/?id=246303

a. Open AD Sites and Services

b. Expand Sites, Default First Site, Servers, Select the new DC server
and right click NTDS settings and select properties.

c. On the General tab put a check mark in the Global Catalog check box.

4. Transfer the FSMO roles.

255690 HOW TO: View and Transfer FSMO Roles in the Graphical User
Interface
http://support.microsoft.com/?id=255690

255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
Controller
http://support.microsoft.com/?id=255504

5. Verify roles have been seized/transferred.

a. Open a Command Prompt on the secondary DC. Run "NTDSUTIL".

b. Type "roles" (without the quotation marks).

c. Type "connections" (without the quotation marks).

d. Type "Connect to Server [ServerName]" (without the quotation marks)
where [ServerName] is the Name of the Domain Controller you would like to
view.

e. Type "Quit" (without the quotation marks).

f. Type "Select Operation Target" (without the quotation marks).

g. Type "List Roles for Connected Server" (without the quotation marks).

6. Take the old Windows 2000 server offline for test. You can perform some
tests to see if it is working properly.

7. After the new Windows 2002 server is able to function in this domain,
run DCPromo on the original DC to demote it. (you can keep it offline as
well)

8. Move DNS database to the new Windows 2000 server.

280061 HOW TO: Move Windows 2000 DNS Zones to Another Windows 2000-based
Server
http://support.microsoft.com/?id=280061

301192 HOW TO: Migrate an Existing Domain Name System Infrastructure
from a
http://support.microsoft.com/?id=301192

9. Move WINS database.

244810 Restoring a Windows 2000 WINS Database from Other Backup Sources
http://support.microsoft.com/?id=244810

300473 HOW TO: Migrate a WINS Database from Windows NT 4 Server to
Windows 2000
http://support.microsoft.com/?id=300473
- This article is for NT 4 but Windows 2000 can use it as well.

Please let me know if this solves this issue or if you need further
assistance. I look forward to hearing from you.

Regards,

Eric Shen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure! - www.microsoft.com/security
Click to expand...
 
Hi Enrique,

To deploy the DNS and WINS changes, the recommended way is to use DHCP. For
enterprise environments, DHCP is playing the role to assign IP
configurations to all the clients. When you update this setting in DHCP,
the clients will receive the information when they try to update the IP
address.

For DHCP configuration in Windows 2000 domain, please refer to the
following article:

300429 HOW TO: Install and Configure a DHCP Server in an Active Directory
http://support.microsoft.com/?id=300429

I hope this addresses your concerns. Please feel free to let me know if you
have further questions.

Regards,

Eric Shen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure! - www.microsoft.com/security
 
Back
Top