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.

626 lines
29 KiB

  1. **********************************************************************
  2. Windows Server 2003, Web Edition
  3. Setup Text Files, Part 2 of 2:
  4. Running Setup for a New Installation
  5. **********************************************************************
  6. (c) 2003 Microsoft Corporation. All rights reserved.
  7. This part of the text file series provides recommendations for
  8. preparing your system for a new installation, and it explains how to
  9. run Setup for Microsoft Windows Server 2003, Web Edition.
  10. For more information about the deployment of servers, see the
  11. Windows Server 2003 Deployment Kit. You can view the Windows
  12. Deployment and Resource Kits on the Web at:
  13. http://www.microsoft.com/reskit/
  14. The following list of headings can help you find the information
  15. about running Setup that applies to you. For information about
  16. planning a new installation, see WebSrv1.TXT.
  17. Contents
  18. --------
  19. 1.0 Preparing Your System for a New Installation
  20. 2.0 Starting Setup
  21. 3.0 Planning for Unattended Setup
  22. 4.0 Entering Server Settings for a New Installation
  23. 5.0 Configuring Your Web Server
  24. 6.0 Product Activation for Products in the Windows
  25. Server 2003 Family
  26. ======================================================================
  27. 1.0 PREPARING YOUR SYSTEM FOR A NEW INSTALLATION
  28. ======================================================================
  29. This section describes the basic steps to take in preparing your
  30. server for a new installation.
  31. ----------------------------------------
  32. 1.1 Checking the System Log for Errors
  33. ----------------------------------------
  34. If the computer already has a working operating system, review the
  35. system log for recent or recurring errors (especially hardware errors)
  36. that could cause problems during the installation. For information
  37. about viewing event logs, see Help for the operating system on
  38. your computer.
  39. ----------------------
  40. 1.2 Backing Up Files
  41. ----------------------
  42. Before you perform a new installation, it is recommended that you
  43. back up your current files, unless the computer has no files or the
  44. current operating system files have been damaged. You can back up
  45. files to a variety of different media, such as a tape drive or the
  46. hard disk of another computer on the network.
  47. -------------------------------
  48. 1.3 Disconnecting UPS Devices
  49. -------------------------------
  50. If you have an uninterruptible power supply (UPS) connected to your
  51. target computer, disconnect the connecting serial cable before running
  52. Setup. Setup automatically attempts to detect devices connected to
  53. serial ports, and UPS equipment can cause problems with the detection
  54. process.
  55. ======================================================================
  56. 2.0 STARTING SETUP
  57. ======================================================================
  58. This section explains how to start Setup for a new installation.
  59. Setup works in several stages, prompting you for information, copying
  60. files, and restarting.
  61. For important information to help you make the initial choices offered
  62. by Setup, see WebSrv1.TXT. For information about unattended Setup and
  63. other options available when you start Setup, see "Planning for
  64. Unattended Setup" later in this text file.
  65. ---------------------------------------------------
  66. 2.1 Providing a Mass Storage Driver or a HAL File
  67. ---------------------------------------------------
  68. If you have a mass storage controller that requires a driver supplied
  69. by the manufacturer, or if you have a custom Hardware Abstraction
  70. Layer (HAL) file supplied by the manufacturer, provide the appropriate
  71. driver file or HAL file during Setup.
  72. 2.1.1 Mass Storage Drivers and the Setup Process
  73. -------------------------------------------------
  74. If you have a mass storage controller (such as a SCSI, RAID, or Fibre
  75. Channel adapter) for your hard disk, confirm that the controller is
  76. designed for products in the Windows Server 2003 family by checking
  77. the hardware and software compatibility information in the Windows
  78. Catalog at:
  79. http://www.microsoft.com/windows/catalog/
  80. If your controller is compatible, but you are aware that the
  81. manufacturer has supplied a separate driver file for use with products
  82. in the Windows Server 2003 family, obtain the file (on a floppy disk)
  83. before you begin Setup. During the early part of Setup, a line at the
  84. bottom of the screen prompts you to press F6. Further prompts will
  85. guide you in supplying the driver file to Setup so that it can gain
  86. access to the mass storage controller.
  87. If you are not sure whether you must obtain a separate driver file
  88. from the manufacturer of your mass storage controller, you can try
  89. running Setup. If the controller is not supported by the driver files
  90. on the Setup CD and therefore requires a driver file that is supplied
  91. by the hardware manufacturer, Setup stops and displays a message saying
  92. that no disk devices can be found, or it displays an incomplete list of
  93. controllers. After you obtain the necessary driver file, restart Setup,
  94. and press F6 when you are prompted.
  95. 2.1.2 Using a Custom HAL File
  96. -------------------------------
  97. If you have a custom Hardware Abstraction Layer (HAL) file supplied
  98. by your computer manufacturer, before you begin Setup, locate the
  99. floppy disk or other medium containing the file. During the early part
  100. of Setup, a line at the bottom of the screen prompts you to press F6:
  101. at this time press F5 (not F6). After you press F5, follow the prompts
  102. to include your HAL file in the Setup process.
  103. --------------------------------
  104. 2.2 Methods for Starting Setup
  105. --------------------------------
  106. The sections that follow, "Starting a New Installation from a CD" and
  107. "Starting a New Installation from a Network," explain how to start
  108. Setup for a new installation.
  109. For information about unattended Setup and other options available
  110. when you start Setup, see "Planning for Unattended Setup" later in
  111. this text file.
  112. 2.2.1 Starting a New Installation from a CD
  113. ---------------------------------------------
  114. If you use the Setup CD, you have several options for starting Setup,
  115. as explained in the following procedures.
  116. Note: If you are running Setup on a computer running Windows 3.x or
  117. MS-DOS, for best efficiency, use disk caching. Otherwise, the Setup
  118. process (started from Winnt.exe) could take a long time. To enable
  119. disk caching on a computer running Windows 3.x or MS-DOS, you can
  120. use SMARTDrive. For information about SMARTDrive, see the
  121. documentation for Windows 3.x or MS-DOS.
  122. >>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING MS-DOS
  123. 1. Insert the CD in the drive.
  124. 2. At the command prompt, type:
  125. d:
  126. where d is the drive letter of the CD-ROM drive.
  127. 3. Type:
  128. cd i386
  129. 4. Type:
  130. winnt
  131. 5. Follow the Setup instructions.
  132. >>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING WINDOWS
  133. Before starting this procedure on a computer running
  134. Windows NT 4.0, apply Service Pack 5 or later.
  135. 1. Insert the CD in the drive.
  136. 2. To begin Setup, do one of the following:
  137. * For a computer running any version of Windows other than
  138. Windows 3.x, wait for Setup to display a dialog box.
  139. * For a computer running Windows 3.x, use File Manager to change
  140. to the CD-ROM drive and to change to the I386 directory, and
  141. then double-click Winnt.exe.
  142. 3. Follow the Setup instructions.
  143. >> TO START SETUP FOR A NEW INSTALLATION FROM THE CD
  144. Another way of using the Setup CD is to start the computer from the
  145. CD-ROM drive. Using this method, you can perform an installation on a
  146. computer that does not have an operating system, although you can also
  147. use this method on computers that have operating systems.
  148. 1. Determine whether the computer on which you want to start Setup
  149. can be started from the CD-ROM drive.
  150. 2. Insert the CD in the drive, and then restart the computer.
  151. 3. Follow the instructions for your operating system to boot the
  152. computer from the CD.
  153. 4. Wait for Setup to display a dialog box, and then follow the
  154. Setup instructions.
  155. 2.2.2 Starting a New Installation from a Network
  156. -------------------------------------------------
  157. To install Windows Server 2003, Web Edition, from a network, you
  158. either share the files directly from the CD or copy them to a shared
  159. folder. Then, you start the appropriate program to run Setup.
  160. >>>TO INSTALL WINDOWS SERVER 2003, WEB EDITION, FROM A NETWORK
  161. 1. On a network server, share the installation files, either by
  162. inserting the CD and sharing the CD-ROM drive or by copying the
  163. files from the I386 folder on the CD to a shared folder.
  164. 2. On the computer on which you want to install Windows Server 2003,
  165. Web Edition, connect to the shared Setup files:
  166. * If you are sharing the CD-ROM drive, connect to the shared
  167. drive and change to the I386 folder.
  168. * If you are sharing a folder, connect to that folder.
  169. 3. Find and run the appropriate file in the I386 directory of the
  170. CD or in the shared folder:
  171. * From a computer running MS-DOS or Windows 3.x, run Winnt.exe.
  172. * From a computer running Microsoft Windows 95, Windows 98,
  173. Windows Millennium Edition, Windows NT with Service Pack 5 or later,
  174. Windows 2000, or Windows XP, run Winnt32.exe.
  175. 4. Follow the Setup instructions.
  176. ======================================================================
  177. 3.0 PLANNING FOR UNATTENDED SETUP
  178. ======================================================================
  179. This section provides general information about unattended Setup. For
  180. detailed instructions on running unattended Setup (also called
  181. automated installation), see "Automating and Customizing Installations"
  182. in the Windows Server 2003 Deployment Kit. You can view the Windows
  183. Deployment and Resource Kits on the Web at:
  184. http://www.microsoft.com/reskit/
  185. To simplify the process of setting up a product in the Windows
  186. Server 2003 family on multiple computers, you can run Setup
  187. unattended. To do this, you create and use an answer file, a
  188. customized script that answers the Setup questions automatically.
  189. Then, you run Winnt32.exe or Winnt.exe with the appropriate options
  190. for unattended Setup. Choose the command according to the operating
  191. system that is running when you start unattended Setup:
  192. * To start unattended Setup on a computer running MS-DOS or
  193. Windows 3.x, use Winnt.exe (with the appropriate options).
  194. * To start unattended Setup on a computer running Windows 95,
  195. Windows 98, Windows Millennium Edition, Windows NT, Windows 2000,
  196. Windows XP, or a product in the Windows Server 2003 family,
  197. use Winnt32.exe (with the appropriate options). With Windows NT 4.0,
  198. before starting unattended Setup, apply Service Pack 5 or later.
  199. To learn about unattended Setup, see the following sources:
  200. * For detailed instructions on running unattended Setup (also
  201. called automated installation): See "Automating and Customizing
  202. Installations" in the Windows Server 2003 Deployment Kit
  203. (described in the first paragraph of this section).
  204. * To view the command options available for Winnt.exe: On a
  205. computer running Windows 3.x or MS-DOS, insert the Setup CD for
  206. Windows Server 2003, Web Edition, in the CD-ROM drive and
  207. open the command prompt. Then, change to the CD-ROM drive, change
  208. to the I386 directory, and type:
  209. winnt /?
  210. * To use an x86-based computer to view the command options
  211. available for Winnt32.exe: On a computer running Windows 95,
  212. Windows 98, Windows Millennium Edition, Windows NT, Windows 2000,
  213. Windows XP, or a product in the Windows Server 2003 family,
  214. insert the Setup CD for Windows Server 2003, Web Edition, in
  215. the CD-ROM drive, and open the command prompt. Then, change to
  216. the CD-ROM drive, change to the I386 directory, and type:
  217. winnt32 /?
  218. * To use an Itanium architecture-based computer to view the command
  219. options available for Winnt32.exe: On an Itanium architecture-based
  220. computer running Windows XP 64-Bit Edition; the 64-bit version of
  221. Windows Server 2003, Enterprise Edition; or the 64-bit version of
  222. Windows Server 2003, Datacenter Edition, insert the Setup CD for
  223. the 64-bit version of the product in the CD-ROM drive and open the
  224. command prompt (click Start, click Run, and then type cmd). Then,
  225. change to the CD-ROM drive, change to the IA64 directory, and type:
  226. winnt32 /?
  227. ======================================================================
  228. 4.0 ENTERING SERVER SETTINGS FOR A NEW INSTALLATION
  229. ======================================================================
  230. After you start Setup, a process begins in which necessary Setup files
  231. are copied to the hard disk. During this process, Setup displays
  232. dialog boxes that you can use to select various options.
  233. The following sections outline the items that you specify as you run
  234. Setup. Before working with these sections, see WebSrv1.TXT for
  235. important background information about issues such as partitions, file
  236. system choices, and the handling of TCP/IP name resolution.
  237. Note: If you have a mass storage controller (such as a SCSI, RAID,
  238. or Fibre Channel adapter) for your hard disk, see "Providing a Mass
  239. Storage Driver or a HAL File" earlier in this text file.
  240. If you have specialized hardware that requires a custom Hardware
  241. Abstraction Layer (HAL) file supplied by your computer manufacturer,
  242. see "Using a Custom HAL File" earlier in this text file.
  243. Choosing or Creating a Partition for Windows Server 2003,
  244. Web Edition
  245. ------------------------------------------------------------------
  246. During a new installation of Windows Server 2003, Web Edition, a
  247. dialog box gives you the opportunity to create or specify a partition
  248. on which you want to install. You can create a partition from the
  249. available unpartitioned space, specify an existing partition, or
  250. delete an existing partition to create more unpartitioned disk space
  251. for the new installation. If you specify any action that will cause
  252. information to be erased, you will be prompted to confirm your choice.
  253. For more information, see the section on planning partitions for new
  254. installations in WebSrv1.TXT.
  255. IMPORTANT: If you delete an existing partition, all data on that
  256. partition is erased. Performing a new installation of Windows
  257. Server 2003, Web Edition, on a partition that contains another
  258. operating system overwrites the existing operating system.
  259. Selecting Regional and Language Options
  260. ---------------------------------------
  261. You can set up Windows Server 2003, Web Edition, to use multiple
  262. languages and regional options.
  263. If you select a European country or region in the list of
  264. countries/regions, or if you live in a country or region where the
  265. euro has been introduced, it is a good idea to verify that the default
  266. currency settings in Regional and Language Options meet your needs.
  267. After you run Setup, you can modify these options by clicking Regional
  268. and Language Options in Control Panel.
  269. Personalizing Windows
  270. ---------------------
  271. Enter your name and, as an option, your organization.
  272. Entering Your Computer Name
  273. ---------------------------
  274. During Setup, in the Computer Name and Administrator Password dialog
  275. box, follow the instructions for entering your computer name. The
  276. recommended length for most languages is 15 characters or less. For
  277. languages that require more storage space per character, such as
  278. Chinese, Japanese, and Korean, the recommended length is 7 characters
  279. or less.
  280. It is recommended that you use only Internet-standard characters in
  281. the computer name. The standard characters are the numbers from 0
  282. through 9, uppercase and lowercase letters from A through Z, and the
  283. hyphen (-) character. Computer names cannot consist entirely
  284. of numbers.
  285. If you are using DNS on your network, you can use a wider variety of
  286. characters, including Unicode characters and other nonstandard
  287. characters, such as the ampersand (&). Using nonstandard characters
  288. might affect the ability of non-Microsoft software to operate on your
  289. network. For more information about DNS, see "Name
  290. Resolution for TCP/IP" in WebSrv1.TXT.
  291. The maximum length for a computer name is 63 bytes. If the name is
  292. longer than 15 bytes (15 characters in most languages, 7 characters in
  293. some), computers running Windows NT Server 4.0 and earlier will
  294. recognize this computer by the first 15 bytes of the name only. In
  295. addition, there are additional configuration steps for a name that is
  296. longer than 15 bytes. For more information, in Help and Support
  297. Center, see "Namespace planning for DNS." To view Help and Support
  298. Center, after running Setup, click Start, and then click Help
  299. and Support.
  300. If a computer is part of a domain, you must choose a computer name
  301. that is different from any other computer in the domain. To avoid name
  302. conflicts, the computer should be unique on the domain, workgroup, or
  303. network. If this computer is part of a domain, and it contains more
  304. than one operating system, you must use a unique computer name for
  305. each operating system that is installed. For example, if the computer
  306. name is FileServerNT when the computer is started with Windows NT
  307. Server 4.0, the computer must have a different name, perhaps
  308. FileServerNew, when it is started with a product in the Windows
  309. Server 2003 family. This requirement also applies to a computer that
  310. contains multiple installations of the same operating system. For more
  311. information, in Help and Support Center, see "Planning your domain
  312. structure."
  313. Setting the Administrator Account Password
  314. ------------------------------------------
  315. During Setup, in the Computer Name and Administrator Password dialog
  316. box, type a password of up to 127 characters in the Administrator
  317. Password box. For the strongest system security, use a password of at
  318. least 7 characters, and use a mixture of uppercase and lowercase
  319. letters, numbers, and other characters, such as *, ?, or $.
  320. IMPORTANT: After Setup is completed, for best security, change the
  321. name of the Administrator account (it cannot be deleted) and keep a
  322. strong password on the account at all times. For more information
  323. about security and the administrative rights and permissions held
  324. by the Administrator account and the Administrators group, see Help
  325. and Support Center. You can view Help and Support Center after
  326. Setup is complete by clicking Start, and then clicking Help
  327. and Support.
  328. Setting the Date and Time
  329. -------------------------
  330. During Setup, in the Date and Time Settings dialog box, set the date,
  331. time, and time zone. If you want the system to automatically adjust
  332. for daylight saving time, select the "Automatically adjust clock for
  333. daylight saving changes" check box.
  334. You can change your computer's date and time after Setup is complete.
  335. If your computer is a member of a domain, your computer clock is
  336. probably synchronized automatically by a network time server. If your
  337. computer is not a member of a domain, you can synchronize your
  338. computer clock with an Internet time server.
  339. Specifying Networking Settings
  340. ------------------------------
  341. You can specify networking information for TCP/IP or other protocols
  342. during Setup, or you can use typical settings and then make any
  343. necessary changes to your networking configuration after installation.
  344. For basic background information about TCP/IP configuration and Setup,
  345. see "Networks: TCP/IP, IP Addresses, and Name Resolution" in WebSrv1.TXT.
  346. >>>TO ALLOW SETUP TO ASSIGN OR OBTAIN AN IP ADDRESS
  347. * When you click "Typical settings" in the Networking Settings
  348. dialog box, Setup checks to see if there is a DHCP server on your
  349. network. If there is a DHCP server on your network, DHCP provides
  350. an IP address. If there is no DHCP server on your network, Setup
  351. will use a limited IP addressing option called Automatic Private
  352. IP Addressing (APIPA). On a server using APIPA, complete the
  353. network configuration after Setup, because a server using APIPA
  354. can communicate only with other computers using APIPA on the same
  355. network segment.
  356. For basic background information about IP address configuration,
  357. including additional information about the limitations of APIPA,
  358. see "IP Addresses" in WebSrv1.TXT.
  359. >>>TO SPECIFY A STATIC IP ADDRESS AND SETTINGS NEEDED FOR DNS AND WINS
  360. 1. During Setup, in the Networking Settings dialog box, click
  361. "Custom settings," and then click Next.
  362. 2. In the Networking Components dialog box, click Internet
  363. Protocol (TCP/IP).
  364. 3. Click Properties.
  365. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click
  366. "Use the following IP address."
  367. 5. In IP address, Subnet mask, and Default gateway, type the
  368. appropriate addresses.
  369. 6. Under "Use the following DNS server addresses," type the address
  370. of a preferred DNS server and, optionally, an alternate
  371. DNS server.
  372. If the local server is the preferred or alternate DNS server,
  373. type the same IP address as assigned in the previous step.
  374. 7. If you will use a WINS server, click Advanced, and then click
  375. the WINS tab in the Advanced TCP/IP Settings dialog box to add
  376. the IP address of one or more WINS servers.
  377. 8. Click OK in each dialog box, and continue with Setup.
  378. Specifying the Workgroup or Domain Name
  379. ---------------------------------------
  380. A domain is a group of accounts and network resources that share a
  381. common directory database and set of security policies and might have
  382. security relationships with other domains. A workgroup is a more basic
  383. grouping, intended only to help users find objects such as printers
  384. and shared folders within that group. Domains make it easier for an
  385. administrator to control access to resources and keep track of users.
  386. For more information about name conflicts, see "Entering Your
  387. Computer Name" earlier in this text file.
  388. ======================================================================
  389. 5.0 CONFIGURING YOUR WEB SERVER
  390. ======================================================================
  391. The Web Interface for Remote Administration is an HTML-based
  392. application used to configure and manage the server from a remote
  393. client. Individual servers, entire server farms, and multiple sites
  394. per server can be managed from a single remote workstation.
  395. The Web Interface for Remote Administration provides a simple means
  396. of performing common Web server configuration tasks including:
  397. * Creating and deleting Web sites
  398. * Configuring network settings
  399. * Managing local user accounts
  400. * Restarting the Web server
  401. 5.1 Choosing Server Components
  402. --------------------------------
  403. You can use the Windows Components Wizard to select the appropriate
  404. components for your server. To use this wizard, after running Setup,
  405. click Start, and then click Control Panel. In Control Panel,
  406. double-click Add or Remove Programs, and then, on the left side of the
  407. dialog box, click Add/Remove Windows Components. With this wizard you
  408. can choose and install individual components.
  409. ======================================================================
  410. 6.0 PRODUCT ACTIVATION FOR PRODUCTS IN THE
  411. WINDOWS SERVER 2003 FAMILY
  412. ======================================================================
  413. After you install a product in the Windows Server 2003 family,
  414. if the product was purchased individually rather than through a volume
  415. licensing arrangement, you will have to activate the product unless
  416. your hardware manufacturer has preactivated it for you. Product
  417. activation is quick, simple, and unobtrusive, and it protects your
  418. privacy. It is designed to reduce software piracy (illegal copies of a
  419. product). Over time, reduced piracy means that the software industry
  420. can invest more in product development, quality, and support. This
  421. results in better products and more innovation for customers.
  422. The following details help explain product activation:
  423. Software reminders
  424. ------------------
  425. Until you activate your product, it provides a reminder each time you
  426. log on and at common intervals until the end of the activation grace
  427. period stated in your End-User License Agreement (30 days is the
  428. typical grace period). If your activation grace period passes and you
  429. do not activate the product, your computer will continue to function,
  430. except that when you log on locally or log on through Remote Desktop
  431. for Administration (the new name for the Windows 2000 functionality
  432. known as Terminal Services in Remote Administration Mode), you will
  433. only be able to use the Activate Windows Wizard.
  434. How the software handles activation
  435. -----------------------------------
  436. Activation is simple and anonymous. When you activate your product,
  437. it means that your product key is now associated with the computer
  438. (the hardware) it is installed on. After that happens, your product
  439. key cannot be used for activation on other computers (unless you are
  440. enrolled in a special program that permits additional activations, for
  441. example, a program through the Microsoft Developer Network (MSDN)).
  442. Your local operating system does some of the work of creating the
  443. association between your product key and the computer it is installed
  444. on. It uses your Product ID, which is derived from your product key,
  445. and puts it together with a coded number (called a hardware hash) that
  446. uniquely represents the hardware components that make up your computer
  447. (without representing any personal information or anything about the
  448. software). When you activate, you provide this number, through the
  449. Internet or by phone, so that it can be confirmed as representing a
  450. legal installation. After you activate, if another person has an
  451. illegal copy of your software, and that person tries to use your
  452. product key to activate the software on another computer, the coded
  453. numbers will show that your product key is already associated with a
  454. particular set of hardware (your computer). The other person's
  455. activation will not work.
  456. The Installation ID that the local operating system generates,
  457. representing the association between your product key and the computer
  458. it is installed on, is used only for the purpose of activation.
  459. Methods for activation
  460. ----------------------
  461. After your operating system is installed, begin activation by
  462. clicking Start, and then clicking Activate Windows. (You can also
  463. click the key icon that appears in the lower right corner of the
  464. screen.) By following the instructions on the screen, you can activate
  465. through the Internet or by phone:
  466. * Internet: When you activate through the Internet, your computer
  467. transmits coded information that shows that your product key
  468. is associated with your computer hardware. Activation is
  469. carried out through a secure server. A confirmation ID is
  470. passed back to your computer, automatically activating your
  471. product. This process normally takes just a few seconds to
  472. complete. No personally identifiable information is required
  473. to activate your product.
  474. * Phone: When you activate by phone, information on the screen
  475. guides you through a few simple steps. When you choose the
  476. country or region where you are located, a phone number (toll-free,
  477. wherever possible) appears on your screen. When you call the
  478. number, a customer service representative asks for the
  479. Installation ID that is displayed on your screen. The customer
  480. service representative enters that number into a secure
  481. database, confirms that the number represents a legally
  482. installed product, and provides a confirmation ID to you. Then,
  483. you type the confirmation ID into the spaces provided on the
  484. screen, and activation is complete.
  485. Reactivation (rarely needed)
  486. ----------------------------
  487. If you overhaul your computer by replacing a substantial number of
  488. hardware components (not just a few), the operating system might view
  489. your hardware as a completely different computer, not the one on which
  490. you activated. In this situation, you can call the telephone number
  491. displayed on the telephone activation screen, and, through a quick,
  492. simple process, you can reactivate your product.
  493. ---------------------------------------------------------
  494. 6.1 Product Activation Compared to Product Registration
  495. ---------------------------------------------------------
  496. Product activation is not the same as product registration. As
  497. discussed above, product activation is required, and it is completely
  498. anonymous. Product registration, in contrast, is completely optional,
  499. and it allows you to provide personal information, such as your e-mail
  500. address, if you choose. Registration entitles you to receive
  501. information about product updates and special offers directly from
  502. Microsoft. All registration information provided is stored securely,
  503. and no information is ever loaned or sold to other parties.