MCSE: The Core Exams in a Nutshell by Michael Moncur Unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. This page was updated January 21, 2000. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification UNCONFIRMED errors and comments from readers: (3) Line 20 from top: "Exam 70-026: System Administration for Microsoft SQL Server 6.5 or 70-029:" Should be: "Exam 70-026: System Administration for Microsoft SQL Server 6.5 or 70-028:" (20) On the Exam: "Suggested Exercises" should read "Highlighter's Index" (21) In the fifth paragraph, first sentence, (under the heading "The OSI Reference Model") you refer to the ISO as the: "International Standards Organization" ISO is not an acronym. It should read: "International Organization for Standardization" [23] In the first paragraph under "Network Layer" heading, the paragraph states: "The network layer adds additional headers to the frames from the data link layer, forming packets". If you are looking at the OSI model from Application down to the Physical layer, wouldn't additional headers be added in that direction. i.e As you work down the model, each layer adds it's own headers? But if you are working from the Physical layer up to the Application layer (in this case Data link to Network layer) shouldn't the headers be removed in this direction as the packet passes up the model? Could you please clarify this for me as I'm using the book for revision for the Network+ Exam which I hope to take shortly. {25} Table 1-1, last 2 rows: 802.11 | Wireless Networking (Draft) 802.12 | High-speed LANs should be 802.11 | Wireless Networking 802.12 | Demand Priority Access {39} My question is in regard to the following statement found in the second paragraph in the "Routers" section. It now reads: "Unlike bridges, routers can connect networks using different architectures (such as Ethernet and Token Ring)." This statement certainly seems to imply that a bridge cannot connect networks using different architectures, such as Ethernet and Token Ring. Yet in the Microsoft text I am also using (ISBN 1-57231-527-X), on page 556 it clearly states that "Bridges can be used to: Link unlike network segments such as Ethernet and Token Ring, and forward packets between them." I have searched the errata sites for both books but do not see this item mentioned and wondered if you could clear up the confusion. (66) Question 2 now reads: "Which of the following is not a disadvantage of peer-to-peer networks? This is a nasty, nasty play on words on your part, a double negative indeed! {66} Question # 2 now reads:. "2. Which of the following is not a disadvantage of peer-to-peer networks? a. Lack of centralized administration. b. Low security. c. High cost." The answer given on page 75 states: "2. C. While peer-to-peer networks do have a lack of central administration and low security, their low cost is a benefit." This answer would be right if the question had said LOW cost, however it states HIGH cost. I believe this should be corrected. {70} Question 27: the solution given may not meet the required result if hub ports are used up by interconnecting hubs. The question may need to be rephrased. (from a different reader:) Keep in mind that a lot of those X-port hubs have an uplink port not counted in the X. But even so, they don't have two that you would need. {72} Question 38: Answer D "Frame Relay is also correct as it uses packet switching as defined on P52. (73) Question 39 is questionable at best. The book states that the solution should be the least expensive solution, for 1.5 Mbps, which is NOT the case (frame is cheaper). Also, it states that the "WAN should be upgradable to a higher bandwidth using the same type of equipment". Techically this is correct, if the same "type" of equipment is used you will most likely have to buy a new CSU/DSU. This question looks like frame is the correct choice, especailly considering both the "month charges, and equipment reuse" are stated in the book to be benifits of frame relay. This is a really borderline question. (73) In problem 40 the answer is b and c, but the question does not state to "Check all that apply." (82) In the "Token Ring" section, fourth line, now reads: "Hubs are called multistation access units (MSAUs)" I believe that multistation access units are called MAUs, and not MSAUs. I have seen this acronym given as both MAU and MSAU. I have even seen a hub called an SMAU. That seems confusing enough that we might want to add the other acronyms to the page. The real test of course is what the hub is called in Microsoft World. (83) Under DialUp Protocols it now reads: "SLIP (Single line internet protocol)" Should be: "SLIP (Serial line internet protocol)" {84} - In the section "T1-T4" the T4 transfer rate of "Mbps" is not displayed as it is for the others in this section. <101, 153> The text under "On the Exam" on page 101 now reads: The Task Manager utility, described in "Optimization and Troubleshooting" at the end of this chapter, allows you to change the priority of background processes; however, you cannot change the priority of an application without stopping and restarting it. Then on page 153 in the third paragraph, the second line reads: Although you can change the priority of a process as described below, this utility does not allow you to change application priorities. CORRECTION: A running application *is* a process. If, for example, I run the Calculator Accessory, it will show up in the Task Manager list as CALC.EXE (in the process window). As such, I can right click it and change it's priority just like any other process--background or otherwise. {105} The final paragraph explains that servers in a domain can serve several roles. It goes on to list the possible roles as PDC, BDC, member servers, or standalone servers. However, member servers and standalone servers are one in the same, at least from the point of view of an NT installation. <106> The second bulleted item reads: VFAT (virutal FAT) is a modified implementation of the FAT system. The main differences are that it supports long file names and raises the maximum partition size limit to 4 GB. CORRECTION: Although VFAT does support long file names, it's maximum partition size is only 2 GB like FAT partitions. This is because a VFAT partition is simply a FAT partition that stores the long file names in some extra free space in the directory structure. ?106? Under File Systems, under NTFS, your book states that NTFS is supported only by Windows NT 4.0 and later, but isn't it supported in NT 3.51 also? <109> ORIGINAL: /F (WINNT only) When used with the /O or /OX option, copies the files to the boot disks without write verification. CORRECTION: /F (not /E) copies files to disks without verification <114> The second to last paragraph reads: rdisk: This entry is unused with scsi entries, and should be set to zero. CORRECTION: When used with a scsi entry, rdisk specifies the Logical Unit Number (LUN) of the boot device. Although it is usually zero, it does not have to be. REFERENCE: Microsoft Knowledge Base Article Q102873 (116-118 General Comment) ADDITION: When performing an unattended installation, one UNATTEND.TXT file is required for each hardware platform that is being installed. For example, If I am installing 50 identical desktops and 50 identical notebooks, I will need 2 UNATTEND.TXT files and 1 Uniqueness Database File (UDF). This would also be true if I was installing 100 identical computers for two different departments in a company, and so on. <137> The eighth paragraph reads: HKEY_DYN_DATA: This subtree stores dynamic hardware information ... CORRECTION: Although Windows 95 includes a HKEY_DYN_DATA key, Windows NT does not have such a root key. Instead, Windows NT uses HKEY_LOCAL_MACHINE\HARDWARE to store its dynamic hardware information. {137} In the section "Editing the Registry" it is stated that the registry has five main subtrees, however, six are then listed. ?139? General Comment: The book states that you cannot rename the user Guest. One reader who has NT4.0 workstation was able to rename the account. {147} In the first section it is explained how to modify permissions of a file or directory. However, the step of selecting properties is omitted. {170} Question 24: Win 95 can not be upgraded to NT 4.0 but can preserve settings if installed along side to a different directory or partition. Applications need then be reinstalled as they both use Sytem and program files dir. Question 25: Question offers the same choice of answers twice answer A and D both read the same, suggest changing answer D to begin with multi(0) instead of scsi(0) Question 25 now reads: b. multi(0)disk(1)rdisk(0)partition(1)\WINNT4="Windows NT" CORRECTION: b. multi(0)disk(0)rdisk(0)partition(1)\WINNT4="Windows NT" REFERENCE: Page 114 {170} Practice Test question 25: Answer b. should read multi(0)disk(0)rdisk(0)partition(1)\winnt4="Windows NT" Ref: MCSE The Electives in a Nutshell {172} Question 42: Answer A is also correct as the Guest account can not be deleted or renamed it is hard coded into NT, and can only be disabled. The Administrator account can not be disabled, locked out or deleted but can have its account name renamed to something other than Administrator. {191} - Table 3-1 is incorrectly titled "Windows NT Workstation Requirements" when these are actually the "Server Requirements". (196) - 2nd bullet under "Installation Methods": "This method can use files installation files from the CD-ROM, from a copy on a local disk, or a network share." This sentence should presumably read: "This method can use installation files from the CD-ROM, from a copy on a local disk, or a network share." {196} - In the section "Planning a Domain" there is a sentence that reads, "The servers in a domain are called domain controllers". However, not all servers are domain controllers. {206} Under the "Directory Replicator" heading, the first paragraph, first sentence reads: "The Directory Replicator service is built into Windows NT Server, but not included with NT Workstation." This is wrong. The Directory Replicator service is included in NT Workstation; however, it can only act as an importer and not an exporter of files. [213] The third paragraph under the "Browser Elections" heading suggests that if a domain master browser goes down, an election is held. This is incorrect. The domain master browser is always a PDC and if the PDC goes down, there is no domain master browser. When the domain master browser (PDC) is down, network browsing will only display resources available on the local subnet (network resources located on other subnets will not be displayed). To rectify this situation, either bring the PDC back online, or promote a BDC to a PDC. (217) General Comment: ADDITION: In The Real World: Restoring Windows NT over an exisiting installation requires some special attention. See the Microsoft Knowledge Base for details. {217} The last line reads: AT 12:00 "ntbackup BACKUP C:\ /t:normal" It should read: AT 12:00 "ntbackup BACKUP C:\ /t normal" {218} Line 23 reads: /t:type It should read: /t type {221} Under the heading, "Local and Global Groups," the first bulleted paragraph reads: "Local groups on non-domain controllers are specific to one computer, and can be granted rights for that computer only. Local groups on the PDC or BDC exists on all domain controllers in the domain, and can be granted rights for any resource in the domain." The first sentence is accurate. In the second sentence, however, local groups on a domain controller can only be granted rights for resources that exist on other domain controllers in the domain. From a member server or a workstation, the only domain accounts visible are users and global groups. (221) The last paragraph reads: Global groups are also visible to trusted domains (discussed in Part 4). It should read: Global groups are also visible to trusting domains (discussed in Part 4). REFERENCE: Page 258-265 (222) The third paragraph reads: Windows NT Server includes the same local groups as NT Workstation: Account Operators, Administrators, Backup Operators, Guests, Power Users, Replicators, Server Operators, and Users. CORRECTION: Windows NT Server includes the same local groups as NT Workstation: Account Operators, Administrators, Backup Operators, Guests, Power Users, Replicators, Users, and an additional Server Operators group. {224} Under the "System Policies" heading, the second bulleted paragraph, second sentence makes reference to the: "HKEY_LOCAL_COMPUTER" registry subtree. This should read: "HKEY_LOCAL_MACHINE" (225) The third paragraph reads: To use a system policy, use the Save option in the File menu to save the policy in the NETLOGON share of the PDC or BDC. CORRECTION: To use a system policy, use the Save option in the File menu to save the policy with the file name "NTconfig.pol" in the NETLOGON share of the PDC or BDC. (228) "On the Exam" box suggests Task Manager works remotely. This is not the case. {243} answer 12: "B. The BDC must authenticate with the PDC during the installation process. If the BDC is not available, installation cannot proceed." should be "B. The BDC must authenticate with the PDC during the installation process. If the *PDC* is not available, installation cannot proceed." {243} Question No 14: Which of the following computer types are able to authenticate users for logon? Select all that apply. a) PDC b) BDC c) Member Server d) Stand-Alone Server The answer is A and B, which is correct for a domain. ?But is a stand alone server a valid answer as this would have to validate users for local log on? (243) (16.) Suggests that it is possible the change the domain of a BDC without reinstalling. This is not the case. {260} - The simple trust and bidirectional trust figures are incorrect. In the simple trust figure, there isn't a trusted domain. In the bidirectional trust figure, there isn't an indication that there is a bidirectional trust using two opposing arrows. (272) Under the "Supporting AppleTalk Printing" heading, the text reads: Windows NT (Workstation or Server) computers with AppleTalk installed can print to AppleTalk printers without using SFM ... When you configure the AppleTalk printer in this fashion, it becomes inaccessible to the Macintosh network. To make it available, share the printer. This will also make it available to Windows clients. CORRECTION: If the AppleTalk printer is installed WITHOUT capturing the port, then it will remain accessible to Macintosh computers as well as any Windows NT computers that have AppleTalk and print directly to the printer. This is true regardless whether or not the AppleTalk printer is shared after being installed. However, if the printer port IS captured, then no other computer (Mac or NT) will be allowed to print directly to the printer--unless it is shared, in which case the printer has to be accessed through the server that captured the printer port. {285} - In the example for calculating time needed for synchronization (5000 * 3) in the second line incorrectly leads to 15000 * 3 in the third line. (285) In the fourth paragraph, under the heading "ChangeLogSize," the sentence now reads: "The change log stores changes made to the user database on the PDC that need to be synchronized to PDCs." Sentence should read: "The change log stores changes made to the user database on the PDC that need to be synchronized to BDCs." (Changed second "PDC" to "BDC") {285} In the Part 4, "NT Server in the Enterprise," the equation on time for domain synchronisation seems to be in error. <297, 301> Page 297: 46. You want to use Network Monitor to monitor traffic to and from a Windows NT Workstation computer, and capture the data on a Windows NT Server computer. Which service should be installed on the NT Workstation computer? Page 301: 46. C. Since the NT Workstation computer is being monitored but will not run Network Monitor, it requires the Network Monitor Agent service. CORRECTION: The question on page 297 is worded incorrectly. The NT Workstation (with Network Monitor Agent) is actually CAPTURING data. The NT Server (with Network Monitor) is simply VIEWING the data the NT Workstation captured and forwarded to the NT Server. In order for the NT Server to do the capturing for another computer, SMS is required with a promiscuous network interface card. {303} The paragraph under "Multiple Master Domain Model" in the Highlighter's Index appears contradictory.