Deploying network settings via Group policy

  • Thread starter Thread starter drumavoley
  • Start date Start date
D

drumavoley

The company i work for recently replaced 500 machines, which are all
running windows 2000 professional, which was done by an external
company - it has become apparent recently that about 250 of these
machines have wrong dns and wims settings - is anyone aware of a way
to roll out these settings via a policy?

thanks
damian
 
Hello (e-mail address removed),

Did you use DHCP or fixed ip addresses?

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
 
Hello (e-mail address removed),

Did you use DHCP or fixed ip addresses?

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.





- Show quoted text -
Click to expand...

static ip addressing
 
The company i work for recently replaced 500 machines, which are all
running windows 2000 professional, which was done by an external
company - it has become apparent recently that about 250 of these
machines have wrong dns and wims settings - is anyone aware of a way
to roll out these settings via a policy?

thanks
damian
Click to expand...

I think there is a way to do this with scripting. Check out the
scripts on the Microsoft web site.
 
Hi,

[...] it has become apparent recently that about 250 of these
machines have wrong dns and wims settings - is anyone aware of a way
to roll out these settings via a policy?
Click to expand...

Wrong DNS -> NO Policy, simple mistake, but big efect :-(

You can export all machine accounts in a textfile and run "psexec"
against them with netsh, change to dhcp, because static adressing
IMHO makes no sense in such a big environment.

Mark
 
Do you mean that you replace W2k pro machines, or that you
replaced with W2k pro? The policies for setting DNS is a
post-W2k policy, so if you replace W2k with XP or Vista you
may have an approach via policy. The most direct way would
possible be one form or another of remote script, such as use
of Wmi to a Wmi service attachment to each machine in turn
to set the values.
 
Do you mean that you replace W2k pro machines, or that you
replaced with W2k pro? The policies for setting DNS is a
post-W2k policy, so if you replace W2k with XP or Vista you
may have an approach via policy. The most direct way would
possible be one form or another of remote script, such as use
of Wmi to a Wmi service attachment to each machine in turn
to set the values.







- Show quoted text -
Click to expand...


We are going with the netsh method, creating a batch file, to be run
at startup and deploying it via group policy.
replaced machines all have win2k prof back on them

thanks
 
Back
Top