How do I define a default DHCP Server?
I'm installing a Server 2008 R2 Server into an small (1 server) network that is currently running Server 2003. I've promoted it and extended the schema accordingly and everything is running fine.
My question is, how do I get the workstations to now go to the new server for DHCP addressing?
I remember in the old days there were 'preferred server' settings that you could tell a workstation which server to go to but I'm not clear on how to do this in a Windows Server 2008 LAN.
I understand how to move the scope, but need to know how to point the workstations (about 10 of them) to the new server for DHCP addressing.
Thanks
My question is, how do I get the workstations to now go to the new server for DHCP addressing?
I remember in the old days there were 'preferred server' settings that you could tell a workstation which server to go to but I'm not clear on how to do this in a Windows Server 2008 LAN.
I understand how to move the scope, but need to know how to point the workstations (about 10 of them) to the new server for DHCP addressing.
Thanks
Mike Thomas
Activate the new one and deactivate the old one, that's all you can do.
ASKER
And workstations will automatically know to go to the new server?
Yes they will, DHCP is cool like that. ;)
Read this article for an explanation on how DHCP works
http://knowurtech.com/networking/how_dhcp_works.html
http://knowurtech.com/networking/how_dhcp_works.html
Hi,
Would recommend you to Authorize the new DHCP in the Domain.
Then remove the old DHCP server ethernet cable and run ipconfig/release and ipconfig/renew on a client system.
If the client gets a new address lease it should be fine.
You can then go ahead and connect the Old DHCP Server back to the new and unauthorize it in the Domain.
Note: Keep the old DHCP server unauthorized for about a week atleast before you decide to do off with the DHCP role on the server.
Just incase required you could reauthorize incase of any major issues.
I am not quite sure how you have taken care of the IP scope here.
Same IP Scope on both the servers ??
Would recommend you to Authorize the new DHCP in the Domain.
Then remove the old DHCP server ethernet cable and run ipconfig/release and ipconfig/renew on a client system.
If the client gets a new address lease it should be fine.
You can then go ahead and connect the Old DHCP Server back to the new and unauthorize it in the Domain.
Note: Keep the old DHCP server unauthorized for about a week atleast before you decide to do off with the DHCP role on the server.
Just incase required you could reauthorize incase of any major issues.
I am not quite sure how you have taken care of the IP scope here.
Same IP Scope on both the servers ??
Typo Error:
I meant "connecting the old DHCP Server back to the Network" when i typed "Connect the Old DHCP Server back to the New"
I meant "connecting the old DHCP Server back to the Network" when i typed "Connect the Old DHCP Server back to the New"
ASKER
Yes same scope. One server is replacing the other. Can you be specific on how to unauthorize?
Right click the sever in the console and select de-authorise
Or rather unauthorise, I would also remove the scope from the old server it uninstall the dhcp service as I have had them still servicing requests.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.