Article ID: 303076 - View products that this article applies to.
This article was previously published under Q303076
This article has been archived. It is offered "as is" and will no longer be updated.
This article contains comments, corrections, and information about known errors relating to the Microsoft Press/McGraw Hill book Academic Learning Series Designing a Microsoft Windows 2000 Directory Services Infrastructure, ISBN 0-7356-1267-6/0-07-285070-1 .
The following topics are covered:
CD-ROM: Evaluation CD May Not Be BootableSome of the Windows 2000 Server Evaluation Edition CDs included with this book may not be bootable. In order to install Windows 2000 Server using the non-bootable Evaluation CD, you must create Windows 2000 Server Setup Boot Disks.
For instructions on how to create the Windows 2000 Server Setup Boot Disks, please refer to the ADVSRV3.TXTfile located on the Evaluation CD:
"To start Setup for a new installation by starting the computer from floppy disks
1. Locate both the Windows 2000 Setup floppy disks and the Windows 2000 CD-ROM.
2. With your computer turned off, insert the first Setup disk into drive A of your computer.
3. Turn on your computer.
4. Follow the Setup instructions.
You can create a set of floppy disks by using the Makeboot utility in the Bootdisk folder of the Windows 2000 Setup CD-ROM. You can create the Setup disks from a computer running any version of Windows or MS-DOS.
You will need four blank, formatted, 3.5-inch, 1.44-MB floppy disks. Label them Setup Disk One, Setup Disk Two, Setup Disk Three, and Setup Disk Four. To create Setup disks
1. Insert a blank, formatted, 3.5-inch, 1.44-MB disk into the floppy disk drive.
2. Insert the Windows 2000 CD-ROM into the CD-ROM drive.
3. Click Start, and then click Run.
4. In the Open box, type d:\bootdisk\makeboot a: (where d: is the drive letter assigned to your CD-ROM drive), and then click OK.
5. Follow the screen prompts."
Lab Manual, page iii: Incorrect Number of Core Elective ExamsOn page iii, in the third paragraph,
"The new certification program is composed of four core requirement exams and three core elective exams."
"The new certification program is composed of four core requirement exams and four core elective exams."
Page xxiv: Incorrect Hardware RequirementsOn page xxiv, under Hardware Requirements,
"32-bit 166MHz Pentium processor
64-MB memory for networking with one to five client computers; 128 MB minimum is recommended for most network environments"
"133 MHz or higher Pentium-compatible CPU
256 megabytes (MB) of RAM recommended minimum; 128 MB minimum supported"
Page 30: Incorrect Information About Host Name And Computer (NetBIOS) NameOn page 30, in the second Note section,
"The host name does not have to be the same as the computer name, NetBIOS, or any other naming protocol."
"The host name is always the same as the computer (NetBIOS) name. In Windows 2000, you cannot specify different host (Directory Naming Service, or DNS) and computer (NetBIOS) names."
Page 61: Incorrect Weighted TotalOn page 61, in Table 2.1, change:
Page 80: NT DNS Does Not Meet Active Directory DNS RequirementsOn page 80, in the paragraph above the Note section, in the last sentence, change:
"If you organization is currently running Windows NT 4 DNS, your DNS service is also compatible with Active Directory DNS requirements."
"If you organization is currently running Windows NT 4 DNS, your DNS service is not compatible with Active Directory DNS requirements."
Page 146: "Domains" Should Be "Trees"On page 146, in the first paragraph under "Implications of Using Multiple Trees",
"When determining whether to define multiple domains"
"When determining whether to define multiple trees"
Page 195: Correction To Point 3On page 195, in point 3, change:
"3. If the OU is allowed to set its own membership, place the administrator group inside the OU. If the OU is not allowed to set its own membership, place the administrator group outside the OU."
"3. If the administrator group is allowed to set its own membership, place the administrator group inside the OU. If the administrator group is not allowed to set its own membership, place it outside the OU."
Page 201: Publish Should Be AssignOn page 201, Change:
"..and another group policy to publish software on management workstations"
"..and another group policy to assign software on management workstations"
Page 202: Incorrect Caption In Figure 5.11On page 202, in Figure 5.11, change:
"OUs defined to hide objects"
"OUs defined to implement Group Policy"
Page 221: Incorrect Domain Local Group Membership In Figure 5.9On page 221, in Table 5.9, groups with both read-only access and full access needs to the Customer database and Tracking database (as defined in Table 5.8) are being incorrectly made members of the same domain local groups: "CustDatabase" and "TrackDatabase".
Only global groups that share the same access needs should be made members of the same domain local group to ensure proper access permission assignment. There should be separate domain local groups created for different access needs.
"CustDatabase - Security, domain local - Domestic Dispatchers, International Dispatchers, Managers, Delivery Representatives
TrackDatabase - Security, domain local - Distribution Trackers, Managers, Distribution Handlers"
"CustDatabase - Security, domain local - Domestic Dispatchers, International Dispatchers, Managers
CustDatabase2 - Security, domain local - Delivery Representatives
TrackDatabase - Security, domain local - Distribution Trackers, Managers
TrackDatabase2 - Security, domain local - Distribution Handlers"
Page 253: "Pull" Should Be "Push" For Intrasite Replication In Table 6.2On page 253, in Table 6.2, in the "Instrasite replication" - "Replication model" cell, "pull" should be "push".
"To reduce replication latency, replication partners notify each other when changes need to be replicated and then pull the information for processing."
"To reduce replication latency, replication partners notify each other when changes need to be replicated and then push the information for processing."
Page 306: Incorrect Child Domain Names In Figure 7.6On page 306, in Figure 7.6,
"london.microsoft.com, chicago.microsoft.com, redmond.microsoft.com"
"london.sales.microsoft.com, chicago.sales.microsoft.com, redmond.development.microsoft.com"
Page 346: Incorrect Subdomain Names In DiagramOn page 346, in the diagram, the subdomain names listed are incorrect.
Page 363: Incorrect Information About Schema Master And Domain Naming MasterOn page 363, the diagram lists multiple schema masters (SM) and domain naming masters (DN) in different domains. This is incorrect. At any time, there can be only one schema master and one domain naming master in the forest.
In the diagram, please remove all the SMs and DNs, except for the SM and DN at hq.corp.f-1000times.com.
And in the last bulleted item on the same page:
"... the forest-wide roles were assigned to DC1s."
"... the forest-wide roles were assigned to DC1 at hq.corp.f-1000times.com."
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.
Contact us for more help
Connect with Answer Desk for expert help.