zoeythecat
Technical User
Hi All,
Hitting this forum with another one. Just looking for some tips and suggestions. I'm replacing a server that has DHCP and WINS. My stategy was this:
(Old Server being replaced)
(1) Backup DHCP database
(2) Backup WINS database
(3) Stop DHCP Service
(4) Stop Wins Service
(New Server)
(1) DHCP (Create scope identical to server i'm replacing)
(2) Restore DHCP database to new server
(3) Activate Scope
(4) Test getting an IP Address
(5) Restore Wins
* My co worker mentioned that I should not need to restore the DHCP database that all clients hitting the DHCP server will just get new IP Addresses and there should be no problem (other than it taking time for users to get their IP Addresses). My question is what happens if your workstation already has an IP Address will this IP Address automatically renew itself when the client logs in or will the client be forced to do an ==>ipconfig /release and /renew?
* Or should I stick to my current strategy?
What are the pro and cons versus restoring the DHCP database to the new server or just simply creating the scope and having a blank database and having users connect to get their IP Addresses?
Any suggestions or thoughts is appreciated.
Thanks in advance,
Zoey
Hitting this forum with another one. Just looking for some tips and suggestions. I'm replacing a server that has DHCP and WINS. My stategy was this:
(Old Server being replaced)
(1) Backup DHCP database
(2) Backup WINS database
(3) Stop DHCP Service
(4) Stop Wins Service
(New Server)
(1) DHCP (Create scope identical to server i'm replacing)
(2) Restore DHCP database to new server
(3) Activate Scope
(4) Test getting an IP Address
(5) Restore Wins
* My co worker mentioned that I should not need to restore the DHCP database that all clients hitting the DHCP server will just get new IP Addresses and there should be no problem (other than it taking time for users to get their IP Addresses). My question is what happens if your workstation already has an IP Address will this IP Address automatically renew itself when the client logs in or will the client be forced to do an ==>ipconfig /release and /renew?
* Or should I stick to my current strategy?
What are the pro and cons versus restoring the DHCP database to the new server or just simply creating the scope and having a blank database and having users connect to get their IP Addresses?
Any suggestions or thoughts is appreciated.
Thanks in advance,
Zoey