The networking services provided by a Windows 2003 server are critical applications. You should also consider fault−tolerant hardware, as discussed in Chapter 5. But even before you consider this option, you should be sure that everything in your server is working properly. Youll want to test five key components as soon as your server is in−house:
Memory • Hard disks • CD−ROM drives • SCSI controllers • Network adapters •
Good memory and disk tests are time−consuming. Testing out the high−end computer that I recommend could take a week or more. Dont let that deter you, though. You want to be sure that youve got a solid platform under your organizationif for no other reason than that youll sleep better at night.
During Windows Server 2003 installation, the system is automatically configured for a variety of hardware options, so you should be sure that all your hardware is working during the installation process. For this reason, youll want to test your CD−ROM drive, SCSI controllers, and network adapters before installing Windows Server 2003. Test all these together to be sure that no IRQ, I/O address, or DMA conflicts occur, although this should be less of a problem if your computer and adapters support plug−and−play hardware. It should go without saying, but Ill say it anyway: Dont consider your testing phase finished until all components pass the tests you set out for them. Now lets start testing:
Testing memory Because the quick boot−up memory test on Intel−based PCs cannot find most memory problems, use Smith Micro Softwares CheckIt (www.smithmicro.com/checkit/) or PC− Doctors PC−Doctor for DOS (www.pc−doctor.com) to test memory. You should run either of these programs from DOS with no memory manager present, and run the complete suite of tests in slow rather than quick mode.
Testing hard disks There are two kinds of software−based hard disk testers: those that write one pattern all over the disk and then read to see whether the pattern was written correctly (MS− DOSs SCANDISK is such a tester), and those that write a range of patterns and test to see whether each was properly written. Youll want a multipattern tester because it is more likely to find the bit−based problems on a disk. SpinRite from Gibson Research (http://grc.com/ default.htm) is a good multipattern tester that can find and declare off−limits any bad areas on the disk that the manufacturer didnt catch.
Testing CD−ROM drives I test my CD−ROM drives in DOS using MSCDEX.EXE and the DOS driver for the drive. If I can do a directory (DIR) on a CD−ROM in the drive that Im testing and copy a file or two from the CD−ROM, I assume that its working well enough to move on to Windows 2003 installation.
Testing SCSI controllers If you tested your hard drives as suggested previously, youve also tested their controllers, at least in isolation from other adapters. Just be sure to run your tests again with active CD−ROM drives and network cards to ensure that no adapter conflicts are lurking in the background just waiting to mess up your Windows Server 2003 installation.
Tip If youve got enough hardware, you might want to run your RAM and disk tests simultaneously. This will cut down on testing time somewhat.
Testing network adapters I never install a machine that will be networked without making sure that it can attach in MS−DOS mode to a server. I use Microsofts NDIS drivers. Make sure to connect your LAN−side adapter to your network before you begin installing Windows 2003.
If youre going to connect your server both to your LAN and directly to the Internet without an intervening firewall, I strongly suggest that you install only the LAN−side network adapter before installing Windows 2003. That way, theres no chance that the adapter might be accidentally activated by Windows
Plug−and−Play hardware system when you first boot up after installing Windows 2003. This could expose your server to the Internet and its seemingly endless threats to computer security. While Im strongly urging you to do things, let me almost insist that you put your server behind a firewall. Ill talk more about how you do this in Chapter 18, Exchange Server System Security.
Warning Use solid, top−name brand server−quality adapters. Ive seen a lot of
workstation−quality adapters from second−level name−brand vendors such as LinkSys and D−Link permanently or temporarily go south at the worst times. Youre better off with cards from vendors such as 3Com. I like the 3C905CX−TX adapters. Ive experienced breakdowns with these cards, but far less frequently than with the others. And dont think you need good adapters only for Internet connections. Windows 2003 servers need LAN access too, and Exchange 2003 cant function at all without access to domain controllers, which should be on the LAN side.