Installing new domain controller

[pendal1]

Guys, my organization has one domain with multiple domain controllers. Each site has at least one domain controller. What I'm doing is converting the old domain controller in a certain site to a file/print server and using the new server we purchased as the new domain controller. Now after I create the new scope and configure the scope options, is there an easy way to get the clients to obtain their ip settings from the new domain controller without having to reboot all the workstations. For example, if I delete the leases on the old domain controller before I demote it - will this force the clients to broadcast for their new ip addresses. Anyway, any advice is appreciated.

 

[mrdenny]

No you will need to reboot the clients in order to force them to get a new lease from the new server. Deleting the reservation from the DHCP server will not force a new lease as DHCP doesn't require that machines maintain a connection to the server.

Setup your new scope over a different range of IP Addresses. This way if any machines do not get rebooted you will avoid address conflicts with machines getting new leases from then new DHCP server.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[pendal1]

Thank you very much mrdenny. I had a guy argue with me over this point so I'm glad to have this clarification.

 

[58sniper]

You can export the settings and current lease info from the existing server, and import them into the new server. That's assuming the parameters are going to stay the same.

Other than that, if nothing else is changing, then there really isn't a reason to force them to get a new address until their normal DHCP renew period.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP