| If the project plan depicts to install Microsoft Windows 2000 Server then we are now ready to get down and dirty and break out that new hardware and install some the OS. For the first server you will want to document every step you take in order to create installation procedure documentation. This documentation will be the blue print for all future server builds and serve as a portion of a disaster recovery plan. The following is an example of the installation procedures needed for Windows 2000 Server: | Step | Description | | 1. | Install and configure server hardware - Unpackaged and prep hardware
- Update the firmware to latest versions
| | 2. | If you will be using hardware like Compaq / Dell servers, you will need to run the appropriate configuration software. i.e., Smart Start | | 3. | Press F6 if you need to install 3rd party SCSI or RAID driver(s) that are not currently on the Windows 2000 CDROM | | 4. | Press Enter to continue with the installation | | 5. | Press F8 to agree with the license agreement
| | 6. | Follow on screen prompts to create the appropriate partitions. | | 7. | 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 | | 8. | Click Next to continue | | 9. | Select the regional settings and click Next | | 10. | Enter a name and company name and click Next | | 11. | Select the appropriate license settings and click Next | | 12. | Select a computer name, enter the administrator password and click Next Note: Windows 2000 allows passwords of up to 127 characters. I recommend that the Administrator account password is at least nine characters long and that it includes at least one punctuation mark or non-printing ASCII character in the first seven characters. In addition, the Administrator account password should be unique from server to server. |
Step | Description | | 13. | You are now prompted to select the Windows 2000 Components to be installed. I recommend selecting only what is needed. I personally remove the following: Accessories and Utilities remove Multimedia, Games, and Chat, in Communications I remove Chat and Phone Dialer and I remove the Accessibility Wizards. Indexing Service I highly recommend removing the Indexing Service Internet Information Services (IIS) I highly recommend removing the IIS service. If you leave it checked then you will have the option of installing Web Interface during the install. I do not recommend this; I try to keep Web Interface separated from my application servers. If you must install Web Interface on a MetaFrame XP Server then do it from the control server. Script Debugger I recommend removing the script debugger unless you or your customer requires it. You will want to check the Terminal Services checkbox to enable Terminal Services. | | 14. | Select the Date and Time settings and click Next | | 15. | Select Application Server Mode and click Next | | 16. | Select the default permissions for application compatibility Permissions compatible with Windows 2000 Users This setting gives default terminal services users the same permissions as a member of the Users group and could cause issues with some legacy applications. Permissions compatible with Terminal Server 4.0 Users This setting gives default Terminal Services users full access to critical registry and file system locations thus enabling support for legacy applications while creating a possible security hole and more importantly, gives the end-user the ability to affect the stability of the system. Click Next | | 17. | You are now prompted to configure the network settings. I highly recommend configuring the network adapter cards now. Select Custom and click Next. | | 18. | Double click on Internet Protocol (TCP/IP) enter the appropriate TCP/IP address information documented during the design phase. Note: It is recommended to enter the FQDN for the domain the server is a part of in the DNS Suffix for this connection area of the DNS tab, located behind the Advanced button.
Click Next
| | 19. | The next screen you will see asks you if you would like to join a domain or stay a part of a workgroup. Select the appropriate setting and click Next Setup continues by copying system files and registers system components. | | 20. | Click Finish to reboot and logon for the first time |
| Step | Description | | 21. | Install any drivers necessary. Microsoft recommends that you place the system into install mode if you will be installing any hardware or hardware drivers. Refer to How to install applications section later in this document for more information on install mode. Click Start Run type: change user /install click OK When you have completed the install of the new hardware you will need to place the system back in to Execute mode. Click Start Run type: change user /execute click OK | | 22. | If you will need to install the Novell Client, you will need to do so now. When completed you will want to disable the Novell System Tray Icon Disable Novell System Tray Icon [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Network Provider\Menu Items] "Enable System Icon"=string:YES | Registry File: Disable Novell System Tray Icon.reg | | | If you experience slow logons, you might want to adjust the network bindings. The following link has some great information on how to tune the Novel client for optimum performance. http://www.ithowto.com/novell/clientspeed.htm | | 23. | Install Microsoft Service Pack 3 http://www.microsoft.com/windows2000/downloads/servicepacks/sp3/default.asp Note: I DO NOT recommend you install Microsoft Service Pack 4 for Windows 2000 yet. Please keep your eyes on dabcc.com for more info on the problems SP4 cause and possible resolutions. | | 24. | Run Microsoft Windows Update and install all Critical Updates and Service Packs, Root Certificates, Windows Compatibility Updates. http://www.microsoft.com/windowsupdate Note: Remember to use change user /install mode for any updates. For more information on change user /install mode please refer to Installing Applications later on in this section. | | 25. | Set the media type, duplex setting, and the speed that the NIC is required to use within the environment. Verify that the switch or managed switch is configured to the preferred setting. Never allow the NIC to Auto detect the settings as described in section Throttling Port Speed and Duplex Settings - Click Start click Settings click Control Panel click Network and Dial-Up Connections right click on Local Area Network click Properties click Configure click the Advanced Tab
| | 26. | Disable any additional Network Interface Cards or implement NIC Teaming per the supplied vender installation procedures. - Click Start click Settings click Control Panel click Network and Dial-Up Connections Right click on any additional NICs and click Disable
| | 27. | Create and format any additional hard disk drives and partitions. |
| Step | Description | | 28. | Move the page file to another faster drive or the second partition if available and set the PAGEFILE to two (4095 MB max) times the total amount of physical RAM installed on the server - Click Start click Settings click Control Panel double click the System applet click on the Advanced tab click Performance Options click Change
| | 29. | Increase the Registry Size. 256 MB should be sufficient. - Click Start click Settings click Control Panel double click on the System applet click Advanced tab click Performance Options click Change
|
In order to keep current with the latest version of Microsofts Data Access Components and to guarantee the IMA service runs at peak performance I recommend you install MDAC version 2.8. The current version of MDAC is 2.8. You can download and install MDAC 2.8 from . Note: Before installing, an updated MDAC version, be sure to stop the MS Terminal Services Licensing service and the Independent Management Architecture service Restart the server before beginning MetaFrame XP installation. 1. Click Start Run type: change user /install click OK. 2. Double click on MDAC_TYP.EXE 3. Click to check I accept all of the terms of the preceding license agreement and click Next. 
4. Click Finish 
5. Click Finish to reboot the server. 
To aid in troubleshooting and to gain access to a command prompt Microsoft has developed the Recovery Console. Note: If can be argued that if you are using a rapid server and application deployment mechanism then it is quicker to just reimage the server and not even mess with troubleshooting issues. I agree with this argument but from time to time it is nice to have the capabilities of the recovery console. Just dont let the engineering ego get in the way in troubleshooting issues that can easily be overcome by a reimage. The following procedures define how to install the Recovery Console as a start up option. 1. With Windows running, insert the Windows 2000 Server CD into your CD-ROM drive. 2. Click Exit when prompted with this Auto run screen:. 
3. Click Start Run Type: CMD and click OK switch to the CD-ROM drive, and type the following: 
4. Click Yes to install the Recovery Console. 
5. Click OK 
The Windows 2000 Recovery Console will now appear as a choice during start up. Citrix MetaFrame XP Server with Feature Release 3 requires version 2.0 of the Microsoft Windows Installer service. This has become a non issue as Microsoft Service Pack 3 and above for Windows 2000 now includes the 2.0 version of the Installer service. If you will not be utilizing Service Pack 3 or above for Windows 2000 then please refer to the following steps. The following details how to install Microsoft Windows Installer Service 2.0. 1. Browse to the \support\msi20\ folder on the MetaFrame XP Feature Release 3 Server CD and double click instmsiw.exe. 
2. Setup will update the Windows Installer Service and prompt you to click OK to continue. Note: If you experience any errors, please refer to the Windows Event Log. 3. Click Yes to reboot the server.
|