WINS Upgrade

Hello All:

I thought I could get rid of WINS, but now I have to
change plans (see KB
http://support.microsoft.com/default.aspx?scid=kb;en-
us;837391). Right now we have just one NT 4.0 WINS server.
I'm not too confidant about the consistency of that WINS
database and would rather not replicate it with a new WINS
server nor do any type of export or migration of the
database.

What I propose to do is to set up a new WINS server on
Server 2003 and on the same day switch everyone over to
the new WINS server via a change in DHCP scope options and
manual changes to static IP servers and clients. I figure
that since everyone would be pointing to the new WINS
server, they should all be fine regarding NetBIOS name
resolution.

I will make sure to shorten the DHCP lease duration enough
so that when I make the change on a Saturday afternoon,
all DHCP clients will have to refresh or renew their
leases by Monday morning and hence receive the new WINS
settings. Eventually I plan to add two more WINS servers
for redundancy and fault tolerance.

Thank you for your opinions and suggestions on the above
plan.

Sincerely,
Martin

"MartinHTN" <(E-Mail Removed)> wrote in message
news:1addf01c44f1a$6eee1fe0$(E-Mail Removed)...
> What I propose to do is to set up a new WINS server on
> Server 2003 and on the same day switch everyone over to
> the new WINS server via a change in DHCP scope options and
> manual changes to static IP servers and clients. I figure
> that since everyone would be pointing to the new WINS
> server, they should all be fine regarding NetBIOS name
> resolution.

All sounds good.

> I will make sure to shorten the DHCP lease duration enough
> so that when I make the change on a Saturday afternoon,
> all DHCP clients will have to refresh or renew their
> leases by Monday morning

I don't think that will matter. I don't think they will receive this
"duration" change until the next time they renew, which will be based on the
old duration (and by then it won't matter). DHCP does not "push" changes to
the client, I believe it is a "passive" system (but I could be wrong).

The client will be forced to renew when they reboot, so the next time they
reboot they will get the change. So just reboot them.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

To summarize that a bit.

Clients always have to negotiate for an address at every bootup reguardless
of the set lease duration. You can also do a release/renew from a command
prompt at any time.

The set duration only really effects machines (in the practical sense) that
are running 24/7 and never turned off.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "MartinHTN" <(E-Mail Removed)> wrote in message
> news:1addf01c44f1a$6eee1fe0$(E-Mail Removed)...
> > What I propose to do is to set up a new WINS server on
> > Server 2003 and on the same day switch everyone over to
> > the new WINS server via a change in DHCP scope options and
> > manual changes to static IP servers and clients. I figure
> > that since everyone would be pointing to the new WINS
> > server, they should all be fine regarding NetBIOS name
> > resolution.
>
> All sounds good.
>
> > I will make sure to shorten the DHCP lease duration enough
> > so that when I make the change on a Saturday afternoon,
> > all DHCP clients will have to refresh or renew their
> > leases by Monday morning
>
> I don't think that will matter. I don't think they will receive this
> "duration" change until the next time they renew, which will be based on
the
> old duration (and by then it won't matter). DHCP does not "push" changes
to
> the client, I believe it is a "passive" system (but I could be wrong).
>
> The client will be forced to renew when they reboot, so the next time they
> reboot they will get the change. So just reboot them.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>