Microsoft KB Archive/268123

= Windows 2000 Server Training Kit Comments and Corrections =

Article ID: 268123

Article Last Modified on 3/1/2007

-

APPLIES TO


 * MSPRESS MCSE Training Kit, Microsoft Windows 2000 Server ISBN 1-57231-903-8

-



This article was previously published under Q268123



SUMMARY
This article contains comments, corrections, and information about known errors relating to the Microsoft Press book Microsoft Windows 2000 Server MCSE Training Kit, ISBN 1-57231-903-8.

The following topics are covered:


 * Pages xliii & 43: Minimum Memory Requirement Is 128 MB
 * Page 7: Windows 2000 Does Not Support RISC-Based Computers
 * Page 17: Incorrect Wording
 * Page 31: Incorrect Snap-in Name
 * Page 42: Incorrect Minimum Requirement For Free Space
 * Page 42: Incorrect Number Of Floppy Disks
 * Pages 45 & 910: Incorrect Minimum Boot Partition Size
 * Page 45: Remove Reference To 7.8GB Partition Limit
 * Page 48: &quot;Boot Partition&quot; Should Be &quot;System Partition&quot;
 * Page 48: Incorrect Reference To FAT File System
 * Page 49: Windows NT Does Not Recognize FAT32
 * Page 77: Error In &quot;Important&quot; Section
 * Page 116: Incorrect Syntax For ProductID
 * Page 117: Incorrect Step 2
 * Page 117: Change &quot;Unattend.txt&quot; To &quot;Unattend.bat&quot;
 * Page 117: Unable To Connect To Server01
 * Page 122: Incorrect Information About RIS
 * Page 122: Incorrect Information About Clean Installation With SMS
 * Page 124: Win32.exe Should Be Winnt32.exe
 * Page 129: Sysprep.exe And Sysprep.inf Misspelled
 * Page 130: Error Regarding Non-null Password In [GUIUnattended] Section
 * Page 154: Incorrect Information About Dynamic Disk Limitations
 * Page 164: Delete &quot;Server Operators Group&quot;
 * Page 164: Correction To Exercise 1
 * Page 169: DiskSpace Should Be DriveSpace
 * Page 182: Incorrect Information About CDFS
 * Page 184: Format.exe Should Be Format.com
 * Page 190: Inaccurate Information About NTFS 5.0 Accessibility
 * Page 203: Incorrect Permissions Listed
 * Page 204: &quot;Allow Inheritable Permissions From Parent To Propagate To This Object&quot; Is Selected By Default
 * Page 206: Incorrect Description About Inheritance
 * Page 208: Add Is Not A Windows 2000 NTFS Permission
 * Page 210: Incorrect Information About Default Inheritance
 * Page 215: Can Should Be Cannot
 * Page 217: Incorrect Information About Stand-Alone Dfs Replica
 * Page 244: Distinguished Name Format Is Incorrect
 * Page 245: Users OU cannot have sub-OUs
 * Page 261: Typographical Error
 * Page 278: Step 26 Is Incorrect
 * Page 282: Steps 4 And 5 Are Incorrect
 * Page 284: Domain Control Should Be Domain Controller
 * Pages 302 & 919: Ntdis.dit Should Be Ntds.dit
 * Page 321: Correction To Runas Command
 * Page 326: Incorrect New User Creation Requirement
 * Page 344: Incorrect Information About Resetting Passwords
 * Page 356: Error In Group Membership Table
 * Page 356: Incorrect Information About Universal Group Availability In Mixed-Mode
 * Page 358: Incorrect Information About Universal Group In Mixed Mode
 * Page 366: Incorrect Information About Enterprise Admins Membership
 * Page 367: Change &quot;Global Group&quot; To &quot;Domain Local Group&quot;
 * Page 369: Incorrect Reference To Windows 2000 Workstation
 * Page 386: MMC Console Should Be Saved As .msc File
 * Page 395: Applications Can Be Published Only To Users
 * Page 438: Incorrect Steps For Enabling Printer Pool
 * Page 461: Grammar Error In NWLink Section
 * Page 499: Incorrect DHCP Backup Folder Path
 * Page 568: &quot;ASDL&quot; Should Be &quot;ADSL&quot;
 * Page 576: Incorrect Information About Callback Number Length
 * Page 671: LSA Stands For &quot;Local Security Authority&quot;
 * Page 682: Then Should Be When
 * Pages 708 & 956: Slipstreaming Switch For Update.exe Is Incorrect
 * Page 718: Incorrect Location For Accessing Send Console Message Dialog Box
 * Page 718: Incremental Should Be Differential
 * Page 743: Incorrect Description About Entering Startup Menu
 * Page 819: Incorrect Question
 * Page 893: Incorrect Information About MetaFrame Upgrade
 * Page 903: Disk Should Be Data
 * Page 912: Incorrect Folder Name
 * Page 1010: Dfs Should Stand For Distributed File System



