Chapter 3. Adding Hardware
BUILDING A PRODUCTION-QUALITY SERVER TAKES TIME. You can automate the installation and testing processes to a large extent, but by the time you're done prepping the RAID array, installing the operating system, partitioning and formatting the data drives, layering on the applications, setting permissions, and verifying that everything works the way your users expect, you've made your way through the better part of a morning.
Even if you take care to anticipate the future needs of the users, the time inevitably comes when you have to add new hardware or update a driver or replace a failed component. You might need a second processor to speed up a slow SQL server or an additional drive to accommodate data growth or a new network adapter with multiple interfaces to speed up a terminal server. Doing this kind of work on a production server requires a little planning. You don't want to interrupt users during working hours, and you sure don't want to create a circumstance where the server doesn't come back online after you've made your changes.
Every piece of hardware has its own idiosyncrasies to which every server reacts in a unique way. It is not possible to cover all the potential perturbations. This chapter introduces the Windows Server 2003 architecture as it pertains to hardware operability then covers the features for installing new devices and troubleshooting them when something goes wrong. It also covers the device management and compatibility features on Intel 64-bit (IA64) platforms and compares them to standard Intel 32-bit platforms (IA32).