MCSE in a Nutshell: The Windows 2000 Exams by Michael Moncur & Paul Murphy 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 last updated November 07, 2002. 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: {5} 2nd paragraph under "Preparing for Exams".; You state "Microsoft's documentation, such as the Windows NT Resource Kits, the online books, and the help files included with various utilities, may be helpful." Surely, this is meant to say "... the Windows 2000 Resource Kits..." since this is what the book is about? {5} 3rd paragraph under "Preparing for Exams".; The last sentence states "You should have access to a network with a minimum of two Windows NT computers to experiment with..." I believe this is supposed to say "...Windows 2000 computers..." since Windows 2000 is the subject of the book. {21} 3rd paragraph: FAT32 doesnīt originate in Windows 98 but Windows 95B! [33] IN THE REAL WORLD; It is stated that "Systems running HPFS must be converted to NTFS before upgrading. The ACLCONV utility, available from microsoft, can perform this conversion. I have seen no evidence of ACLCONV having this benefit. And according to Q104097 on the Microsoft KB, CONVERT performs this function. Quote: "ACLCONV: Converts LAN Manager access control lists (ACLs) to Windows NT permissions on Windows NT file system (NTFS) files. CONVERT: Converts a partition from FAT or HPFS to NTFS." http://support.microsoft.com/default.aspx?scid=kb;EN-US;q104097 [34] top paragraph; According to the ResKit the /U parameter can only be used with winnt. For winnt32 you need to use /unattend. [52] Disk Quotas - last sentence in section; Disk quotas can only be assigned to user objects and not Group objects, as inorrectly implied by this sentence. [65, 94] NTFS Security table: The NTFS Permissions should be: Full Controll Modify Read & Execute List Folder Contents Read Write [72,130] p130, "safe mode", 3rd paragraph; For all I read in TechNet the rdisk command is no longer available. An ERD can ONLY be created via Ntbackup. [106] Installing service packs, 3rd paragraph: Shouldn't the text be: Update.exe (without the /slip parameter)??? The description on page 36 (Using Service Packs) is different. [139] Question 29; The Answers given by the book are A. Application Sharing B. Remote Sharing C. Remote Administration D. Application Tuning The books answers are A and C. The corect Answer to me is just C. There is no such thing as Application Ssharing Mode. There are 2 modes that may be selected when installing Terminal Server, they are Application Server Mode and Remote Administration Mode. Sharing is not a Mode. [140] Question 34; How can a Print device refer to more than one logical printer? A print device is the physical printer, it cannot refer to logical printers. Logical printers can refer to more than one print device. Your answers say that is a correct s tatement and that the only incorrect answer is D. {144} Answer to Q. 23; The answer should be (c) since the problem involves moving a compressed file to another volume. Files do not inherit the compression state of the destination folder when moving within a volume. [228] table 4-8; Range 172.16.0.0 is in the Class B range (not C as stated in the book), isnīt it? [229] 3rd paragraph in 'supernetting' section; The 3 class C addresses given in the example are 132.124.4.0, 132.24.5.0 and 132.24.6.0. Given that they have to be consecutive addresses to be supernetted, shouldn't the first address be 132.24.4.0? {229} Headline "Supernetting" 3rd paragraph; The 3 shown addresses are class b addresses. {246} The LMHOSTS File section, 1st paragraph; The first sentence states that "In enhanced B-node NetBIOS resolution, the LMHOSTS file is checked if a negative response is received from the WINS server." However, in the description of of Enhanced B-node on page 243, paragraph 5, it states that enhanced B-node 'is Windows NT's default if a WINS server is not used.' It then states that first broadcast, and then LMHOSTS is used for name resolution, with no further mention of WINS. It seems as though one of these descriptions is incorrect. [257] top; ms chapv2 and win 2k only completly untrue and very misleading...... see http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q189771& (303) "In the real world"; SMTP is a mail protocol; I think that the author means SNMP. [1] Part 5; located the text online as opposed to in print; The Active Directory system is all about managing data. How does it go from place to place and who has access to it? The division of data access does not always follow strict departmental lines. If the company is designed in such a way that billing and sales need access to customer financial records and customer service and technical support need access to customer product records, you can divide by function rather than department. Instead of having four separate OUs based on department, you may be better off with two OUs, based on the data they need to access. Don't forget that OUs are automatically arranged in a hierarchical structure with permissions inheritance. You can create top level OUs based on the data they need to access and lower level OUs by department. Then you can move an entire department in and out of data access OUs whenever the department's needs change. Because permissions would be automatically inherited from the top level data access OU to the lower level departmental OU, you wouldn't have to change permissions for employees on an individual basis. They would inherit permissions from their departmental OU, which in turn inherits permissions from the data access OU. The above information is utterly incorrect. OUs are not security principals, and are not used to grant access to resources. The only permissions that are inherited via the AD structures are the permissions on the AD objects themselves, *not* file system permissions or user rights. Those permissions are granted using security principals- users, computers and groups. Whoever wrote this seems to have a strong misunderstanding of Active Directory. AD != NDS.