Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

965 lines
43 KiB

  1. **********************************************************************
  2. Windows Server 2003, Enterprise Edition
  3. Setup Text Files, Part 4 of 6:
  4. Running Setup
  5. **********************************************************************
  6. This part of the text file series provides recommendations for
  7. preparing your system for a new installation or an upgrade, and it
  8. explains how to run Setup for Microsoft Windows Server 2003,
  9. Enterprise Edition.
  10. This part of the text file series also provides a description of the
  11. Manage Your Server program, which appears after Setup completes a new
  12. installation. Together, Setup and the Manage Your Server program help
  13. you get your servers up and running quickly.
  14. For more information about the deployment of servers, see the
  15. Microsoft Windows Server 2003 Deployment Kit. You can view the
  16. Windows Deployment and Resource Kits on the Web at:
  17. http://www.microsoft.com/reskit/
  18. The following list of headings can help you find the information
  19. about running Setup that applies to you. For information about
  20. planning an upgrade or a new installation, see EntSrv1.TXT,
  21. EntSrv2.TXT, and EntSrv3.TXT. If you have a server cluster, also be
  22. sure to read EntSrv5.TXT and EntSrv6.TXT.
  23. Contents
  24. --------
  25. 1.0 Preparing Your System for an Upgrade
  26. 2.0 Starting Setup for an Upgrade
  27. 3.0 Preparing Your System for a New Installation
  28. 4.0 Starting Setup on an x86-based Computer
  29. 5.0 Starting Setup on an Itanium Architecture-based Computer
  30. 6.0 Planning for Unattended Setup
  31. 7.0 Entering Server Settings for a New Installation
  32. 8.0 Configuring Your Server
  33. 9.0 Product Activation for Products in the
  34. Windows Server 2003 Family
  35. ======================================================================
  36. 1.0 PREPARING YOUR SYSTEM FOR AN UPGRADE
  37. ======================================================================
  38. This section describes the basic steps to take in preparing your
  39. server for an upgrade.
  40. If you are upgrading Windows Server 2003, Enterprise Edition, on
  41. server cluster nodes, be sure to read EntSrv5.TXT and EntSrv6.TXT.
  42. ----------------------------------------
  43. 1.1 Checking the System Log for Errors
  44. ----------------------------------------
  45. Use Event Viewer to review the system log for recent or recurring
  46. errors that could cause problems during the upgrade. For information
  47. about viewing errors, see Help for the operating system that you
  48. are running.
  49. ----------------------
  50. 1.2 Backing Up Files
  51. ----------------------
  52. Before upgrading, it is recommended that you back up your current
  53. files, including anything containing configuration information, for
  54. example, the System State and the system and boot partitions. You can
  55. back up files to a variety of different media, such as a tape drive or
  56. the hard disk of another computer on the network.
  57. --------------------------------------------------------------
  58. 1.3 Preparing Mirror Sets and Other Disk Sets for an Upgrade
  59. (Windows NT 4.0 only)
  60. --------------------------------------------------------------
  61. With the disk management technologies in Microsoft Windows NT 4.0,
  62. you could create volume sets, mirror sets, stripe sets, or stripe sets
  63. with parity, each with specific capabilities and limitations. By using
  64. dynamic disks, introduced with Windows 2000, you can take advantage of
  65. similar technologies, and with Windows Server 2003, Enterprise
  66. Edition, you can also extend dynamic volumes without repartitioning or
  67. reformatting.
  68. This transition from the technologies used in Windows NT 4.0 means
  69. that you must make certain choices before running Setup for
  70. Windows Server 2003, Enterprise Edition. For important
  71. information about these choices, see "Working with Volume, Mirror,
  72. or Stripe Sets or Stripe Sets with Parity" in EntSrv2.TXT.
  73. -------------------------------
  74. 1.4 Disconnecting UPS Devices
  75. -------------------------------
  76. If you have an uninterruptible power supply (UPS) connected to your
  77. target computer, disconnect the connecting serial cable before running
  78. Setup. Setup automatically attempts to detect devices connected to
  79. serial ports, and UPS equipment can cause problems with the detection
  80. process.
  81. -------------------------------------
  82. 1.5 Reviewing Hardware and Software
  83. -------------------------------------
  84. When you start Setup for an upgrade, the first process it carries out
  85. is a check for compatible hardware and software on your computer.
  86. Setup displays a report before continuing. Use this report, along with
  87. information in Relnotes.htm (in the \Docs folder on the Setup CD), to
  88. find out whether you need to update your hardware, drivers, or
  89. software before upgrading.
  90. Confirm that your hardware and software is designed for products in
  91. the Windows Server 2003 family by checking the hardware and
  92. software compatibility information in the Windows Catalog at:
  93. http://www.microsoft.com/windows/catalog/
  94. If you have hardware devices that do not use Plug and Play, see
  95. "Taking an Inventory of Devices That Do Not Use Plug and Play"
  96. in EntSrv1.TXT.
  97. ======================================================================
  98. 2.0 STARTING SETUP FOR AN UPGRADE
  99. ======================================================================
  100. If you are upgrading to Windows Server 2003, Enterprise Edition,
  101. you can start Setup from the CD or from a network. For information
  102. about the versions of Windows from which you can upgrade, see
  103. "Operating Systems from Which You Can Upgrade" in EntSrv1.TXT.
  104. For information about providing a mass storage driver or a Hardware
  105. Abstraction Layer (HAL) file during Setup, see "Providing a Mass
  106. Storage Driver or a HAL File" later in this text file.
  107. IMPORTANT: To run Setup for an upgrade, you must be a member of the
  108. Administrators group on the local computer. If the computer is
  109. joined to a domain, members of the Domain Admins group might be
  110. able to perform this procedure. As a security best practice, if you
  111. start Setup from a computer running Windows 2000, consider using
  112. Run as.
  113. Run as is a secondary logon method that you can use to start commands
  114. or programs using a different security context. For example, you can
  115. log on as a member of the Users group and, without logging off, run a
  116. command as a member of the Administrators group. To find more
  117. information in Windows 2000 about Run as, on a server running Windows
  118. 2000, click Start, click Help, click the Search tab, and then search
  119. for "runas."
  120. >>>TO START AN UPGRADE FROM THE CD ON A COMPUTER RUNNING WINDOWS
  121. 1. Insert the CD in the drive, and wait for Setup to display a
  122. dialog box.
  123. 2. Follow the Setup instructions.
  124. >>>TO START AN UPGRADE FROM A NETWORK
  125. 1. On a network server, share the installation files by either
  126. inserting the CD and sharing the CD-ROM drive or by copying the
  127. files from the I386 folder on the CD to a shared folder.
  128. 2. On the computer on which you want to install Windows
  129. Server 2003, Enterprise Edition, connect to the shared folder
  130. or drive that contains the Setup files.
  131. 3. Run Setup.exe.
  132. 4. Follow the Setup instructions.
  133. ======================================================================
  134. 3.0 PREPARING YOUR SYSTEM FOR A NEW INSTALLATION
  135. ======================================================================
  136. This section describes the basic steps to take in preparing your
  137. server for a new installation.
  138. If you are installing Windows Server 2003, Enterprise Edition,
  139. on server cluster nodes, be sure to read EntSrv5.TXT and EntSrv6.TXT.
  140. ----------------------------------------
  141. 3.1 Checking the System Log for Errors
  142. ----------------------------------------
  143. If the computer already has a working operating system, review the
  144. system log for recent or recurring errors (especially hardware errors)
  145. that could cause problems during the installation. For information
  146. about viewing event logs, see Help for the operating system on
  147. your computer.
  148. ----------------------
  149. 3.2 Backing Up Files
  150. ----------------------
  151. Before you perform a new installation, it is recommended that you
  152. back up your current files, unless the computer has no files or the
  153. current operating system files have been damaged. You can back up
  154. files to a variety of different media, such as a tape drive or the
  155. hard disk of another computer on the network.
  156. -----------------------------
  157. 3.3 Uncompressing the Drive
  158. -----------------------------
  159. Uncompress any DriveSpace or DoubleSpace volumes before installing.
  160. Do not install Windows Server 2003, Enterprise Edition, on a
  161. compressed drive unless the drive was compressed with the NTFS file
  162. system compression feature.
  163. ---------------------------------------------------------------------
  164. 3.4 Preparing Mirror Sets and Other Disk Sets (Windows NT 4.0 only)
  165. ---------------------------------------------------------------------
  166. With the disk management technologies in Windows NT 4.0, you could
  167. create volume sets, mirror sets, stripe sets, or stripe sets with
  168. parity, each with specific capabilities and limitations. By using
  169. dynamic disks, introduced with Windows 2000, you can take advantage of
  170. similar technologies, and with Windows Server 2003, Enterprise
  171. Edition, you can also extend dynamic volumes without repartitioning or
  172. reformatting.
  173. This transition from the technologies used in Windows NT 4.0 means
  174. that you must make certain choices before running Setup for
  175. Windows Server 2003, Enterprise Edition. For important
  176. information about these choices, see "Working with Volume, Mirror, or
  177. Stripe Sets or Stripe Sets with Parity" in EntSrv2.TXT.
  178. -------------------------------
  179. 3.5 Disconnecting UPS Devices
  180. -------------------------------
  181. If you have an uninterruptible power supply (UPS) connected to your
  182. target computer, disconnect the connecting serial cable before running
  183. Setup. Setup automatically attempts to detect devices connected to
  184. serial ports, and UPS equipment can cause problems with the detection
  185. process.
  186. ======================================================================
  187. 4.0 STARTING SETUP ON AN X86-BASED COMPUTER
  188. ======================================================================
  189. This section explains how to start Setup for a new installation on an
  190. x86-based computer. For an explanation of how to start Setup on an
  191. Itanium architecture-based computer, see "Starting Setup on an Itanium
  192. Architecture-based Computer" later in this text file.
  193. Setup works in several stages, prompting you for information, copying
  194. files, and restarting. Setup concludes with Manage Your Server, which
  195. you can use to adjust the server configuration for your
  196. specific needs.
  197. For important information to help you make the initial choices
  198. offered by Setup, see EntSrv2.TXT and EntSrv3.TXT. For information
  199. about unattended Setup and other options available when you start
  200. Setup, see "Planning for Unattended Setup" later in this text file.
  201. ---------------------------------------------------
  202. 4.1 Providing a Mass Storage Driver or a HAL File
  203. ---------------------------------------------------
  204. If you have a mass storage controller that requires a driver supplied
  205. by the manufacturer, or if you have a custom Hardware Abstraction
  206. Layer (HAL) file supplied by the manufacturer, provide the appropriate
  207. driver file or HAL file during Setup.
  208. 4.1.1 Mass Storage Drivers and the Setup Process
  209. --------------------------------------------------
  210. If you have a mass storage controller (such as a SCSI, RAID, or Fibre
  211. Channel adapter) for your hard disk, confirm that the controller is
  212. designed for products in the Windows Server 2003 family by
  213. checking the hardware and software compatibility information in the
  214. Windows Catalog at:
  215. http://www.microsoft.com/windows/catalog/
  216. If your controller is compatible, but you are aware that the
  217. manufacturer has supplied a separate driver file for use with products
  218. in the Windows Server 2003 family, obtain the file (on a floppy
  219. disk) before you begin Setup. During the early part of Setup, a line
  220. at the bottom of the screen prompts you to press F6. Further prompts
  221. will guide you in supplying the driver file to Setup so that it can
  222. gain access to the mass storage controller.
  223. If you are not sure whether you must obtain a separate driver file
  224. from the manufacturer of your mass storage controller, you can try
  225. running Setup. If the controller is not supported by the driver files
  226. on the Setup CD and therefore requires a driver file that is supplied
  227. by the hardware manufacturer, Setup stops and displays a message
  228. saying that no disk devices can be found, or it displays an incomplete
  229. list of controllers. After you obtain the necessary driver file,
  230. restart Setup, and press F6 when you are prompted.
  231. 4.1.2 Using a Custom HAL File
  232. ------------------------------
  233. If you have a custom Hardware Abstraction Layer (HAL) file supplied
  234. by your computer manufacturer, before you begin Setup, locate the
  235. floppy disk or other medium containing the file. During the early part
  236. of Setup, a line at the bottom of the screen prompts you to press F6:
  237. at this time press F5 (not F6). After you press F5, follow the prompts
  238. to include your HAL file in the Setup process.
  239. ---------------------------------------------
  240. 4.2 Starting Setup on an x86-based Computer
  241. ---------------------------------------------
  242. The sections that follow, "Starting a New Installation from a CD" and
  243. "Starting a New Installation from a Network," explain how to start
  244. Setup for a new installation. For information about starting Setup for
  245. an upgrade, see "Starting Setup for an Upgrade" earlier in this
  246. text file.
  247. For information about unattended Setup and other options available
  248. when you start Setup, see "Planning for Unattended Setup" later in
  249. this text file.
  250. 4.2.1 Starting a New Installation from a CD
  251. --------------------------------------------
  252. If you use the Setup CD, you have several options for starting Setup,
  253. as explained in the following procedures.
  254. Note: If you are running Setup on a computer running
  255. Microsoft Windows 3.x or MS-DOS, for best efficiency, use disk
  256. caching. Otherwise, the Setup process (started from Winnt.exe)
  257. could take a long time. To enable disk caching on a computer
  258. running Windows 3.x or MS-DOS, you can use SMARTDrive. For
  259. information about SMARTDrive, see the documentation for
  260. Windows 3.x or MS-DOS.
  261. >>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING MS-DOS
  262. 1. Insert the CD in the drive.
  263. 2. At the command prompt, type:
  264. d:
  265. where d is the drive letter of the CD-ROM drive.
  266. 3. Type:
  267. cd i386
  268. 4. Type:
  269. winnt
  270. 5. Follow the Setup instructions.
  271. >>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING WINDOWS
  272. Before starting this procedure on a computer running Windows NT 4.0,
  273. apply Service Pack 5 or later.
  274. 1. Insert the CD in the drive.
  275. 2. To begin Setup, do one of the following:
  276. * For a computer running any version of Windows other than
  277. Windows 3.x, wait for Setup to display a dialog box.
  278. * For a computer running Windows 3.x, use File Manager to change
  279. to the CD-ROM drive and to change to the I386 directory, and
  280. then double-click Winnt.exe.
  281. 3. Follow the Setup instructions.
  282. >>>TO START SETUP FOR A NEW INSTALLATION FROM THE CD ON AN X86-BASED
  283. COMPUTER
  284. Another way of using the Setup CD is to start the computer from
  285. the CD-ROM drive. This method applies only if you want to perform a
  286. new installation, not an upgrade. Using this method, you can perform
  287. an installation on a computer that does not have an operating system,
  288. although you can also use this method on computers that have operating
  289. systems.
  290. 1. Determine whether the computer on which you want to start Setup
  291. can be started from the CD-ROM drive and whether you want to
  292. perform a new installation (not an upgrade). Continue only if
  293. both are true.
  294. 2. Insert the CD in the drive, and then restart the computer.
  295. 3. Follow the instructions for your operating system to boot the
  296. computer from the CD.
  297. 4. Wait for Setup to display a dialog box, and then follow the
  298. Setup instructions.
  299. 4.2.2 Starting a New Installation from a Network
  300. -------------------------------------------------
  301. To install Windows Server 2003, Enterprise Edition, from a
  302. network, you either share the files directly from the CD or copy them
  303. to a shared folder. Then, you start the appropriate program to
  304. run Setup.
  305. >>>TO INSTALL WINDOWS SERVER 2003, ENTERPRISE EDITION, FROM A
  306. NETWORK (X86-BASED COMPUTERS ONLY)
  307. 1. On a network server, share the installation files, either by
  308. inserting the CD and sharing the CD-ROM drive or by copying the
  309. files from the I386 folder on the CD to a shared folder.
  310. 2. On the computer on which you want to install Windows Server
  311. 2003, Enterprise Edition, connect to the shared Setup files:
  312. * If you are sharing the CD-ROM drive, connect to the shared
  313. drive and change to the I386 folder.
  314. * If you are sharing a folder, connect to that folder.
  315. 3. Find and run the appropriate file in the I386 directory of the
  316. CD or in the shared folder:
  317. * From a computer running MS-DOS or Windows 3.x, run Winnt.exe.
  318. * From a computer running Microsoft Windows 95, Windows 98,
  319. Windows Millennium Edition, Windows NT with Service Pack 5 or
  320. later, Windows 2000, or Windows XP, run Winnt32.exe.
  321. 4. Follow the Setup instructions.
  322. ======================================================================
  323. 5.0 STARTING SETUP ON AN ITANIUM ARCHITECTURE-BASED COMPUTER
  324. ======================================================================
  325. This section explains how to start Setup for a new installation on an
  326. Itanium architecture-based computer. For an explanation of how
  327. to start Setup on an x86-based computer, see "Starting Setup on
  328. an x86-based Computer" earlier in this text file.
  329. In computers with the Itanium processor or the Itanium 2 processor,
  330. the Extensible Firmware Interface (EFI) is the interface between a
  331. computer's firmware, hardware, and operating system. The EFI defines a
  332. new partition style called a GUID partition table (GPT), which is
  333. available only for Itanium architecture-based computers. The
  334. installation partition on an Itanium architecture-based computer must
  335. be on a GPT disk. Setup automatically specifies GPT for the disk used
  336. for installation. You can still read and write to
  337. master boot record (MBR) volumes, which are common to most PCs, but
  338. you cannot install on one.
  339. You cannot access GPT disks locally from an x86-based computer. If
  340. you want to move a disk from an Itanium architecture-based computer to
  341. an x86-based computer, use an MBR disk. This is true regardless of
  342. whether the disk is basic or dynamic.
  343. Before installing, verify that you are using the correct version of
  344. the firmware. For more information, refer to the hardware
  345. manufacturer's documentation.
  346. IMPORTANT: Itanium architecture-based computers require a
  347. minimum 100-MB FAT partition for the operation of the EFI. This EFI
  348. system partition is created automatically during Setup, and it
  349. stores programs and information files that the EFI uses to start
  350. the operating system. Do not delete or reformat this partition.
  351. Setup also creates a Microsoft Reserved Partition (MSR), which is
  352. required by the operating system. The size of this partition depends
  353. on the size of the hard disk. On drives less than 16 GB in size, the
  354. MSR is 32 MB. On drives greater than or equal to 16 GB, the MSR is 128
  355. MB. Do not delete or reformat this partition.
  356. >>>TO START SETUP ON AN ITANIUM ARCHITECTURE-BASED COMPUTER
  357. 1. Immediately after turning on the computer, insert the Setup CD
  358. in the CD-ROM drive.
  359. 2. When the EFI Boot Manager menu appears, select the
  360. CD-ROM option.
  361. 3. When prompted, press any key to start from the CD-ROM.
  362. 4. Follow the on-screen Setup instructions.
  363. ======================================================================
  364. 6.0 PLANNING FOR UNATTENDED SETUP
  365. ======================================================================
  366. This section provides general information about unattended Setup. For
  367. detailed instructions on running unattended Setup (also called
  368. automated installation), see "Automating and Customizing
  369. Installations" in the Windows Server 2003 Deployment Kit. You can
  370. view the Windows Deployment and Resource Kits on the Web at:
  371. http://www.microsoft.com/reskit/
  372. To simplify the process of setting up a product in the Windows
  373. Server 2003 family on multiple computers, you can run Setup
  374. unattended. To do this, you create and use an answer file, a
  375. customized script that answers the Setup questions automatically.
  376. Then, you run Winnt32.exe or Winnt.exe with the appropriate options
  377. for unattended Setup. Choose the command according to the operating
  378. system that is running when you start unattended Setup:
  379. * To start unattended Setup on a computer running MS-DOS or
  380. Windows 3.x, use Winnt.exe (with the appropriate options).
  381. * To start unattended Setup on a computer running Windows 95,
  382. Windows 98, Windows Millennium Edition, Windows NT,
  383. Windows 2000, Windows XP, or a product in the Windows
  384. Server 2003 family, use Winnt32.exe (with the appropriate
  385. options). With Windows NT 4.0, before starting unattended Setup,
  386. apply Service Pack 5 or later.
  387. To learn about unattended Setup, see the following sources:
  388. * For detailed instructions on running unattended Setup (also
  389. called automated installation): See "Automating and Customizing
  390. Installations" in the Windows Server 2003 Deployment Kit
  391. (described in the first paragraph of this section).
  392. * To view the command options available for Winnt.exe: On a
  393. computer running Windows 3.x or MS-DOS, insert the Setup CD
  394. for Windows Server 2003, Enterprise Edition, in the CD-ROM
  395. drive and open the command prompt. Then, change to the CD-ROM
  396. drive, change to the I386 directory, and type:
  397. winnt /?
  398. * To use an x86-based computer to view the command options
  399. available for Winnt32.exe: On a computer running Windows 95,
  400. Windows 98, Windows Millennium Edition, Windows NT,
  401. Windows 2000, Windows XP, or a product in the Windows
  402. Server 2003 family, insert the Setup CD for Windows
  403. Server 2003, Enterprise Edition, in the CD-ROM drive, and
  404. open the command prompt. Then, change to the CD-ROM drive, change
  405. to the I386 directory, and type:
  406. winnt32 /?
  407. * To use an Itanium architecture-based computer to view the
  408. command options available for Winnt32.exe: On an Itanium
  409. architecture-based computer running Windows XP 64-Bit Edition;
  410. the 64-bit version of Windows Server 2003, Enterprise
  411. Edition; or the 64-bit version of Windows Server 2003,
  412. Datacenter Edition, insert the Setup CD for the 64-bit version
  413. of the product in the CD-ROM drive and open the command prompt
  414. (click Start, click Run, and then type cmd). Then, change to the
  415. CD-ROM drive, change to the IA64 directory, and type:
  416. winnt32 /?
  417. ======================================================================
  418. 7.0 ENTERING SERVER SETTINGS FOR A NEW INSTALLATION
  419. ======================================================================
  420. If you are upgrading, you can skip this section because Setup will
  421. use your previous settings.
  422. After you start Setup, a process begins in which necessary Setup
  423. files are copied to the hard disk. During this process, Setup displays
  424. dialog boxes that you can use to select various options.
  425. The following sections outline the items that you specify as you run
  426. Setup. Before working with these sections, see EntSrv2.TXT
  427. and EntSrv3.TXT for important background information about issues such
  428. as partitions, file system choices, and the handling of TCP/IP name
  429. resolution. You can modify some settings after running Setup by using
  430. the Configure Your Server Wizard or other configuration tools.
  431. Note: If you have a mass storage controller (such as a SCSI, RAID,
  432. or Fibre Channel adapter) for your hard disk, see "Providing a Mass
  433. Storage Driver or a HAL File" earlier in this text file.
  434. If you have specialized hardware that requires a custom Hardware
  435. Abstraction Layer (HAL) file supplied by your computer manufacturer,
  436. see "Using a Custom HAL File" earlier in this text file.
  437. Choosing or Creating a Partition for Windows Server 2003,
  438. Enterprise Edition
  439. --------------------------------------------------------------
  440. During a new installation of Windows Server 2003, Enterprise
  441. Edition, a dialog box gives you the opportunity to create or specify a
  442. partition on which you want to install. You can create a partition
  443. from the available unpartitioned space, specify an existing partition,
  444. or delete an existing partition to create more unpartitioned disk
  445. space for the new installation. If you specify any action that will
  446. cause information to be erased, you will be prompted to confirm
  447. your choice.
  448. For more information, see the section on planning partitions for new
  449. installations in EntSrv3.TXT.
  450. IMPORTANT: If you delete an existing partition, all data on that
  451. partition is erased.
  452. Performing a new installation of Windows Server 2003,
  453. Enterprise Edition, on a partition that contains another operating
  454. system overwrites the existing operating system.
  455. Selecting Regional and Language Options
  456. ---------------------------------------
  457. You can set up Windows Server 2003, Enterprise Edition, to use
  458. multiple languages and regional options.
  459. If you select a European country or region in the list of
  460. countries/regions, or if you live in a country or region where the
  461. euro has been introduced, it is a good idea to verify that the default
  462. currency settings in Regional and Language Options meet your needs.
  463. After you run Setup, you can modify these options by clicking Regional
  464. and Language Options in Control Panel.
  465. Personalizing Windows
  466. ---------------------
  467. Enter your name and, as an option, your organization.
  468. If you select a European country or region in the list of
  469. countries/regions, or if you live in a country or region where the
  470. euro has been introduced, it is a good idea to verify that the default
  471. currency settings in Regional and Language Options meet your needs.
  472. After you run Setup, you can modify regional and language options by
  473. clicking Regional and Language Options in Control Panel.
  474. Choosing a Licensing Mode
  475. -------------------------
  476. Select your client licensing mode. For information about licensing
  477. modes, see EntSrv2.TXT. If you are unsure which mode to use, select
  478. "Per Server," because you can change once from "Per Server" mode to
  479. "Per Device or Per User" mode at no cost.
  480. Entering Your Computer Name
  481. ---------------------------
  482. During Setup, in the Computer Name and Administrator Password dialog
  483. box, follow the instructions for entering your computer name. The
  484. recommended length for most languages is 15 characters or less. For
  485. languages that require more storage space per character, such as
  486. Chinese, Japanese, and Korean, the recommended length is 7 characters
  487. or less.
  488. It is recommended that you use only Internet-standard characters in
  489. the computer name. The standard characters are the numbers from 0
  490. through 9, uppercase and lowercase letters from A through Z, and the
  491. hyphen (-) character. Computer names cannot consist entirely
  492. of numbers.
  493. If you are using DNS on your network, you can use a wider variety of
  494. characters, including Unicode characters and other nonstandard
  495. characters, such as the ampersand (&). Using nonstandard characters
  496. might affect the ability of non-Microsoft software to operate on your
  497. network. For more information about DNS, see the "Name Resolution for
  498. TCP/IP" section in EntSrv3.TXT.
  499. The maximum length for a computer name is 63 bytes. If the name is
  500. longer than 15 bytes (15 characters in most languages, 7 characters in
  501. some), computers running Windows NT Server 4.0 and earlier will
  502. recognize this computer by the first 15 bytes of the name only. In
  503. addition, there are additional configuration steps for a name that is
  504. longer than 15 bytes. For more information, in Help and Support
  505. Center, see "Namespace planning for DNS." To view Help and Support
  506. Center, after running Setup, click Start, and then click Help
  507. and Support.
  508. If a computer is part of a domain, you must choose a computer name
  509. that is different from any other computer in the domain. To avoid name
  510. conflicts, the computer should be unique on the domain, workgroup, or
  511. network. If this computer is part of a domain, and it contains more
  512. than one operating system, you must use a unique computer name for
  513. each operating system that is installed. For example, if the computer
  514. name is FileServerNT when the computer is started with Windows NT
  515. Server 4.0, the computer must have a different name, perhaps
  516. FileServerNew, when it is started with a product in the Windows
  517. Server 2003 family. This requirement also applies to a computer that
  518. contains multiple installations of the same operating system. For more
  519. information, in Help and Support Center, see "Planning your domain
  520. structure."
  521. Setting the Administrator Account Password
  522. ------------------------------------------
  523. During Setup, in the Computer Name and Administrator Password dialog
  524. box, type a password of up to 127 characters in the Administrator
  525. Password box. For the strongest system security, use a password of at
  526. least 7 characters, and use a mixture of uppercase and lowercase
  527. letters, numbers, and other characters, such as *, ?, or $.
  528. IMPORTANT: After Setup is completed, for best security, change the
  529. name of the Administrator account (it cannot be deleted) and keep a
  530. strong password on the account at all times. For more information
  531. about security and the administrative rights and permissions held
  532. by the Administrator account and the Administrators group, see Help
  533. and Support Center. You can view Help and Support Center after
  534. Setup is complete by clicking Start, and then clicking Help and
  535. Support.
  536. Setting the Date and Time
  537. -------------------------
  538. During Setup, in the Date and Time Settings dialog box, set the date,
  539. time, and time zone. If you want the system to automatically adjust
  540. for daylight saving time, select the "Automatically adjust clock for
  541. daylight saving changes" check box.
  542. You can change your computer's date and time after Setup is complete.
  543. If your computer is a member of a domain, your computer clock is
  544. probably synchronized automatically by a network time server. If your
  545. computer is not a member of a domain, you can synchronize your
  546. computer clock with an Internet time server.
  547. Specifying Networking Settings
  548. ------------------------------
  549. You can specify networking information for TCP/IP or other protocols
  550. during Setup, or you can use typical settings and then make any
  551. necessary changes to your networking configuration after installation.
  552. For basic background information about TCP/IP configuration and
  553. Setup, see "Networks: TCP/IP, IP Addresses, and Name Resolution"
  554. in EntSrv3.TXT. For additional information about TCP/IP configuration,
  555. see Help and Support Center as well as the Windows Deployment and
  556. Resource Kits for the Windows Server 2003 family. To open Help
  557. and Support Center, after completing Setup, click Start, and then
  558. click Help and Support.
  559. >>>TO ALLOW SETUP TO ASSIGN OR OBTAIN AN IP ADDRESS
  560. * When you click "Typical settings" in the Networking Settings
  561. dialog box, Setup checks to see if there is a DHCP server on
  562. your network. If there is a DHCP server on your network, DHCP
  563. provides an IP address. If there is no DHCP server on your
  564. network, Setup will use a limited IP addressing option called
  565. Automatic Private IP Addressing (APIPA). On a server using
  566. APIPA, complete the network configuration after Setup, because
  567. a server using APIPA can communicate only with other computers
  568. using APIPA on the same network segment.
  569. For basic background information about IP address configuration,
  570. including additional information about the limitations of
  571. APIPA, see "IP Addresses" in EntSrv3.TXT.
  572. >>>TO SPECIFY A STATIC IP ADDRESS AND SETTINGS NEEDED FOR DNS AND
  573. WINS
  574. 1. During Setup, in the Networking Settings dialog box, click
  575. "Custom settings," and then click Next.
  576. 2. In the Networking Components dialog box, click Internet
  577. Protocol (TCP/IP).
  578. 3. Click Properties.
  579. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click
  580. "Use the following IP address."
  581. 5. In IP address, Subnet mask, and Default gateway, type the
  582. appropriate addresses.
  583. 6. Under "Use the following DNS server addresses," type the address
  584. of a preferred DNS server and, optionally, an alternate
  585. DNS server.
  586. If the local server is the preferred or alternate DNS server,
  587. type the same IP address as assigned in the previous step.
  588. 7. If you will use a WINS server, click Advanced, and then click
  589. the WINS tab in the Advanced TCP/IP Settings dialog box to add
  590. the IP address of one or more WINS servers.
  591. 8. Click OK in each dialog box, and continue with Setup.
  592. Specifying the Workgroup or Domain Name
  593. ---------------------------------------
  594. A domain is a group of accounts and network resources that share a
  595. common directory database and set of security policies and might have
  596. security relationships with other domains. A workgroup is a more basic
  597. grouping, intended only to help users find objects such as printers
  598. and shared folders within that group. Domains make it easier for an
  599. administrator to control access to resources and keep track of users.
  600. For more information, see "Deciding Between Workgroups and Domains"
  601. in EntSrv3.TXT.
  602. For more information about name conflicts, see "Entering Your
  603. Computer Name" earlier in this text file.
  604. ======================================================================
  605. 8.0 CONFIGURING YOUR SERVER
  606. ======================================================================
  607. When Setup is complete, the computer restarts. Setup has now
  608. completed the basic installation. Manage Your Server appears on the
  609. screen the first time you log on as the computer's administrator. You
  610. can use Manage Your Server to install and configure server roles,
  611. including file servers, print servers, Web and media servers, and
  612. networking and communications servers. You can start Manage Your
  613. Server at any time if you are logged on as an administrator. To start
  614. Manage Your Server, click Start, and then either click Manage Your
  615. Server or point to All Programs, point to Administrative Tools, and
  616. then click Manage Your Server.
  617. Also at this point, you can view Help and Support Center by clicking
  618. Start, and then clicking Help and Support. If you have used Windows NT
  619. in the past, one topic you might find useful is "New ways to do
  620. familiar tasks," which is available in the online Help topics or
  621. through use of the Search feature in Help and Support Center.
  622. Choosing Server Components
  623. --------------------------
  624. You can use the Windows Components Wizard to select the appropriate
  625. components for your server. To use this wizard, after running Setup,
  626. click Start, and then click Control Panel. In Control Panel,
  627. double-click Add or Remove Programs, and then, on the left side of the
  628. dialog box, click Add/Remove Windows Components. With this wizard you
  629. can choose and install individual components.
  630. ======================================================================
  631. 9.0 PRODUCT ACTIVATION FOR PRODUCTS IN THE WINDOWS SERVER 2003
  632. FAMILY
  633. ======================================================================
  634. After you install a product in the Windows Server 2003 family,
  635. if the product was purchased individually rather than through a volume
  636. licensing arrangement, you will have to activate the product unless
  637. your hardware manufacturer has preactivated it for you. Product
  638. activation is quick, simple, and unobtrusive, and it protects your
  639. privacy. It is designed to reduce software piracy (illegal copies of a
  640. product). Over time, reduced piracy means that the software industry
  641. can invest more in product development, quality, and support. This
  642. results in better products and more innovation for customers.
  643. The following details help explain product activation:
  644. Software reminders
  645. ------------------
  646. Until you activate your product, it provides a reminder each time you
  647. log on and at common intervals until the end of the activation grace
  648. period stated in your End-User License Agreement (30 days is the
  649. typical grace period). If your activation grace period passes and you
  650. do not activate the product, your computer will continue to function,
  651. except that when you log on locally or log on through Remote Desktop
  652. for Administration (the new name for the Windows 2000 functionality
  653. known as Terminal Services in Remote Administration Mode), you will
  654. only be able to use the Activate Windows Wizard.
  655. How the software handles activation
  656. -----------------------------------
  657. Activation is simple and anonymous. When you activate your product,
  658. it means that your product key is now associated with the computer
  659. (the hardware) it is installed on. After that happens, your product
  660. key cannot be used for activation on other computers (unless you are
  661. enrolled in a special program that permits additional activations, for
  662. example, a program through the Microsoft Developer Network (MSDN)).
  663. Your local operating system does some of the work of creating the
  664. association between your product key and the computer it is installed
  665. on. It uses your Product ID, which is derived from your product key,
  666. and puts it together with a coded number (called a hardware hash) that
  667. uniquely represents the hardware components that make up your computer
  668. (without representing any personal information or anything about the
  669. software). When you activate, you provide this number, through the
  670. Internet or by phone, so that it can be confirmed as representing a
  671. legal installation. After you activate, if another person has an
  672. illegal copy of your software, and that person tries to use your
  673. product key to activate the software on another computer, the coded
  674. numbers will show that your product key is already associated with a
  675. particular set of hardware (your computer). The other person's
  676. activation will not work.
  677. The Installation ID that the local operating system generates,
  678. representing the association between your product key and the computer
  679. it is installed on, is used only for the purpose of activation.
  680. Methods for activation
  681. ----------------------
  682. After your operating system is installed, begin activation by
  683. clicking Start, and then clicking Activate Windows. (You can also
  684. click the key icon that appears in the lower right corner of the
  685. screen.) By following the instructions on the screen, you can activate
  686. through the Internet or by phone:
  687. * Internet: When you activate through the Internet, your computer
  688. transmits coded information that shows that your product key
  689. is associated with your computer hardware. Activation is
  690. carried out through a secure server. A confirmation ID is
  691. passed back to your computer, automatically activating your
  692. product. This process normally takes just a few seconds to
  693. complete. No personally identifiable information is required
  694. to activate your product.
  695. * Phone: When you activate by phone, information on the screen
  696. guides you through a few simple steps. When you choose the
  697. country or region where you are located, a phone number
  698. (toll-free, wherever possible) appears on your screen. When you
  699. call the number, a customer service representative asks for the
  700. Installation ID that is displayed on your screen. The customer
  701. service representative enters that number into a secure
  702. database, confirms that the number represents a legally
  703. installed product, and provides a confirmation ID to you. Then,
  704. you type the confirmation ID into the spaces provided on the
  705. screen, and activation is complete.
  706. Reactivation (rarely needed)
  707. ----------------------------
  708. If you overhaul your computer by replacing a substantial number of
  709. hardware components (not just a few), the operating system might view
  710. your hardware as a completely different computer, not the one on which
  711. you activated. In this situation, you can call the telephone number
  712. displayed on the telephone activation screen, and, through a quick,
  713. simple process, you can reactivate your product.
  714. ---------------------------------------------------------
  715. 9.1 Product Activation Compared to Product Registration
  716. ---------------------------------------------------------
  717. Product activation is not the same as product registration. As
  718. discussed above, product activation is required, and it is completely
  719. anonymous. Product registration, in contrast, is completely optional,
  720. and it allows you to provide personal information, such as your e-mail
  721. address, if you choose. Registration entitles you to receive
  722. information about product updates and special offers directly from
  723. Microsoft. All registration information provided is stored securely,
  724. and no information is ever loaned or sold to other parties.
  725. (additional Setup information in EntSrv5.txt)
  726. Information in this document, including URL and other Internet
  727. Web site references, is subject to change without notice.
  728. Unless otherwise noted, the example companies, organizations,
  729. products, domain names, e-mail addresses, logos, people, places
  730. and events depicted herein are fictitious, and no association
  731. with any real company, organization, product, domain name,
  732. e-mail address, logo, person, place or event is intended or
  733. should be inferred. Complying with all applicable copyright laws
  734. is the responsibility of the user. Without limiting the rights
  735. under copyright, no part of this document may be reproduced,
  736. stored in or introduced into a retrieval system, or transmitted
  737. in any form or by any means (electronic, mechanical, photocopying,
  738. recording, or otherwise), or for any purpose, without the express
  739. written permission of Microsoft Corporation.
  740. Microsoft may have patents, patent applications, trademarks,
  741. copyrights, or other intellectual property rights covering subject
  742. matter in this document. Except as expressly provided in any
  743. written license agreement from Microsoft, the furnishing of this
  744. document does not give you any license to these patents, trademarks,
  745. copyrights, or other intellectual property.
  746. (c) 2002-2003 Microsoft Corporation. All rights reserved.
  747. The names of actual companies and products mentioned herein may
  748. be the trademarks of their respective owners.