Module 3: Configuring

and Managing WINS

Module Overview
• Overview of the Windows Internet Name Service

• Managing the WINS Server

• Configuring WINS Replication

• Migrating from WINS to DNS

Lesson 1: Overview of the Windows Internet
Name Service
• When Is WINS Required?

• Overview of WINS Components

• WINS Client Registration and Release Process

• What Is Burst Handling?

• WINS Server Name Resolution Process

• What Are NetBIOS Node Types?

• Demonstration: Installing and Configuring a WINS Server

When Is WINS Required?
WINS is required for the following reasons:
• Older versions of Microsoft operating systems rely on
WINS for name resolution
• Some applications, typically older applications, rely on
NetBIOS names
• When you need dynamic registration of single-label names

• If users rely on the Network Neighborhood or My Network

Places network browser features
• If you are not using Windows Server 2008 as your DNS
infrastructure
Overview of WINS Components

WINS Server
Subnet 2 WINS
Database

WINS Client

Subnet 1

WINS Proxy
WINS Client Registration and Release Process

Name Registered

Name Released

WINS Client WINS Server

1 • WINS client sends request to register

• WINS server returns registration message with TTL value,
indicating when the registration expires

2 • WINS client sends request to release name

• WINS server sends a positive name release response
 What Is Burst Handling?

Burst handling allows a WINS server to handle a high

number of simultaneous name registration requests

1 WINS client 2 WINS acknowledges

registrations exceed registrations with a short
the burst queue threshold renewal interval
WINS Server Name Resolution Process
Up to three attempts
WINS Server A

Client 1

Subnet 2

Subnet 1
2
WINS Server B

3 Subnet 2

Client makes three attempts to contact WINS server,

1 but does not receive a response

2 Client attempts to contact all WINS servers until contact is made

3 If name is resolved, IP address is returned to the client

What Are NetBIOS Node Types?

A NetBIOS node type determines the method that a

computer uses to resolve a NetBIOS name

Node Registry
Description
type value
Uses broadcasts for name
B-node registration 1
and resolution
Uses a NetBIOS name server, such
P-node 2
as WINS, to resolve NetBIOS names
Combines B-node and P-node, but
M-node 4
functions as a B-node by default
Combines P-node and B-node, but
H-node 8
functions as a P-node by default
Demonstration: Installing and Configuring a
WINS Server

In this demonstration, you will see how to install the

WINS server feature and configure burst handling
Lesson 2: Managing the WINS Server
• Overview of Client Records

• Demonstration: Filtering and Viewing Records

in WINS
• How Scavenging Works

• Deleting WINS Records

• Backing Up and Restoring the WINS Database

• Compacting the WINS Database

• Demonstration: Managing the WINS Server Database

Overview of Client Records

A WINS client record includes the following information:

The
Theregistered
The
service
IP address
that
NetBIOS
Displays
The
Theregistered
WINS
state
that“x”
name,
of
corresponds
server
tothe
the
indicate
which
Adatabase
from
entry,
unique
can
which
whether
to hexadecimal
the
Shows
entry,
bethe
aregistered
the
unique
which
entry
when
entry
originates
number
can
the
name
is static
entrythat
will
andthe
expire
WINS
name,
including
or a group,
the displays
hexadecimal
beinternet
active,
“null”
released,
group,
type
or server
isor
identifier
blank
multihomed
or assigns
tombstoned
if the entry
during
computer
is name
not static
registration
Demonstration: Filtering and Viewing Records
in WINS

In this demonstration, you will see how to filter and

view records in the WINS database
How Scavenging Works

Scavenging removes extinct entries from the WINS database

Deleting WINS Records

To delete obsolete records, you can update the

WINS database by:
• Simple deletion. Records selected by using the WINS
console are removed from the current local
WINS server

• Tombstoned deletion. Records are marked for

deletion, replicated to other WINS servers, and then
removed during the next scavenging operation
Backing Up and Restoring the WINS Database

You can restore the WINS database to

recover from a corrupt database

To back up a WINS database:

• Specify a backup directory

• Back up manually or configure automatic backups

To restore a WINS database:

• Stop the WINS service

• Manually delete and restore database files

Compacting the WINS Database

Compacting recovers unused space in a WINS database

Maintain WINS database integrity by using:

• Dynamic compacting. Automatically occurs while the

database is in use

• Offline compacting. Administrator stops the WINS server

and uses the Jetpack.exe command-line tool
Demonstration: Managing the WINS Server
Database

In this demonstration, you will see how to configure

a WINS Backup and compact a WINS Database
Lesson 3: Configuring WINS Replication
• What Is Push Replication?

