Designing a Windows Update Strategy for the Enterprise of scenarios frequently
To this day, there are many protocols that aren?t used as often as others but that occa- sionally rise to make their presence known and require special attention from administrators who otherwise no longer encounter them. On the MCITP level, you actually encounter these sorts of scenarios frequently. This is because most complex networks will contain a lot of different technologies that mutually cohabit (or at least coexist) in the same envi- ronment. Because of this, Microsoft expects that all candidates applying for MCITP-level certification completely understand how to deal with even the most MCITP Test obscure networking protocols and understand their effect on their networking environment.
In the following section, I’ll begin by explaining the most commonly encountered pro- tocol: WINS.
In some ways, I?ve already addressed legacy technology at some level, but now you’re going to dive into a concept that isn?t used as commonly anymore and will probably go the way of the dodo after this incarnation of Windows Server, or possibly after the next incarnation. In case you hadn?t guessed, I’m talking about Windows Internet Name Service (WINS).
When using WINS, generally four components are available to administrators using Windows Server 2008:
Each of these roles in self-explanatory by its name; the server serves WINS, the WINS database keeps a collection of records, the clients request WINS information, and the prox- ies provide resolution for WINS in TCP/IP con?gured networks.
Normally organizations won?t implement WINS without a valid reason. Among these rea- sons are the following:
Legacy applications using NetBIOS Older version of Windows
Dynamic registration of single-label names
Additionally, an organization may implement WINS if it is running logically older versions
of Windows or applications requiring older versions of Windows, which include anything
using Network Neighborhood or My Network Places.
WINS Name Resolution
The WINS name resolution process is pretty easy to understand. First, any given client sends up to three attempts to connect to a WINS server, but no response is given. If no response is given, it will attempt to find another. If it does, the WINS MCITP Certificate server responds with a given IP address.
Within the WINS database, various pieces of information are stored that in total create the necessary components to resolve names to IP addresses, which is the given purpose of any general name resolution server. Within WINS, client records contain the following:
Record names IP addresses
Types
State Static
Owner Version
Each of these records within the database is occasionally changed, deleted, or somehow modi?ed through a process called scavenging.
Processing your request, Please wait....
