Windows 2003 Active Directory management split dual-use domain controllers

Recently I have several questions about dividing a dual-use domain controller. Most of the questions are like, "I work for a small company, I upgraded my computer to Windows 2000 a few years ago, but I can't afford two servers." Therefore, we have deployed a domain for our company. Also, the domain service is used as the host system. Now we want to divide this dual-use domain controller so that each system has its own capabilities. So how do you change it to two new servers without losing data? ”

The method is simple. All domain controllers in Windows SQL Server (and Windows Server 2003) are in the same-body. Knowing this, the solution is obvious. The following are the basic troubleshooting steps:

1. Install Windows SQL Server (or Windows Server 2003) in one (or two) systems

2. Create a new system member from the current domain

3. Upgrade one of the servers to a domain controller

After completing these steps, pay special attention to testing the new system for a few days. Once stability is shown, the transition can be continued:

1. Demote a former domain controller to a member server

2. Install Server Software in a second new system

3. Migrate the data from the old system to the new host (depending on what kind of step the service or server will take)

This allows your domain controller to run new hardware, and a member server in the new hardware can perform specific programs. At the same time, the old server can still be used. Do you need any advice on using the old server?

I strongly recommend deploying at least one additional domain controller that works when a domain problem occurs, and what you need to do is:

1. Format the old server to clear the drive

2. Install the favorite Windows Server

3. Connect the system to the domain

4. Upgrade it to a domain controller

Now, you have not only divided the old dual-use domain controllers, but also improved network work by backing up or deploying a second domain controller. When two (or more) domain controllers manage the same domain, for maintenance or upgrades, a domain controller can be offline without real and network disconnection. Maintenance and the loss of the Active Directory database can also be avoided when a hardware or system failure occurs.