Adding another DHCP Server 3

[stenk]

I would like to add another DHCP server to the BDC. The reason for this is I would like to set this BDC up as our Main PDC, when I upgrade to 2000.

The only problem is they do not comunicate like WINS does and I need to know whether I create the same scope as is on the current PDC or if I have to create another scope outside of the one already created.

I hope you all know what I mean!

I just want to make sure that when I promote the BDC to be the PDC and shutdown our old PDC, that it will act as the old PDC did!.

Is there any thing I should look out for .

Please help

Many thanks

Sten

 

[Redhook01]

You should be able to go ahead and set up the same scope on the "new" dhcp server. Just remember that you can't have it active while the "old" dhcp server is still running. You will need to restart the clients once you make the switch so they can get new leases from the new server. I can't think of anything else off the top of my head. Hope this helps.

 

[globalstrata]

What Redhook01 has mentioned works. But when you activate the new DHCP, if all the clients do not renew their IPs, you will have conflits. To avoid this, do the following:

1. Install and configure DHCP in the new server.
2. Stop the service for both servers.
3. Copy the DHCP server directory tree, systemroot\System32\Dhcp, to a temporary location on the new (destination) DHCP server. For example, copy the directory tree to C:\Temp\System32\Dhcp.
4. Start the Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer and backup the specified key to a text file.
5. Rename the System.mdb file to System.src in the new server. Copy the DHCP server directory tree from the temporary folder to systemroot\System32\Dhcp to replace the existing DHCP server directory.
6. Start Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer
7. Select the DHCPServer key (located under the Services key) and Restore the registry hive that you backed up from the old server (step 4). In Restore Key, for File name specify the following: systemroot\System32\Dhcp\Backup\Dhcpcfg
When prompted, click Yes.
8. Close the registry and then start the DHCP service in the new server
9. In the old server, delete the DHCP server database folder, %SystemRoot%\System32\Dhcp, at the source server. Uninstall the DHCP server to remove it from this server.


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[ShackDaddy]

Or, to make things simpler, do the following:

1. Set up the new DHCP server and configure the scope to be the same set of addresses as the old scope is using. Don't activate the scope yet.

2. Deactivate the scope on the original server. DON'T delete the scope, just deactivate it.

3. Turn off all client computers.

4. Activate the new scope on the new server.

5. Restart all client computers.

When the clients come online, they will try to renew their old IP addresses and ask their original DHCP server to do so. The original server will respond with a NACK (Negative Acknowledgement) which will force the client to drop the IP address and start from scratch. It will issue a request for an IP and the new server will offer it one from the new scope. All the clients will receive new addresses on startup, and the new scope will become populated.

Before you do this, make sure that there are no hardcoded addresses within the range of the scope you have configured. As things progress, you can actually look at the members of the deactivated scope on the original server and watch the lease list shrink and shrink as each client lease gets dumped with the NACK.

This is how I like to do it because it also works when you are moving your clients from an NT DHCP server to a Windows 2000 DHCP server. Plus, you and your staff get lots of exercise!

Of course, if you are looking for a way to move your leases from one NT DHCP Server to another without getting off your butt and without the client addresses changing, Gladys' solution is a very good one. The best, in fact.

ShackDaddy

 

[stenk]

Many Thanks for all your help every one.

Kindest regards,

Sten