MCSE Core Required Exams in a Nutshell, Third Edition
by  William R. Stanek

The 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.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated April 22, 2008.


UNCONFIRMED  errors and comments from readers: 


{149}  Under 'Changing group scope' header;
The second bullet point under the 'Changing group scope' header states 
that a global group can be changed to a universal group providing no 
member has global scope. This is incorrect. A universal group can contain 
global groups, so it is possible to change a global group to a universal 
group when one of the members is a global group.


{171} Question 23;
Answer C is listed as correct but does not meet the criteria listed in 
the answer. There is no uppercase letter.

{171} Question 23;
According to Microsoft's information "http://www.microsoft.com/technet/prodtechnol/windowsserver2003/
technologies/directory/activedirectory/stepbystep/strngpw.mspx", answers A, B & C are correct.

They both meet the following complexity requirement:
(1) At least 6 characters long
(2) Contains characters from at least three of five categories
- English upper case characters
- English lower case characters
- Base 10 digits
- Non-alphanumeric
- Unicode characters

``````````````````````````````````````````````
C:\Documents and Settings\midguy>dsadd user"cn=test 
user,ou=users,ou=accounts,ou=boston,dc=bigfirm,dc=local" -fn test -ln user -display "test user" -samid 
testuser -pwd Ilove2gotoSchool
dsadd succeeded:cn=test user,ou=users,ou=accounts,ou=boston,dc=bigfirm,dc=local

C:\Documents and Settings\midguy>dsadd user "cn=test 
user01,ou=users,ou=accounts,ou=boston,dc=bigfirm,dc=local" -fn test -ln user01 -display "test user01" -
samid testuser01 -upn testuser01@bigfirm.local -pwd gottorunfaster
dsadd failed:cn=test user01,ou=users,ou=accounts,ou=boston,dc=bigfirm,dc=local:The password does not meet 
the password policy requirements. Check the minimum password length, password complexity and password 
history requirements.:Set password failed
type dsadd /? for help.


[192]  table 5-1;
Class B network subnet mask 255.240.0.0 should be 255.255.0.0
Class C network subnet mask 255.255.0.0 should be 255.255.255.0

This error appears also in table 5-2 same page.
and on the pages:
page 382 : table 8-9 (even more errors)
page 384 : table 8-10

[192] Table 5-2;
The bit lengths listed do not match the subnet masks for class B and C 
networks.

(199) last paragraph;
the utility mentioned should be named pathping instead of pingpath (correctly spelled on the next page)

[215] 5th paragraph;
"Reserved addresses cannot be part of an excluded IP address range."

"http://technet2.microsoft.com/windowsserver/en/library/ab8ae112-34c5-49b5-9795-155d89035f0d1033.mspx?
mfr=true"

"You can create reservations using any IP address in the scope's address range, even if the IP address is 
also within an exclusion range. Because of this design, when the 80/20 rule is implemented and all 
addresses in the scope are excluded (80% at one server, 20% at the other), reservations still function 
properly."

(221) last paragraph;
"when DHCP clients lose access to resources or are unable to establish clients,[...]"

'clients' should read 'connections'

(226) bullet point 7;
"...enter the alternate the DNS suffix..." unnecessary 'the'

"as shown in the righthand dialog box" the righthand dialog doesn't show the alternative dns suffix 
entered.

(227) topmost paragraph;
"Normally, the FQDN is the computer's name combined with the name of which the computer is a member." the 
second name should read "domain" or "name of the domain"

(242) last section;
"Configuring zone transfers. Using the Zones tab[...]" the name of the tab should be "Zone Transfers"

[305] table 6-1.;
"Class C 192.168.0.0/255.255.0.0" is in fact a class B subnet

{306} Configuring APIPA part;
"IP addresses in the range 69.254.0.1 to 169.254.255.254 with a subnet mask of 255.255.0.0" the range 
should be "169.254.0.1 to 169.254.255.254"

[393] 6th paragraph;
pathping listed as pingpath. This occurs several times throughout the book.