Changing client TCP/IP settings remotely.

[Guest MT]

Unfortunately, the environment I work in does not use DHCP. I need to change

the primary dns server for all my desktops and servers. Is there a safe and

simple way to do this without actually going to each machine? I'm sure there

are some complicated scripts and I don't want to use Group Policy either. Any

tools or tricks to make this happen?

 

 

Thank you.

[Guest Lanwench [MVP - Exchange]]

Re: Changing client TCP/IP settings remotely.

 

MT <MT@discussions.microsoft.com> wrote:

> Unfortunately, the environment I work in does not use DHCP. I need to

> change the primary dns server for all my desktops and servers. Is

> there a safe and simple way to do this without actually going to each

> machine? I'm sure there are some complicated scripts and I don't want

> to use Group Policy either. Any tools or tricks to make this happen?

>

>

> Thank you.

 

OK, so you haven't used DHCP in the past. That doesn't explain why you can't

use DHCP *now* :-)

 

You can use netsh in a script -

http://www.petri.co.il/configure_tcp_ip_from_cmd.htm

 

but you'll need to assign it as a startup script via Group Policy.

[Guest Pegasus \(MVP\)]

Re: Changing client TCP/IP settings remotely.

 

 

"MT" <MT@discussions.microsoft.com> wrote in message

news:6B056078-41CE-48D8-9415-5471DEB14A0F@microsoft.com...

> Unfortunately, the environment I work in does not use DHCP. I need to

> change

> the primary dns server for all my desktops and servers. Is there a safe

> and

> simple way to do this without actually going to each machine? I'm sure

> there

> are some complicated scripts and I don't want to use Group Policy either.

> Any

> tools or tricks to make this happen?

>

>

> Thank you.

 

You could invoke netsh.exe with psexec.exe (http://www.sysinternals.com). Is it

safe? Yes, provided that you have fully tested your syntax. I you get the

syntax wrong then you're likely to make the machine inaccessible for remote

commands, forcing you to fix things on site. Is it simple? Not particularly.

You will need to get up to speed on netsh.exe.

[Guest MT]

Re: Changing client TCP/IP settings remotely.

 

I've used DHCP at my last gig, but this place is a mixed environment with Sun

Solaris thin clients utilizing DHCP in network. They won't let us subnet the

network and if I use the Unix DHCP server, my Windows boxes will query the

Unix dns. So, I have no choice but to use static IP's for everything.

 

"Lanwench [MVP - Exchange]" wrote:

> MT <MT@discussions.microsoft.com> wrote:

> > Unfortunately, the environment I work in does not use DHCP. I need to

> > change the primary dns server for all my desktops and servers. Is

> > there a safe and simple way to do this without actually going to each

> > machine? I'm sure there are some complicated scripts and I don't want

> > to use Group Policy either. Any tools or tricks to make this happen?

> >

> >

> > Thank you.

>

> OK, so you haven't used DHCP in the past. That doesn't explain why you can't

> use DHCP *now* :-)

>

> You can use netsh in a script -

> http://www.petri.co.il/configure_tcp_ip_from_cmd.htm

>

> but you'll need to assign it as a startup script via Group Policy.

>

>

>

>