Pages xliii & 43: Minimum Memory Requirement Is 128 MB
The minimum memory requirement for Windows 2000 Server is 128 MB.

On page xliii, under Hardware Requirements, change:

&quot;64 MB of RAM&quot;

To:

&quot;128 MB of RAM&quot;

In the table on page 43, change:

&quot;64 MB for networking with one to five client computers; 128 MB minimum is recommended for most network environments.&quot;

To:

&quot;128 MB of RAM&quot;

Page 7: Windows 2000 Does Not Support RISC-Based Computers
On page 7, the first sentence under Windows 2000 Architectural Overview, indicates that Windows 2000 will run on RISC based computers. However, it will not.

Change:

&quot;Windows 2000 is a portable operating system designed to run on Complex Instruction Set Computing (CISC)-based and Reduced Instruction Set Computing (RISC)-based computers.&quot;

To:

&quot;Windows 2000 is a portable operating system designed to run on Complex Instruction Set Computing (CISC)-based computers.&quot;

Page 17: Incorrect Wording
On page 17, in the first line,

Change:

&quot;Miniport drivers are already implemented in Windows 2000...&quot;

To:

&quot;Miniport drivers are already implemented in Windows NT...&quot;

Page 31: Incorrect Snap-in Name
On page 31, in the Note section,

Change:

&quot;...in the Site Manager snap-in&quot;

To:

&quot;...in the Active Directory Sites And Services snap-in&quot;

Page 42: Incorrect Minimum Requirement For Free Space
In the table on page 42, the minimum free hard disk space should be 1 GB.

Change:

&quot;...on a partition with at least 671 MB of free space (2 GB is recommended).&quot;

To:

&quot;...on a partition with at least 1 GB of hard disk free space (2 GB is recommended).&quot;

Page 42: Incorrect Number Of Floppy Disks
On page 42, in the last bulleted item, change:

&quot;Format three 3.5-inch 1.44 MB floppy disks&quot;

To:

&quot;Format four 3.5-inch 1.44 MB floppy disks&quot;

Page 45: Remove Reference To 7.8 GB Partition Limit
The Note section on page 45 refers to a 7.8 GB maximum partition size. The 7.8 GB limit only applies to Windows NT. Windows 2000 does not have this limit. Please see the following articles for more information:

224526 Windows NT 4.0 Supports Maximum of 7.8-GB System Partition

240672 Setup Does Not Check for INT-13 Extensions Before Creating System Partition

Pages 45 & 910: Incorrect Minimum Boot Partition Size
Lines 2 and 30 on page 45, and question 5 on page 910, list 671 MB as the minimum boot partition size for installing Windows 2000 server. This is incorrect. The minimum boot partition size is 1 GB.

Page 48: &quot;Boot Partition&quot; Should Be &quot;System Partition&quot;
On page 48, there are three places where &quot;boot partition&quot; should be referred to as &quot;system partition&quot;.

In the first paragraph under File System Considerations, change:

&quot;Use the following guidelines and the table below to help you decide which file system format to use for your boot partition.&quot;

To:

&quot;Use the following guidelines and the table below to help you decide which file system format to use for your system partition.&quot;

In the fourth bulleted item, change:

&quot;You should choose the FAT option if your boot partition is smaller than 2 GB...&quot;

To:

&quot;You should choose the FAT option if your system partition is smaller than 2 GB...&quot;

