Free Power Tools Brochure
Get Mark Minasi's
17-page guide today!



      

advertisement

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

February 20, 2002 05:20 PM

Recovering WINS

Rating: (0)
Windows IT Pro
InstantDoc ID #23833
Techniques and tools for repairing your WINS servers
In "Recovering DHCP," September 2001, InstantDoc ID 21841, I discussed the importance of Windows 2000's and Windows NT's DHCP services on DHCP-enabled networks. I provided tips, techniques, and tools for performing maintenance and disaster-recovery procedures on DHCP servers. Now I want to provide the same information for another essential network service: WINS.

As ...

ARTICLE TOOLS

You must be a paid Professional Member to access this entire article.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Monthly or Annual

Professional Membership

VIP Membership

Compare Member Benefits

Add a Comment

Sean Daily's articles about recovering essential network services, "Recovering WINS" (March 2002, InstantDoc ID 23833) and "Recovering DHCP" (September 2001, InstantDoc ID 21841), were very informative, especially the suggestions about preparing for disaster. Do you recommend a time interval (e.g., once a month, once a quarter, once a year) for performing the maintenance for those crucial services? Also, have you written any articles about preparing for disaster recovery on Windows 2000 Server or Active Directory (AD)? I'm developing a maintenance schedule and plan to implement the recommendations from your articles.



---------------------------------------------------


How frequently you need to perform the maintenance services I discussed in the articles depends on the size of your organization. Large networks will have an inherently greater use of services such as WINS and DHCP than small networks will have. Thus, performing more frequent maintenance tasks on the databases these services use is important for large networks. In any case, a quarterly maintenance schedule is an absolute minimum*
a monthly schedule is a better idea for all but the smallest networks.
Search the archive on Windows & .NET Magazine's Web site (http://www.winnet
mag.com/magazine) to find other recovery-oriented articles. Look for the third part of my recovering essential services series, "Recovering AD," in an upcoming issue of the magazine.

--Sean Daily


Earl Hinkle 5/8/2002 3:00:34 PM


You must log on before posting a comment.

Are you a new visitor? Register Here

Related Resources

More

Setup rights to helpdesk group to unlock shared files

Does anyone know how to setup a group or permissions for a group (helpdesk) to be able to unlock a shared network file such as a spreadsheet or Access...222-96217

advertisement

GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS

Podcasts

To successfully implement virtual desktops, IT administrators must carefully match user requirements to specific desktop technologies. Listen to this podcast to learn what you need to keep in mind when formulating your approach to desktop virtualization.

Downloads

PacketTrap IT is a comprehensive and affordable network management and application monitoring solution that solves problems associated with bandwidth, network and application performance, and connectivity. Gain insight into your network - try PacketTrapIT free for 21 days!

Web Seminars

Aside from its employees, data is an organization’s most important resource. Join Windows technical specialist and 11-time MVP John Savill to learn the best practices for managing data using features in Windows Server.
View this web seminar on demand!

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.