I have One Domain Controller in my network. It is also the only DNS and DHCP server. I am wanting to demote thisserver as a backup domain controller and make another server the primary domain controller with the DNS and DHCP roles. How would i go about doing this? I want to move the global catalog to the new server and possibly have the old server a backup DNS and DHCP server as well. Thanks for your help in advanced!-Chris

Since you're talking Global Catalog I'll assume you're running Windows 2000 Server or later. (Please provide the Windows version and Service Pack level) Chris Collier said: I have One Domain Controller in my network. It is also the only DNS and DHCP server. I am wanting to demote thisserver as a backup domain controller and make another server the primary domain controller with the DNS and DHCP roles. How would i go about doing this? I want to move the global catalog to the new server and possibly have the old server a backup DNS and DHCP server as well. Thanks for your help in advanced!-Chris Here's a high level step-by-step: Install a new server box with Windows Server. Apply the latest Service Pack and Windows Updates. Install this server with the same Windows Server version as your current server or a newer version. Note:When you install the box with a newer version of Windows prepare your Active Directory before you promote the new server to a Domain Controller. (More information) Install DNS and promote the new server to a Domain Controller. Make it an additionalDomain Controller for the same Active Directory domain in the same Active Directory forest as your current Domain Controller. (More information) Be sure to check the Event Viewer logs on both Domain Controllers and the dcpromo.log and dcpromoui.log on the new Domain Controller to ensure promotion and replication. Congratulations! You now have two Domain Controllers. Make the new Server a Global Catalog and restart it afterwards. (More information) Transfer the five Flexible Single Master Operation (FSMO) Roles from the current Domain Controller to the new Domain Controller. (More information) One of the FSMO roles is the PDC emulator role. After transfering this role to your new server it is the equivalent of the Primary Domain Controller. (PDC) Install the DHCP Server on the new Domain Controller and migrate the DHCP database from the old Domain Controller to the new Domain Controller. (More information) Make sure the DHCP Scope is deactivated on the old server. Change the DHCP Scopes on both servers. In the DHCP Scope on the new server assign the IP address of the new Domain Controller as the primary DNS Server. This last step will ensure your client will begin using the new Domain Controller as their Primary DNS server after their DHCP lease expires. (More information) I've chosen to disable the old DHCP server and migrate it to the new server. Alternatively you can also create a 80% scope and a 20% scope on the new and old server respectively. (More information)I've chosen to keep the old server a Global Catalog as well, because of the Infrastructure Master rule of thumb.