Some errata in Chapters 1-4

[schell77]

P. 17: "Windows XP requires the .NET Framework to run properly." This should say "GPMC requires..."
P. 37: "In Chapter 3, I'll demonstrate..." should refer to Chapter 2.
P. 41: "In Chapter 3, I'll show you the GPMC way" should refer to Chapter 2.
P. 42: "In Chapter 3, you'll see an alternate way to allow users to create GPOs." Again, this should refer to Chapter 2.
P. 49: In the discussion of the Force Classic Control Panel Style GPO setting, we read "Once this policy setting is disabled, the policy forces Windows XP users to use the Control Panel in the new task-based style." My experience in SP1 and SP2 is that Disable just reverts to the user preference.
P. 119, first sentence: the phrase "after logging on to the workstation" is repeated within the sentence.
P. 166 under The \Applications Folder: "These files are used in conjunction with deployed with..."
P. 167, first paragraph: "Set up Folder Redirection as described in Chapter 10." Should read Chapter 9.
P. 174: "Today, we know Group Policy by the 13 function groups described in the Introduction." They aren't described in the Introduction though.
P. 201: The path to USERENV.LOG is given as "\winnt\debug\usermode". In Windows XP/2003 it's "\windows\debug\UserMode" by default

[schell77]

On p. 93 (and in Microsoft's WS2003 documentation) we read that GPO links are not backed up and restored by the GPMC Backup feature (or by the backup scripts provided with GPMC). It's true that the links are not restored, but the backup includes (in the gpreport.xml file) the links, status (enabled or not) and Enforced attribute setting for the GPO at the time of backup. You can view this from the GPMC, though you'll have to manually restore it after restoring the GPO.

Very true. Thanks for the feedback !

[AdamV]

a minor one: page 36 sidebar on default OU for new users and computers refers to MS KB 324929 which is in fact 324949

Jeremy - On a general note, have you though about concolidating errata which you have checked and accepted and publishing this somewhere eg as a .pdf file.

www.cwnp.com do this for their study guides and I found this really useful. They cover things like simple typos, spelling errors, wrong references, through rewording for clarification, and even "real world" changes to technology which directly affect how true something is (like a new standard is now agreed, no longer just in progress etc.).

Obviously there is a limit for things which are real changes like a new application (WSUS over SUS) or major additions like added policy settings in a service pack, but it would be nice ot be able to buy the book, make amends from an errata sheet and know it is as up to date / correct as possible.

SYBEX's web site is the official home of errata for the second edition (the one you hold now.)

However, I've just completed a 3rd edition and it should be out sometime in August... with all errata fixed and lots of little things cleaned up, expanded upon and made better.

Hope you like it !