In the fifth bulleted item, change:

&quot;...you have a boot partition larger than 2 GB.&quot;

To:

&quot;...you have a system partition larger than 2 GB.&quot;

Page 48: Incorrect Reference To FAT File System
On page 48, in the fifth bulleted item, change:

&quot;You should choose the FAT option if you are dual-booting with the OSR2 release of Windows 95, Windows 98, or Windows NT and...&quot;

To:

&quot;You should choose the FAT32 option if you are dual-booting with the OSR2 release of Windows 95, Windows 98, and...&quot;

Page 49: Windows NT Does Not Recognize FAT32
In the table on page 49, Windows NT is incorrectly listed as compatible with the FAT32 file system. Change:

Page 77: Error In &quot;Important&quot; Section
On page 77, in the &quot;Important&quot; section, change:

&quot;and if you disable this feature in the BIOS,&quot;

To:

&quot;and if you enable this feature in the BIOS,&quot;

Page 116: Incorrect Syntax For ProductID
On page 116, in step 12,

Change:

&quot;ProductID+&quot;

To:

&quot;ProductID = &quot;your product ID&quot;

Page 117: Change &quot;Unattend.txt&quot; To &quot;Unattend.bat&quot;
On page 117, in the &quot;Caution&quot; section in Step 2,

Change:

&quot;Unattend.txt&quot;

To

&quot;Unattend.bat&quot;

Page 117: Incorrect Step 2
On page 117, in step 2,

Change:

&quot;Open a command prompt and type cdh:&quot;

To:

&quot;Open a command prompt, type h: and press Enter.&quot;

Page 117: Unable To Connect To Server01
Step 1 on page 117 asks you to connect to Server01 from the second computer. You may not be able to connect to Server01 if there is not a DHCP server available on the network.

Solution:

If the second computer is running Windows 98, configure it to acquire an IP address from a DHCP server.

Note: The two computers can communicate with each other this way. This is made possible by a feature called Automatic Private IP Addressing (APIPA) employed by Windows 98 and Windows 2000. With this feature, a Windows 98/2000 computer can assign itself an IP address in the event that a DHCP server is not available or does not exist on the network. APIPA-enabled computers can only communicate within the assigned subnet. The APIPA-assigned IP address is a class B address in the range of 169.254.x.x.

If the second computer is running an operating system other than Windows 98, please complete the following steps:


 * 1) On Server01, run &quot;ipconfig&quot; at the command prompt to determine what the APIPA-assigned IP address is for Server01.
 * 2) On the second computer, manually specify an IP address in the range of 169.254.x.x other than the one assigned to Server01. Addresses 169.254.0.0 and 169.254.255.255 are also invalid. Set the subnet mask to 255.255.0.0

Page 122: Incorrect Information About RIS
On page 122, the fifth bulleted item lists &quot;Remote Installation Service (RIS)&quot; as an automated installation method for Windows 2000 Server. This is incorrect. Remote Installation Service is an automated installation method for Windows 2000 Professional only.

Page 122: Incorrect Information About Clean Installation With SMS
The table on page 122 indicates that a clean installation of Windows 2000 can be performed by SMS. This is incorrect. SMS can be used only for installations to computers that contain a previously installed operating system and are running the SMS client agent.

In the &quot;Clean Installation&quot; column for SMS,

Change:

&quot;Yes&quot;

To:

&quot;No&quot;

Page 124: Win32.exe Should Be Winnt32.exe
On page 124, in the first paragraph under Figure 3.3, it incorrectly lists the setup program name as &quot;Win32.exe&quot;.

Change:

&quot;...when running the Win32.exe Setup program&quot;

To:

&quot;...when running the Winnt32.exe Setup program&quot;

Page 129: Sysprep.exe And Sysprep.inf Misspelled
On page 129, in paragraphs two and three, file names &quot;Sysprep.exe&quot; and &quot;Sysprep.inf&quot; are misspelled.

Change:

&quot;Sysrep.exe&quot; and &quot;Sysrep.inf&quot;

To:

&quot;Sysprep.exe&quot; and &quot;Sysprep.inf&quot;

