The wizard now takes you through the second stage of the installation process. You are asked for information about yourself, the organization or company licensing the software, and the computer.
Windows Server 2003 takes this information and begins a noninteractive installation in which it copies software to support machine configuration, installed devices, and so on. After this phase, Windows Server 2003 prompts you for the following information:
♦ Language Options. You are asked to customize language, locale, and keyboard settings. If you are installing in the United States, you can, for the most part, leave these at the default settings. You can also configure the server to use multiple languages and regional settings. Choosing multiple languages forces Windows to install the character sets from multiple languages.
♦ Name and Organization. Provide the name of the person responsible for the software and the name of the organization that owns the license.
♦ Licensing Mode. You can choose to select licensing on a per-server, per-seat, or perdevice basis. If you choose to license per seat, you must enter the number of client access licenses (CALs) purchased. If you are going to provide application services by using the Terminal Services in Application Mode, choose the CAL option.
♦ Computer Name. This is where you get to add the NetBIOS name. Windows Server 2003 chooses a default name for you, which you should change because it doesn't make very much sense. Coming up with a convenient naming convention that your users recognize is far better. In the examples given throughout this book, we use LA for LATINACCENTS, followed by the abbreviation for the role that the server plays and the role number. If the machine is destined to become a domain controller, for example, we name it MCDC, followed by the server number: LADC00 or LADC06. An example of a DNS server would be LADNS01.
Windows pretty much leaves you to your own devices in naming your computers. The best rule to follow is to name the machine according to any convention you dream up that works for your situation . . . just be consistent. Resist cute names for several reasons: The names may be hard for your users to relate to, and some may find them annoying. (Not everyone loves Disney.) Server names are also the prefixes for the new Dynamic DNS names assigned to the server. A simple machine name for the genesis. mcity.org domain name would be LADNS06.LATINACCENTS.MCITY.ORG, which is far better than BULLWINKLE.LATINACCENTS.MCITY.ORG. Be careful, too, about using names that attract security problems. We once used the name Checkpointcharlie, which was subsequently hacked the following week.
♦ Password for the Administrator Account. This account is installed into the local domain's Administrator account except for domain controllers.
♦ Windows Server 2003 Components. The next step is to add the optional components and services. Ignore most of these services in trial installations and go directly to Networking Options. Here, you must provide DHCP information, the DNS server address, and other information. Some of the services are selected for you by default, such as Transaction Server and IIS. If you are not going to use a service such as Transaction Server, deselect it. The Windows Server 2003 Components Wizard is shown in Figure 6-2.
Windows Components Wizard
You can add « lemove comporenls olVritlo^s
ijjä Accessories and Utilities
Was this article helpful?