thanks, Is there an article that I can refer to that states this?
Main Topics
Browse All TopicsWe are planning to demote our initial Windows 2000 Server. We are now running two Windows 2003 DCs and would like to get the Windows 2000 Server out of the mix. Is there a way to restore the 2000 server back to a DC if the process goes wrong? According to the docs I found it should be fairly simple to demote a server, I'm just curious of what kind of issues I may run into?
These are the instructions I plan to follow:
from http://support.microsoft.c
Removing Active Directory from a Domain Controller
NOTE: When a domain controller is demoted, if it is not the last domain controller in the domain, it performs a final replication and then transfers the roles to another domain controller. As part of the demotion process, the Dcpromo utility removes the configuration data for the domain controller from Active Directory. This data takes the form of an NTDS Settings object, which exists as a child to the server object in Active Directory Sites and Services Manager. After the domain controller is demoted it no longer has Active Directory information available, and uses the Security Accounts Manager (SAM) database for local database information. If the domain controller is a global catalog, that role is not transferred to another domain controller. In this case, you must manually select the check box in Active Directory Sites and Services Manager for another domain controller to take over the role.
If the demotion process does not succeed for any reason, you must manually delete this metadata from the directory. Use the Ntdsutil.exe utility to manually remove the NTDS Settings object. For additional information about how to use Ntdsutil.exe, click the article number below to view the article in the Microsoft Knowledge Base:
216498 (http://support.microsoft.
1. Click Start, click Run, type dcpromo, and then click OK.
2. This starts the Active Directory Installation Wizard. Click Next.
3. There is a check box in the Remove Active Directory screen. If this computer is the last domain controller in the domain, click to select the check box. Otherwise, click Next.
4. In the next screen, set the password for the administrator account on the server after Active Directory is removed. Type the appropriate password in the Password and Confirm Password boxes, and then click Next.
5. In the Summary screen, review and confirm the options you selected, and then click Next.
6. The wizard begins the process of removing Active Directory from the server. After the process is finished, a message indicates that Active Directory was removed from the computer.
7. Click Finish to quit the wizard.
8. Restart the computer.
NOTE: Windows 2000-based DNS severs should point to themselves for DNS in their TCP/IP properties. If this server needs to resolve names from its Internet service provider (ISP),you should configure a forwarder.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
this will help to add an additional 2000 DC back in if you ever need to
1) Promote your new machine as an additional domain controller in an already existing domain - this will allow AD to replicate to the new server
2) Make sure DNS is AD integrated on your old DC to allow all DNS replications also
3) Transfer the FSMO roles to the new server
http://www.petri.co.il/tra
http://support.microsoft.c
4) Make the new DC a Global Catalog under Sites and Services
http://support.microsoft.c
5) Deactivate DHCP on the old DC (if used) and recreate the scope on the new DC, note if you have a fairly complex or Large DHCP scheme you may want to export and import the database
http://support.microsoft.c
6) Run DCDIAG to make sure all is well and replication is fine
7) Demote the old DC if you dont intend to keep it as a backup
8) Recreate Shares etc on the new server
9) Reinstall printers and share them etc....
this will allow you to have the complete AD directory on the new DC and clients will barely be aware of any changes
DCPROMO is buggy, you may find issues when demoting but we can deal with that when it comes, it also doesn't always remove the DC from sites and services, which you need to do manually
I can't find an article that gives all the steps in one place. Most 'demotion' articles assume that you know not to proceed with removing the DC that is instrumental in your DNS/DHCP/WINS/GC/FSMO\file
I suggest that you re-install a workstation with Windows Server 2003, join it to the domain, promote it, wait for synchronisation and then demote it. This way you will gain confidence in that part of the process.
I would take issue with Microsoft's blanket "NOTE: Windows 2000-based DNS severs should point to themselves for DNS in their TCP/IP properties.". That article is dated November 2004 and that part is wrong. You should ensure that no servers or clients are using the target DC for DNS if you are using Active Directory Integrated DNS. We pretty much assume that your DNS is AD-integrated.
Business Accounts
Answer for Membership
by: ryangormanPosted on 2006-07-25 at 07:27:39ID: 17176050
Demoting a Domain Controller is a painless task. You could even promote another Windows 2000 member server into a Windows 2003 domain if the domain mode was still Windows 2000 Native or Windows 2000 Mixed.
Before demoting a server you should check that no other clients rely on this server for DC centric tasks. I am assuming that your DCs provide DHCP/DNS/WINS although this need not be the case.
1. Manually transfer FSMO roles to preferred DCs.
2. Ensure that you have at least one other GC.
3. Transfer DHCP server to another server.
4. Ensure that you have at least one other DNS/WINS server.
5. Ensure that no clients rely on this server for DNS/WINS.
6. Configure this server to point to another internal DNS server in its TCP/IP properties.
7. Demote the server.