Page 130: Error Regarding Non-null Password In [GUIUnattended] Section
The [GuiUnattended] section on page 130 contains an error concerning non-null passwords. Change:

&quot;Any password supplied here will take effect only if the original source for the image (master computer) specified a non-null password.&quot;

To:

&quot;Any password supplied here will take effect only if the original source for the image (master computer) specified a null password.&quot;

Page 154: Incorrect Information About Dynamic Disk Limitations
On page 154, remove the following statement under the &quot;Dynamic Disk and Dynamic Volume Limitations&quot; section:

&quot;Dynamic disks that are less fault tolerant than the simple volume, extended simple volume, spanned volume, or striped volume cannot contain the boot or system partition. This feature is built into Windows 2000 to provide a baseline of fault tolerance for partitions containing operating system files.&quot;

You can upgrade a basic disk containing the system or boot partition to a dynamic disk. For further information on converting a basic disk to a dynamic disk, please refer to the Disk Management Help in Windows 2000.

Page 164: Delete &quot;Server Operators Group&quot;
On page 164, in the first sentence under &quot;Managing Disks on a Remote Computer&quot;, delete Server Operators group.

Change:

&quot;As a member of the Administrators or Server Operators group, you can manage disks...&quot;

To:

&quot;As a member of the Administrators group, you can manage disks...&quot;

Page 164: Correction To Exercise 1
On page 164,

Change:

&quot;Exercise 1: Configuring a Simple Disk and Converting It to a Dynamic Disk&quot;

To:

&quot;Exercise 1: Configuring a Simple Disk&quot;

Page 169: DiskSpace Should Be DriveSpace
On page 169, in the last paragraph,

Change:

&quot;MS-DOS 6.22 DiskSpace&quot;

To:

&quot;MS-DOS 6.22 DriveSpace&quot;

Page 182: Incorrect Information About CDFS
On page 182, under &quot;CD-ROM File System&quot;, it states that in Windows 2000, CDFS does not support lowercase filenames. This is incorrect. This limitation applies to Windows NT 3.51 only.

Page 184: Format.exe Should Be Format.com
On page 184, in the last paragraph,

Change:

&quot;If the Format.exe program is used to ...&quot;

To:

&quot;If the Format.com program is used to ...&quot;

Page 190: Inaccurate Information About NTFS 5.0 Accessibility
On page 190, the first paragraph needs clarification to include Service Pack specifications.

Change:

&quot;Windows NT 4.0 systems are not able to mount NTFS 5.0 volumes.&quot;

To:

&quot;Windows NT 4.0 systems (pre-SP4) are not able to mount NTFS 5.0 volumes.&quot;

Page 203: Incorrect Permissions Listed
On page 203, in the sixth bulleted item, change:

&quot;When assigning permission to public data folders, assign Modify and Read and Execute to the Users group, and Full Control to Creator Owner.&quot;

To:

&quot;When assigning permission to public data folders, assign Read and Write to the Users group, and Full Control to Creator Owner.&quot;

Page 204: &quot;Allow Inheritable Permissions From Parent To Propagate To This Object&quot; Is Selected By Default
On page 204, in the Description field for &quot;Allow Inheritable Permissions From Parent To Propagate To This Object&quot;, change: &quot;By default, this option is not selected for folders, which means subfolders do not inherit permissions assigned to their parent folder.&quot;

To:

&quot;By default, this option is selected for folders, which means subfolders inherit permissions assigned to their parent folder.&quot;

Page 206: Incorrect Description About Inheritance
On page 206, in the chart's Description field for &quot;Apply These Permissions To Objects And/Or Containers Within This Container Only&quot;,

Change:

&quot;Click to clear this check box to prevent permissions inheritance.

Select this check box to propagate the modified individual NTFS permissions down the folder hierarchy.&quot;

To:

&quot;Select this check box to prevent permissions inheritance.

Click to clear this check box to propagate the modified individual NTFS permissions down the folder hierarchy.&quot;

Page 208: Add Is Not A Windows 2000 NTFS Permission
On page 208 in the &quot;Copying Files and Folders&quot; section, change:

