Timothy D. Paul said
Firstly a warning, this is the second edition and covers Windows 2003. There is a third edition that covers the newer OS. I bought this book by mistake and it's too big (postage would be too expensive) to return. So buy with care.
This is a big book in terms of pages but the content is less than stellar. Don't expect to find too much on designing AD in real world situations such as integration with networking topologies and devices. Nor expect to find details on integrating AD with other Microsoft technology such as SharePoint. No this cookbook is really an administrator companion, and I think it does a pretty decent job in that but not more.
George Falcon said
Very handy cookbook reference for my office bookshelf. I've used it a number of times, and it's more than paid for itself in expediting regularly-scheduled inquiries of our AD structure here at GEICO HQ.
kc2kth said
Excellent reference if you work with AD on a regular basis either as an admin or a developer. Each "how to" offers methods for manually performing a specific task as well as (where possible) how to automate the task using code. Should be on every Windows admin/developer's desk.
W. Hargraves said
Overall, this is a great book for reference.
There are a number of areas where I think the book falls short - all of the scripts are very hard coded scripts that don't tell you how to do some functions that would make their scripts actually useful (like "pull the list of users with attributes from a tab-delimited file and create them" or something similar, this would make mass creation of users actually useful, instead of "create user1, user2, user3, etc..."). I think that the writers expect you to be a VB expert (or at least close to it) if you're going to actually make the vb scripts useful.
Most of the scripts are "How to use a script to do the same functions that you can already do in AD with ADUC or another MMC", but I think that the most important thing for me about the book is what it inspires me to think of doing. Things that MS doesn't necessarily expect you to do. I'm still not seeing a way to add sidHistory to an object (MS does it with another applet - there is a way...), but there are so many things in the book that just have me thinking about how you can implement changes to an environment that MS says you can't do. What they really mean is "You can't do that with the GUI tools that we provide you".
C. Ross said
I am so glad that this book was recommended to me by a guy I took a class on scripting from. I use this book everyday (almost). I even took it on vacation with me for light reading.
Comments