Skip to main content

Active Directory Cookbook 3rd Edition

just wrote a short review about active directory cookbook, 3rd edition. this is one of the most useful books in my library.
Originally submitted at O'Reilly

When you need practical hands-on support for Active Directory, the updated edition of this Cookbook provides quick solutions to more than 300 problems you might encounter when deploying, administering, and automating Microsoft's network directory service. You'll find recipes for the Lightwe...


Fan of the Series


5out of 5
Pros: Easy to understand, Well-written, Helpful examples, Accurate, Concise
Best Uses: Intermediate, Expert
Describe Yourself: Sys Admin
I became a fan of the series when Robbie Allen released the very first one. Since then, I've been hooked. It's amazing how the book has developed over time to become the monstrosity that it is today. It's enormous, weighing in at over 1000 pages. Though the true value is in all the "recipes" in the book, I really enjoy all the background material that each section provides.

Each topic has:
  • Problem - the task you need to perform
  • Solution - how to perform it
  • Discussion - additional information about the topic

It's great to have a reference that succinctly defines the task and the solution without having to read gobs of pages. It's not just limited to scripting as the name may imply. Most solutions are defined for scripting (vbscript, powershell, command shell), however, often times you'll find the gui (graphical user interface) equivalent of how to achieve the task.

Laura Hunter is a great author and well-respected MVP in the Active Directory space. All of the contributing authors from the past editions are tops in their field and sources of information I have relied on in the past and will continue to do so for as long as I support Active Directory.

It's time I give up my 2nd Edition Cookbook and make room for this one on my reference shelf. Valuable book!

Comments

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …