Pre-Installation Considerations

Before getting started with loading and configuring Windows Server 2000 or 2003, there are some important considerations to think about.

• Review the Microsoft hardware compatibility list. Microsoft publishes this list at http://www.microsoft.com/hwdq/hcl/, but does not guarantee that the hardware listed will work flawlessly with Terminal Services, nor that hardware not listed will not work. It does certify that the hardware listed has been tested and provides a good starting point for evaluation. Only consider hardware not on the list if it is known to work with Terminal Services and MetaFrame.

• Make sure your existing file server, domain controllers, and Active Directory infrastructure are installed and functioning properly. You will be storing scripts, Group Policy objects, and templates centrally, not on each MetaFrame server. In addition, a file server will need to be installed and be accessible when your servers go online.

• Make sure all required drivers and startup disks are available. Even with the maturity of the Windows Server platform, hardware is constantly changing, and special drivers may be required for RAID controllers, NICs, the BIOS, or other server components when loading Windows Server 2000/2003. Make sure these are available and on the appropriate media before you begin.

• Review information on platform-specific issues. The respective web-based knowledge bases from Citrix and Microsoft have a wealth of information on different server hardware. It is prudent to review this information and circumvent potential problems before they occur. This review may even serve to change your mind about which hardware to purchase.

• Prepare hardware. Thoroughly prepare and test your hardware before attempting to load any software. Make sure all shipping protection has been removed. Open the case and make sure all components are securely seated and installed correctly. Power-on the server and run the vendor's diagnostics on the entire system. If your vendor hasn't "burned in" the server, let the diagnostics run at least overnight, if not for a few days, to eliminate any "lemons" before you begin to rely on the system.

• Double-check the data center environment. Don't assume power, cooling, or moisture levels are adequate. Check them out with the data center staff and compare them to published tolerances from the hardware manufacturer.