&quot;To copy files and folders within or between NTFS volumes, a user must have been granted Add permission for the destination folder.&quot;

To:

&quot;To copy files and folders within or between NTFS volumes, a user must have been granted Create Files/Write Data and Create Folders/Append Data permissions for the destination folder.&quot;

Also, under the &quot;Moving Files and Folders&quot; section, change:

&quot;To move files and folders between NTFS partitions requires the Add permission for the destination...&quot;

To:

&quot;To move files and folders between NTFS partitions requires the Create Files/Write Data and Create Folders/Append Data permission for the destination...&quot;

Page 210: Incorrect Information About Default Inheritance
On page 210, in line 10, change:

&quot;By default, permissions assigned to the partition and parent folder are not inherited and do not propagate to...&quot;

To:

&quot;By default, permissions assigned to the partition and parent folder are inherited and propagate to...&quot;

Page 215: Can Should Be Cannot
On page 215, in the table, in the &quot;Memory overhead&quot; row,

Change:

&quot;Without this service installed, Windows 9x clients can access...&quot;

To:

&quot;Without this service installed, Windows 9x clients cannot access...&quot;

Page 217: Incorrect Information About Stand-Alone Dfs Replica
On page 217, in the last bulleted item,

Change:

&quot;You can create a replica from a stand-alone Dfs root;&quot;

To:

&quot;You can create a replica from a stand-alone Dfs link;&quot;

Page 244: Distinguished Name Format Is Incorrect
On page 244, the distinguished name example given is in an incorrect format.

Change:

&quot;DC=COM/DC=Microsoft/CN=Users/CN=James Smith&quot;

To:

&quot;CN=James, Smith,CN=Users,DC=Microsoft,DC=Com&quot;

Page 245: Users OU cannot have sub-OUs
On page 245, in paragraph two under &quot;Relative Distinguished Name&quot;, change:

&quot;For example, if the Users OU contains a James Smith user account, you could not add another James Smith user to it. However, if the Users OU contains two smaller OUs..&quot;

To:

&quot;For example, if an OU contains a James Smith user account, you could not add another James Smith user to it. However, if the OU contains two smaller OUs...&quot;

Page 261: Typographical Error
On page 261 under &quot;First-Layer Domains&quot;, change:

&quot;Additionally, this will help minimize direct service replication,&quot;

To:

&quot;Additionally, this will help minimize directory service replication,&quot;

Page 278: Step 26 Is Incorrect
On page 278, change step 26 from:

&quot;Open Control Panel on Server02&quot;

To:

&quot;Select Network Identification from the Advanced menu of the Network And Dial-Up Connections window.&quot;

Page 282: Steps 4 And 5 Are Incorrect
On page 282, replace steps 4, 5, 6, and 7 with the following:

4. Select the Create A New Share radio button.

5. In the Path To Share text box, type c:\publicrepl.

6. In the Share Name text box, type pubrepl.

7. Click Finish.

The distributed file system message box appears stating that \\Server02\c$\publicrepl does not exist.

8. Click Yes to create the folder.

Page 284: Domain Control Should Be Domain Controller
On page 284, under Lesson Summary, in the third line,

Change:

&quot;...to add a domain control...&quot;

To:

&quot;...to add a domain controller...&quot;

Pages 302 And 919: Ntdis.dit Should Be Ntds.dit
On pages 302 and 919, in question 1, the file name Ntds.dit is misspelled as Ntdis.dit.

Change:

&quot;Ntdis.dit&quot;

To:

&quot;Ntds.dit&quot;

Page 321: Correction To Runas Command
There is an error on page 321 in line 3.

Change:

&quot;runas user&quot;

To:

&quot;runas /user&quot;

Page 326: Incorrect New User Creation Requirement
In the table on page 326, in the Description field for First Name and Last Name,

Change:

&quot;This or Last Name is required.

This or First Name is required.&quot;

To:

&quot;This, Initials, or Last Name is required.

This, Initials, or First Name is required.&quot;

Page 344: Incorrect Information About Resetting Passwords
On page 344, under &quot;Resetting Passwords&quot;,

Change:

&quot;If a user's password expires before she or he can change it, or if a user forgets her or his password, you need to reset the password.&quot;

