OPERATING SYSTEM INSTALLATION PROCEDURES

The following step-by-step instructions are meant to provide a quick reference for installing Windows Server 2003 with Terminal Services. Included in these instructions are the postinstallation changes we recommend to address limitations in the operating system itself. These limitations are often due to insufficient default values, but they can also be settings to work around bugs , or simply changes we think are necessary to the "health and well-being" of an Terminal Services/Presentation Server environment. After each recommended change, we provide the setting value or instructions, as well as the reason. Where possible, we have also provided a URL reference with more information on why that change may be necessary.

For the first server build in the farm, document every step in order to create installation procedure documentation. This documentation will be the blueprint for all future server builds and serve as a portion of a disaster recovery plan.

An example of the installation procedures needed for Windows Server 2003 is shown in the following table.

Step	Description
1.	If hardware like Compaq/Dell servers will be used, run the appropriate configuration softwarefor example, Smart Start.
2.	Press F6 to install third-party SCSI or RAID driver(s) that are not currently on the Windows Server 2003 CD-ROM, if needed.
3.	Press ENTER to continue with the installation.
4.	Press F8 to agree to the license agreement.
5.	Follow onscreen prompts to create the appropriate partitions.
6.	Select to format the partition using the NTFS file system. Setup will format the partition and copy installation files. When completed, it will reboot the system and continue to the GUI setup.
7.	Select the regional settings and click Next .
8.	Enter a name and company name and click Next.
9.	Enter the Product Key and click Next.
10.	Select the appropriate license settings and click Next.
11.	Select a computer name, enter the administrator password, and click Next. Windows Server 2003 allows passwords of up to 127 characters. We recommend that the Administrator account password be a minimum of nine characters long and include at least one punctuation mark or nonprinting ASCII character in the first seven characters .
12.	Select the appropriate Date and Time setting and click Next.
13.	The installer is now prompted to configure the network settings. We highly recommend configuring the network adapter cards now. Select Custom and click Next.
14.	Double-click Internet Protocol (TCP/IP) and enter the appropriate TCP/IP address information documented during the design phase. It is recommended to enter the FQDN for the domain the server is a part of. Do this in the DNS Suffix For This Connection area of the DNS tab, which you reach by clicking Advanced. Click Next.
15.	The next screen will ask if you would like to join a domain or stay part of a workgroup. Select the appropriate setting and click Next. Setup continues by copying system files and registering system components .
16.	Click Finish to reboot and log on for the first time.
17.	The server will display the Manage Server GUI after the initial logon. Click the Add Or Remove A Role link.
18.	Click Next to continue.
19.	Select Terminal Server and click Next.
20.	Click Next to install Terminal Server.
21.	Close all programs and click OK.
22.	The server will reboot, and you will need to log on again.
23.	Click Finish in the Configure Your Server Wizard.
24.	For Windows Server 2003, you have to assign the groups that will be allowed to access the terminal server through Terminal Services. Go to Start All Programs Administrative Tools Computer Management. Click Local Users And Groups to expand it. Then click Groups. Double-click Remote Desktop Users, and add the users or groups that are appropriate.
25.	We recommend removing any unnecessary components from Windows. Go to Start Control Panel Add/Remove Programs. Select Add/ Remove Windows Components. We recommend always removing the Accessibility Wizard and Communication Folder from the Accessories and Utilities.
26.	Install any necessary drivers. To do so, the system should be placed in install mode. Refer to the section "Installing and Configuring Applications" in Chapter 13 for more information on install mode. Choose Start Run. In the dialog box that appears, type: change user / install . Then click OK. When the install of the new hardware is completed, place the system back in to Execute mode. Choose Start Run. In the dialog box that appears, type: change user / execute . Then click OK.
27.	If the Novell Client is required, install it at this point. When completed, disable the Novell System Tray icon. To disable the Novell System Tray icon, use the following key: [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Network Provider\ Menu Items] "Enable System Icon"=string:YES If slow logons are experienced , adjust the network bindings order.
28.	Run Microsoft Windows Update and install all critical updates and service packs , root certificates, and Windows compatibility updates. These can be downloaded from the following Web address: http://www.microsoft.com/windowsupdate Remember to use change user /install mode for any updates. For more information on change user /install mode, refer to Chapter 13.
29.	Set the media type, the duplex setting, and the speed that the NIC is required to use within the environment. Verify that the network switch or managed switch is configured to the preferred setting. Never allow the NIC to "auto-detect" the settings. Go to Start Control Panel Network Connections. Right-click Local Area Network. Choose Properties Configure. Then click the Advanced tab.
30.	Disable any additional network interface cards or implement NIC Teaming per the supplied vendor installation procedures. Go to Start Control Panel Network Connections. Right-click any additional NICs and click Disable.
31.	Create and format any additional partitions.
32.	Move the page file to another, faster drive or the second partition if available and set the PAGEFILE to 2.1 times the total amount of physical RAM installed on the server (4095MB max). Go to Start Control Panel. Double-click the System applet. Click the Advanced tab. Click Settings under Performance, then select the Advanced tab, and choose Change.

Service Packs and Hotfixes

The golden rule for loading post-release service packs and hotfixes is "Don't unless you have to." Unfortunately, critical applications or hardware issues often require service packs or hotfixes to correct critical problems or install the latest releases. Microsoft periodically releases service packs that are the culmination of fixes to problems discovered by customers and Microsoft technical support. Customers with a specific or "system down" requirement for a fix that was created after a service pack can often receive it in the form of a hotfix from Microsoft technical support. Citrix also releases a periodic service pack in order to reduce the number of interim hotfixes.

As of this writing, Service Pack 2 for Windows Server 2003 is the only service pack available. We recommend checking the Citrix and Microsoft Web sites for the current level of service packs and related issues to evaluate whether they apply.

Note 

Windows Server 2003 uses a "Windows Update" feature that allows hotfixes to be automatically downloaded from the Internet. We strongly recommend against allowing automatic update on production servers. It does not provide the level of testing rigor that is required to maintain a stable and robust server farm.