MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
The following article will help you to replace single domain controller in domain with a single domain controller
How to replace single domain controller in domain with a single domain controller?
The following article describe a guidelines to replace exiting Windows 2003 Domain Controller with a new server.
The article assume the following pre-requirement settings.
1. There no Exchange/SQL server etc. on the current Domain Controller.
2. There only one domain, and there only one domain controller function as:
DHCP/WINS/DNS/File Server/Print Server.
3. The source server using regular (No SBS) Windows 2003 Standard or higher.
The following steps need to be taken to replace the exiting Domain Controller.
1. Install the Windows 2003 Standard or higher on a new server.
Tip: You will need to setup the current Domain Controller as DNS server.
2. Promote the new server to become Domain Controller (in the same domain).
Step-by-Step Guide to Setting Up Additional Domain Controllers
3. Promote the new Domain Controller to be "Global Catalog" and reboot the server.
Enable or disable a global catalog
4. Install DNS server on the new Domain Controller.
How To Integrate Windows Server 2003 DNS with an Existing DNS Infrastructure in Windows Server 2003
How To Install and Configure DNS Server in Windows Server 2003
5. Set the local IP of the new Domain Controller as DNS server.
6. Option - Install WINS service on the new Domain Controller and change
the Domain Controller IP settings to point on the local IP as WINS server IP.
Tip: You can migrate the current WINS database to the new server.
How to migrate a WINS Database from Windows 2000-based WINS server to a Windows 2003-based WINS server
7. Move FSMO rules to the new Domain Controller.
How to view and transfer FSMO roles in the graphical user interface
8. Demote the original Domain Controller from using as "Global Catalog" and reboot the server.
Enable or disable a global catalog
9. Demote the original Domain Controller from using as "Domain Controller".
10. Migrate printer settings from the old server to the new one by using "Windows Print Migrator 3.1" tool.
Microsoft Windows Server 2003 Print Migrator 3.1
11. Migrate File Server settings from the old server to the new one by using "Microsoft File Server Migration Toolkit".
Microsoft File Server Migration Toolkit
12. Install DHCP server on the Domain Controller and migrate the DHCP settings from the old server.
How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003
Tip: Don’t forget to set the new Domain Controller as DNS & WINS (Optionally) for the DHCP scope/s.
13. Edit users profiles and/or user logon scripts to point to the new Domain Controller as File Server and Printer server.
14. Uninstall unnecessary services from the old Domain Controller.
15. Install third party tools on the new Domain Controller (Backup Software, Antivirus etc.)
16. Re-register users computers in the new DHCP by using ipconfig /release and ipconfig /renew.
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)