To:

&quot;If a user forgets her or his password, you need to reset the password.&quot;

Page 356: Error In Group Membership Table
There is an error in the &quot;Native-mode scope&quot; column of the Group Membership table. It's missing the words, &quot;as well as other domain&quot;. Change to:

Page 356: Incorrect Information About Universal Group Availability In Mixed-Mode
On page 356, in the table under &quot;Group Membership&quot;, in the &quot;In Mixed-mode scope can contain&quot; - &quot;Universal&quot; cell,

Change:

&quot;Not available in Mixed Mode&quot;

To:

&quot;Not available in Mixed Mode, unless the Group Type is Distribution&quot;

Page 358: Incorrect Information About Universal Group In Mixed Mode
On page 358, in the first bulleted item, change:

&quot;Universal groups do not exist in Mixed mode.&quot;

To:

&quot;Universal security groups do not exist in Mixed mode.&quot;

Page 366: Incorrect Information About Enterprise Admins Membership
In the table on page 366, in the &quot;Description&quot; field of &quot;Enterprise Admins&quot;,

Change:

&quot;By default, the Administrators built-in local group for each domain is a member of the Enterprise Admins global group.&quot;

To:

&quot;By default, the Enterprise Admins global group is a member of the Administrators built-in local group.&quot;

Page 367, Change &quot;Global Group&quot; To &quot;Domain Local Group&quot;
On page 367, in the table, change the first column's heading from &quot;Global group&quot; to &quot;Domain local group&quot;

Page 369: Incorrect Reference To Windows 2000 Workstation
On page 369, line 7, there is a reference to &quot;Windows 2000 Workstation&quot;. This should read &quot;Windows 2000 Professional&quot;.

Page 386: MMC Console Should Be Saved As .msc File
On page 386, line 13, change:

&quot;save the MMC console as an .mmc file.&quot;

To:

&quot;save the MMC console as an .msc file.&quot;

Page 395: Applications Can Be Published Only To Users
The table on page 395 erroneously states that applications can be published to computers. The last row of the table should be removed:

&quot;Computer Configuration - The Add/Remove Programs wizard for all computers in the site, domain, or OU&quot;

Page 438: Incorrect Steps For Enabling Printer Pool
On page 438, in the second paragraph,

Change:

&quot;Once there, select or create the ports containing print devices that will be part of the pool and then check the Enable Printer Pooling check box at the bottom of the page.&quot;

To:

&quot;Once there, check the Enable Printer Pooling check box at the bottom of the page, then select or create the ports containing print devices that will be part of the pool.&quot;

Page 461: Grammar Error In NWLink Section
On page 461, the last sentence currently suggests that CSNW and GSNW are NetWare servers. This isn't the case. The sentence should read:

&quot;To access files or printers on a NetWare server, services such as the Client Service for NetWare (CSNW) in Windows 2000 Professional or the Gateway Service for NetWare (GSNW) in Windows 2000 Server must be used.&quot;

Page 499: Incorrect DHCP Backup Folder Path
On page 499, in the last paragraph, change:

&quot;You can restore the DHCP database file manually by copying the contents of the %systemroot%\System32\DHCP\Backup\Jet folder to the...&quot;

To:

&quot;You can restore the DHCP database file manually by copying the contents of the %systemroot%\System32\DHCP\Backup\Jet\new folder to the...&quot;

Page 568: &quot;ASDL&quot; Should Be &quot;ADSL&quot;
In Figure 10.8 on page 568, there is an incorrect reference to ASDL. Change:

&quot;ASDL&quot;

To:

&quot;ADSL&quot;

Page 576: Incorrect Information About Callback Number Length
On page 576, the second paragraph contains incorrect information about the allowed length of the callback number in different server modes.

Change:

&quot;If a user account is in a Windows 2000 native-mode domain, the callback number can be up to 128 characters. If a user account is on a RAS server running Windows 2000 as a stand-alone server, in a Windows NT 4.0 domain, or in a Windows 2000 mixed-mode domain, the callback number is from 24 through 48 characters, due to the compressed format for storing callback numbers.&quot;

