Although Windows 2000 servers have a reputation for being notoriously insecure, if you take the time it is actually possible to lock them down so tightly that leading scanners will not even recognize they are Windows servers.

The best way to do this is to automate the security on your servers by using security templates, sometimes referred to as .inf files.

• Securing Windows 2000 Servers, Part 1 discusses using Microsoft's Management Console (MMC) on Windows 2000 servers to automatically configure and enforce a number of security policies.

• Part 2 of the Securing Windows 2000 Servers series teaches you how to assign Local Policies and Event Log security policies to your basic Windows 2000 server templates.

• In Part 3 of the Securing Windows 2000 Servers series, Laura Taylor teaches you how to configure and assign System Services, Registry Settings, and File System Settings security policies.

• Part 4 shows you how to distribute your security policy so that you can use it on multiple systems and, by doing so, standardize your security configurations.

• In Part 5 you'll learn how to keep your DNS server secure, which is paramount to keeping your network secure.

• Part 6 covers how to secure a Windows 2000 Exchange Server.

If you are following along with the series on Securing Windows 2000 Servers and have any questions or comments, make sure you post them in the Intranet Journal Discussion Forum, where the author and hundreds of fellow readers can answer any question you have or dispense advice.

Enjoy the series and good luck.

Of Interest

Intranet Journal Discussion Forum It's Easy to Secure Windows 2000 Servers, Part 1 It's Easy to Secure Windows 2000 Servers, Part 2 It's Easy to Secure Windows 2000 Servers, Part 3 It's Easy to Secure Windows 2000 Servers, Part 4 It's Easy to Secure Windows 2000 Servers, Part 5 It's Easy to Secure Windows 2000 Servers, Part 6