Best of ENP: Adding IPSec to your network isn't all that hard and it's a good way to secure traffic, but is it worth the additional moving parts it introduces?
Articles by Drew Bird
With IPSec, you can encrypt network traffic and protect it from malicious users. With the first of our two part series, we tell you how to implement it on Windows Server 2003.
Part Three: Strong passwords can do a lot, but what if your network needs an extra level of security? Here's how to get started with smartcards and biometrics in the Windows world.
Part Two: Biometrics and smart-cards are hot, but a sane password policy can do a lot to keep your network secure. Here's how to give would-be crackers the boot with the Win2k3 Account Lockout Policy.
Part One: Many security-minded admins scoff at passwords as tissue-thin protection against malicious users. But with Windows 2003 Server's password policy tools, you can do a lot to tighten down your most basic line of defense.
When it comes to avoiding spyware, most net admins are probably pretty well protected on their own computers. Experts seem to think that's less true of the networks they maintain.
SUS is out, WUS is in. Here's a preview of what's to come with Windows Update Services, Microsoft's expanded take on software update management.
Sometimes it's the little things that count. Here are three stocking stuffers from Microsoft that can help you check in on your Win2k3 server's performance, track down bandwidth hogs, and comb through the logs looking for that elusive performance hit.
Software Restriction Policies, Part Two: Last week we introduced you to the software restriction policies features in Windows Server 2003. This week we go in-depth to show you how to create your own SR policies to secure your systems against worms and malware.
Software Restriction Policies, Part One: One way to head worms and trojan malware off at the pass is to keep them from running at all. With Win Server 2003 Software Restriction Policy management, you can do just that, flexibly, with no additional software, and with little change to your carefully tuned Active Directory configuration.
Here's a list of eight steps you can take to tighten down your Windows 2003 server: Print it out, tape it to your cube wall, implement a few, and maybe you won't have to hear your pager over Thanksgiving dinner.
Volume Shadow Copy Service, Part Two: You won't want to trash your existing backup routine in favor of Microsoft's VSS, but you'll probably wonder what you ever did without it.
Users want to recover altered or deleted files all the time, but they never seem to want what you give them. With Windows Server 2003's Volume Shadow Copy Service, backups start making a lot more sense for both you and your users.
It sounds a little bold to say that the GPMC is the only tool you’ll ever need to manage group policy on your Windows Server 2003 system, but the reality is that it’s probably true.
Windows Security Configuration and Analysis Tool, Part Two: This week we revisit the Windows Server 2003 SCA tool to learn more about how to read what it's telling you, and how to set up your own baseline security templates.
Implementing SPF, Part 1: Even though Sender ID for E-Mail has run into some problems, SPF can still help shield you from phishing attacks. Here's how to add SPF to your DNS server in Windows Server 2003.
Windows Security Configuration and Analysis Tool, Part One: With the Windows Server 2003 SCA Tool, you've got a valuable means to lock down your server. Here's how to use one of the best tools you may have never heard of.
If you're looking for a remote administration tool for Windows 2003 Server systems that's got the basic features you need and a familiar interface for novice administrators, HTML Remote Administration Tools might be the ticket.
With the Windows Network Load Balancing Manager, you're just a few steps away from a more efficient network. Here's how, hands on.
Network load balancing clusters offer increased fault tolerance and improved performance for server-based applications. Best of all, the technology has been supported in every Windows networking operating system since NT 4.0.
In Part 2 of our two-part series on monitoring network traffic, we continue our look at some of the tools that are built in to Windows Server 2003. We also touch on some third-party tools that you may want to consider.
Is your network running at optimum performance? If you can't answer that question, you should check out the network monitoring tools included with Windows Server 2003.
Given the simplicity and value of setting up fault tolerance for your DHCP services, it's surprising how many network admins fail to do so. Drew Bird explores how a simple matter of planning your implementation and putting it into place can save you potential aggravation down the road.
Elevating your Windows Server 2003 Active Directory domain and forest functional levels can deliver enhanced functionality, but is it worth the time and hassle?
Faced with thousands of dollars in unused Netware licenses, a school district makes the jump to Linux.