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 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.

> 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

On 25 Jul, 10:16, Myweb <mei...@gmx.de> wrote:
> Hello drumavo...@gmail.com,
>
> 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.
>
>
>
> > 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- Hide quoted text -
>
> - Show quoted text -

static ip addressing

On Wed, 25 Jul 2007 08:45:08 -0000, (E-Mail Removed) scribbled:

>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

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

Hi,

(E-Mail Removed) schrieb:
> [...] 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?

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
--
Mark Heitbrink - MVP Windows Server - Group Policy

Homepage: www.gruppenrichtlinien.de - deutsch
Blog: gpupdate.spaces.live.com - english

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.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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
>

On Jul 27, 4:33 pm, "Roger Abell [MVP]" <mvpNoS...@asu.edu> wrote:
> 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.
>
> <drumavo...@gmail.com> wrote in message
>
> news:(E-Mail Removed)...
>
>
>
> > 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- Hide quoted text -
>
> - Show quoted text -


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