WINS removal in an AD integrated environment

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

Guest

I have steadily worked to remove WINS from my AD integrated DNS environment
over the last year. I have had no clients using WINS for the last 4 months.
My peers are still painting a gloom and doom scenario since they "tried" to
do away with WINS years ago and it was not successful. My question is this,
can anyone think of anything that I might need to do to make sure the wooden
stake is correctly driven thru the heart of this legacy crutch?
 
sszz77 said:
I have steadily worked to remove WINS from my AD integrated DNS environment
over the last year. I have had no clients using WINS for the last 4
months.
My peers are still painting a gloom and doom scenario since they "tried"
to
do away with WINS years ago and it was not successful. My question is
this,
can anyone think of anything that I might need to do to make sure the
wooden
stake is correctly driven thru the heart of this legacy crutch?
Click to expand...

If you run a Microsoft network you will likely be happier
with NetBIOS name resolution on your network.

There are still an interesting number of features and functions
that need NetBIOS.

IF you use NetBIOS AND you have more than one subnet you
have a practical NEED for WINS Server.

It costs nothing and it fairly trivial to operate so there is seldom
a reason to fight this or swim upstream.

You will lose browsing without NetBIOS -- this is usually the
kicker that forces NetBIOS.

There are also numerous minor features that need NetBIOS
(including sometimes Cluster Services or Exchange) and
you may need it if you (ever) need an EXTERNAL trust (NT4
or trusts with another Forest's domains.)

You could theoretically use LMHosts files in a routed environment,
but face it: If you use NetBIOS in a routed environment you need
WINS server (from a practical standpoint.)
 
Back
Top