• What Is Pull Replication?

• What Is Push/Pull Replication?

• Demonstration: Configuring WINS Replication Partner

Properties
• Checking WINS Database Consistency
What Is Push Replication?
• A push partner notifies replication partners based on the number
of changes in its database
• Push replication maintains a high level of synchronization

ServerA 4
3
24
2 Replicas
3 sent
Notification
Replication sent
request ServerB

Subnet 1 11 Subnet 2
50 changes occur in
database

11 ServerA reaches set threshold of 50 changes in its database

22 ServerA notifies ServerB that the threshold is reached

33 ServerB responds to ServerA with a replication request

44 ServerA sends replicas of its new database entries

What Is Pull Replication?

• A pull partner requests replication based on a time interval

• Pull replication limits frequency of replication traffic across
slow links

11 Requests
2 changes
Replicas sent
ServerA every eight hours ServerB

Subnet 1
Subnet 2

11 ServerA requests database changes every 8 hours

22 ServerB sends replicas of its new database entries

What Is Push/Pull Replication?

Push/pull replication ensures that the databases on

multiple WINS servers are nearly identical at any
given time by:

• Notifying replication partners whenever the

database reaches a set threshold of changes

• Requesting replication based on a set time

Demonstration: Configuring WINS Replication
Partner Properties

In this demonstration, you will see how to configure

WINS Replication Partner properties
Checking WINS Database Consistency

Checking WINS database consistency helps maintain

database integrity among WINS servers in a large network

WINS Server

WINS Server

WINS Server
Lesson 4: Migrating from WINS to DNS
• Name Resolution for a Single-Label Name

• What Is the GlobalNames Zone?

• How GlobalNames Zone Name Resolution Works

• Setup Requirements for Implementing the GlobalNames

Zone
• Demonstration: Migrating from WINS to DNS Using the
GlobalNames Zone
Name Resolution for a Single-Label Name
Windows Server 2008 introduces a new zone type for DNS
called GlobalNames Zone

• Resolves single-label names in the enterprise without

using WINS

• Mitigates the management and maintenance of DNS suffix

search lists

• Relies on static record creation

• Requires the zone be available on DNS servers throughout

the forest
What Is the GlobalNames Zone?

The GlobalNames zone:

• Enables Single-Label name resolution for IPV6

enabled networks

• Uses CNAME records to point to the FQDN of the computer

that hosts the resource

• Is recommended to be integrated in Active Directory

with forest-wide replication

• Can be a used as a method to decommission WINS servers

• Requires no additional client configuration because the

client resolves the name in standard DNS query form
How GlobalNames Zone Name Resolution Works

Nochanges
•• No changesare
aremade
madeto
tothe
theclient
clientmachine
machineconfiguration
configuration

Theclient
•• The clientqueries
queriesDNS
DNSin
inthe
thestandard
standardformat
format

Ifthe
•• If theDNS
DNSquery
queryfails
fails(CNAME
(CNAMErecord
recorddoes
doesnot
notexist),
exist),the
the
resolutionprocess
resolution processproceeds
proceedsper
perthe
theclient
clientconfiguration
configuration
Setup Requirements for Implementing the
GlobalNames Zone

Requires authoritative name servers running

 Windows Server 2008
Configure forest-wide, Active Directory-integrated
 replication of the GlobalNames zone

 Create staticFunctions
CNAMEofrecords
Content Advisor include:
that point to FQDN records

 Disable dynamic updates on the GlobalNames zone

Enable single-label GlobalNames zone support on all
 DNS servers that host the zone

Use the following command to enable support for the GlobalNames

zone on all DNS servers hosting the zone:
dnscmd /config /EnableGlobalNamessupport 1
Demonstration: Migrating from WINS to DNS
Using the GlobalNames Zone

In this demonstration, you will use the GlobalNames

zone to migrate from WINS to DNS
Lab: Configuring a WINS Infrastructure
• Exercise 1: Installing WINS

• Exercise 2: Configuring WINS Burst Handling

• Exercise 3: Configuring WINS Replication

• Exercise 4: Migrating from WINS to DNS

Logon information
Virtual machines NYC-DC1 and NYC-SVR1
User name Administrator
Password Pa$$w0rd

Estimated time: 60 minutes

Lab Review
• True or False: You only are required to have WINS
services available for down-level or legacy Windows
operating systems.
• Can Windows clients dynamically register NetBIOS single-
label names in the GlobalNames DNS zone?
• When using the Push/Pull replication options for WINS
servers in your environment, what WINS topology does
this replication type best support?
Module Review and Takeaways
• Review Questions

• Considerations for WINS Services

• Best Practices

• Tools