Automatic change from manual IP to DHCP

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi!

We have several hundred clients with manually configured IP adresses.
Now its my task to switch to DHCP (which is no problem at all) but there should be no activity on the clients! The change should occur only on our servers like "clicikng the right script, clients change with no interaction, ready to use".

So I have to manage this through policies (first thought)...has anyone an idea for me how to do that?

Thx,
Jo
 
Jo Troester said:
Hi!

We have several hundred clients with manually configured IP adresses.
Now its my task to switch to DHCP (which is no problem at all) but there
should be no activity on the clients! The change should occur only on our
servers like "clicikng the right script, clients change with no interaction,
ready to use".
So I have to manage this through policies (first thought)...has anyone an idea for me how to do that?

Thx,
Jo

You could execute the following command on each client machine with the help
of psexec.exe (from www.sysinternals.com):

netsh interface ip set address "Local Area Connection" DHCP

This is the easy bit. What is less easy is the synchronisation: If you have
a well-populated address range then you are likely to get address conflicts
between early converters (who get an address from the DHCP server) and the
latecomers (who might want to use this very same address when they boot up).
Perhaps a change of subnets could resolve the issue.
 
This seems to work fine, thank you :-)
But only the IP settings are changed, manually DNS-entries are still active. How to get rid of them?
 
netsh interface ip set dns name="Local Area Connection" source=dhcp

thats it

thx ;-.>
 
netsh interface ip delete dns "Local Area Connection" ***.***.***.***
*** are ip address of DNS Server,

don't know if you can use wildcards.
Jo Troester said:
This seems to work fine, thank you :-)
But only the IP settings are changed, manually DNS-entries are still
active. How to get rid of them?
 
Can use all instead of the ipaddress
Dave Cooper said:
netsh interface ip delete dns "Local Area Connection" ***.***.***.***
*** are ip address of DNS Server,

don't know if you can use wildcards.

active. How to get rid of them? anyone the boot
 
You will have to delve deeper into the netsh command and see what it can do
for you. Here are some examples:

netsh interface ip delete dns name="Local Area Connection 2" addr=all
netsh interface ip set dns name="Local Area Connection 2" source=static
addr=192.168.20.20
netsh interface ip add dns name="Local Area Connection 2" addr=192.168.30.30


Jo Troester said:
This seems to work fine, thank you :-)
But only the IP settings are changed, manually DNS-entries are still
active. How to get rid of them?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top