Feb 222008

If you miss Part1,Part2,Part3of migration tutorial check from the following places




In final part we will see how to remove your old server (win server 2000) from network,Raise the domain level functionality to native Windows 2003,Rename your new windows server 2003 same as your old server.

12 Disconnect the old server (win server 2000)

  • Go to Start -> Run and type dcpromo and click on OK button.
  • On the Active Directory Installation Wizard screen, follow the wizard and demote it from the domain controller to a standalone server.
  • Reboot the Server.
  • Change the server membership to a Workgroup.
  • Reboot the Server.
  • Shutdown and disconnect the server from the network.

13. Raise the domain level functionality to native Windows 2003 in win server 2003.

For this follow this procedure

  • Log on the win server 2003 of the domain with domain administrator credentials.
  • Click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.
  • In the console tree, right-click the domain for which you want to raise functionality, and then click Raise Domain Functional Level.
  • Under Select an available domain functional level, do the following
  • Click Windows Server 2003, and then click Raise to raise the domain functional level to Windows Server 2003.

Note:- You can also raise the domain functional level by right-clicking a domain that appears in the Active Directory Users and Computers MMC snap-in, and then clicking Raise Domain Functional Level. To raise the domain functional level, you must be a member of the Domain Administrators group.

The current domain functional level appears under Current domain functional level in the Raise Domain Functional Level dialog box. The level increase is performed on the PDC FSMO and requires the domain administrator

14. Test with a client that you can logon, check the event log for any errors.

15. Changing the new DC’s (Win2K3) IP Address and Hostname to the same Hostname and IP Address as the old DC (Win2K)

  • Make sure the Old Domain Controller (Win2K) is disconnected from the network.
  • Make sure all the references of the old (Win2K) server name does not exist anymore In Active directory (Sites, Domain Controllers Container and DNS).
  • Make sure the domain functional level is raised to Windows 2003 native mode.
  • Change the IP Address of the new domain controller (Win2K3)
  • Change the Domain Controller hostname using Netdom tool.

Netdom tool comes with the support tools package, which is available on the Server installation CD, under \support\tools folder.

  • Install support tools and go to Command Prompt.
  • Type the following command to add the new domain controller name, and then press ENTER:

netdom computername CurrentComputerName /add:NewComputerName

Note: The NewComputerName must be a fully qualified domain name (FQDN). Currentcomputername can be the existing FQDN or the IP Address of the computer.

c) Type the following command to designate the new name as the primary computer name, and then press ENTER:

netdom computername CurrentComputerName /makeprimary:NewComputerName

d) Restart the computer.

e) After the computer restarts, go to Command Prompt.

f) Type the following command to remove the old domain controller name, and then press ENTER:

netdom computername NewComputerName /remove:OldComputerName

Finally if you are using any logon scripts using kix program,Network Printers you need to make sure everything is working fine

Incoming search terms:

  11 Responses to “Disconnect the old server (win server 2000),Raise the domain level functionality to native Windows 2003,Rename your new windows server 2003(Part4)”

  1. Thanks for the detailed tutorial on how to transfer from win 2000 to win 2003. very helpful and easy to follow!! Thank you so much!

  2. I have a question about the renaming of the server. Is anyone still looking at this?

    Thanks in advance

  3. Hello,
    I am getting the netdom syntax error, can you please let me know what is the correct syntax for renaming domain controller

  4. what is the error message you are getting and what command you are trying

  5. Could you please let me know, while doing all this, can users still access to the network? Will Exchange Server 2000 work as well?

    Thanks, Linh

  6. @linh

    This is not recommended so you need to do this weekends or after office hours

  7. Thank you

  8. Thank you for this excellent resource, tutorials like this are invaluable.
    I have exchange 2000 running on our 2000 DC, so for a week or so after the migration, the 2000 dc will still be in production until exchange is migrated to a new member server.
    Can the instructions, part 1 -3, still be followed step by step or does exchange complicate matters and require futher steps?
    Many Thanks.

  9. It nice reference for migration.Thanks a lot

  10. We bought a new Server with Windows Server 2003 installed on it. The old PDC also has Windows Server 2003 and exchange installed on it, but it is going to be taken off of the network. Can i know the steps to Migrate from the old server to the new server.

  11. Hi! I have just used this tutorial to update from an old W2K Server to W2K8 R2, it worked without major troubles using these steps. Thank you for this great piece of work

 Leave a Reply



You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>