To:

&quot;If the Windows 2000 Routing and Remote Access service server is a stand-alone server or a member of a Windows 2000 native domain, the callback number can be of unlimited size. If a Windows 2000 Routing and Remote Access service server is a member of a Windows NT 4.0 domain or a Windows 2000 mixed domain, the callback number can only be 128 characters long.&quot;

Page 671: LSA Stands For &quot;Local Security Authority&quot;
On page 671, in the third line,

Change:

&quot;it forwards the request to the Local Service Authority (LSA).&quot;

To:

&quot;it forwards the request to the Local Security Authority (LSA).&quot;

Page 682: Then Should Be When
On page 682, in the third bulleted item under &quot;Overview of Windows 2000 Auditing&quot;, change:

&quot;The success or failure of the event and then the event occurred&quot;

To:

&quot;The success or failure of the event and when the event occurred&quot;

Pages 708 & 956: Slipstreaming Switch For Update.exe Is Incorrect
On pages 708 & 956 under &quot;Service Pack Slipstreaming&quot; the switch to apply a new service pack to distribution files is incorrect.

Change:

&quot;run Update.exe with the /slip switch.&quot;

To:

&quot;run Update.exe with the -s:distribution_folder switch, where distribution_folder is the name of the folder that contains the Windows 2000 installation files.&quot;

Page 718: Incorrect Location For Accessing Send Console Message Dialog Box
On page 718, in the last paragraph,

Change:

&quot;You can use e-mail or the Send Console Message dialog box in the File Service Management snap-in to send administrative messages to users. You can access the File Service Management snap-in through the Computer Management snap-in.&quot;

To:

&quot;You can use e-mail or the Send Console Message dialog box in the Compute Management snap-in to send administrative messages to users. You can access the Send Console Message dialog box by right-clicking Computer Management in the Computer Management snap-in and select All Tasks.&quot;

Page 718: Incremental Should Be Differential
On page 718, in the third bullet,

Change:

&quot;These backups use the same strategy as the normal and incremental backups&quot;

To:

&quot;These backups use the same strategy as the normal and differential backups&quot;

Page 743: Incorrect Description About Entering Startup Menu
On page 743, in the fifth paragraph, the description on how to enter the Windows 2000 Startup Menu applies only to a computer with multiple operating systems.

Change:

&quot;Press F8 when you see the message Please Select The Operating System To Start.&quot;

To:

&quot;Press F8 when you see the message &quot;Starting Windows 2000...&quot;.&quot;

Page 819: Incorrect Question
On page 819, in question 2,

Change:

&quot;How can you increase disk access time for the server?&quot;

To:

&quot;How can you decrease disk access time for the server?&quot;

Page 893: Incorrect Information About MetaFrame Upgrade
On page 893, under &quot;Terminal Server 4.0 with MetaFrame&quot;, there is an error in reference to upgrading Terminal Server. Change:

&quot;Upgrading from Terminal Services 4.0 with MetaFrame is similar to upgrading from Terminal Server 4.0, but first you need to upgrade to the MetaFrame version for Windows 2000. After MetaFrame is upgraded, you can follow the same procedure for upgrading from Terminal Server 4.0 without MetaFrame.&quot;

To:

&quot;With MetaFrame for Terminal Server 4.0 installed, you must first install Windows 2000 with Terminal Services, then install the latest version of MetaFrame for Windows 2000.&quot;

Page 903: Disk Should Be Data
On page 903, in step 24,

Change:

&quot;Enable Disk Compression&quot;

To:

&quot;Enable Data Compression&quot;

Page 912: Incorrect Folder Name
On page 912, in the fourth line from the bottom,

Change:

&quot;$OEM\$1\Sysprep&quot;

To:

&quot;$OEM$\$1\Sysprep&quot;

Page 1010: Dfs Should Stand For Distributed File System
On page 1010,

Change:

&quot;Dfs (domain file system)&quot;

To:

&quot;Dfs (distributed file system)&quot;

Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.

Additional query words: TKBOOK WIN2000 1-57231-903-8 0-7356-1386-9

Keywords: kbdocerr kbdocfix kbinfo KB268123

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.