Errata

Active Directory Cookbook

Errata for Active Directory Cookbook

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Other Digital Version I
first paragraph

The link http://www.rallenhome.com/books/adcookbook2 is broken

 Zaid Arafeh  Aug 21, 2011 
Printed Page 12
Code for this book

URL link to the code: "http://techtask.com/code/viewbook/2" is broken.

 PL  Jan 28, 2012 
Printed Page 249
1st paragraph, command line

When running the "for" command as written (substituting the actual OU and domain names), I receive the error message, "The system cannot find the file 1."

 Anonymous  Nov 10, 2009 
Printed Page 249
First example on the page

An anonymous user noted that < When running the "for" command as written (substituting the actual OU and domain names), I receive the error message, "The system cannot find the file 1." > The problem is that the wrong switch is used in the example, /F instead of /L. Try instead:

for /L %i in (1,1,1000) do dsadd user cn=User%i,ou=bulk,dc=adatum,
dc=com -pwd User%i

 Joe Morris  Dec 22, 2009 
Printed Page 314
3rd Paragraph

The PowerShell example for protecting a user from accidental deletion gives Everyone permission to delete the user!

The Add-QADPermission cmd-let is missing its -Deny argument.

I'm also not convinced, from experimentation, that simply adding -Deny results in the protection described under "Discussion" and can still accidentally (well intentionally in this case) delete the user as Administrator.

Can you suggest a PowerShell command that works?

[I'm still on Windows Server 2003 Standard]

 Charles Stevenson  Jul 16, 2010 
Printed Page 758
item number 12

wrong: "oy, sor180"
correct: "180"

I 'm rather sure of that. The wrong string fails silently, the correct string causes the two informational event id 's 700 and 701 (see "Directory Service Log").

 Andreas Ertle  Aug 19, 2012