The book is not bad, but it only handles "simple" stuff, if I dare call any computer administration simple.
People entering server administration should, first off, be those that are already considered power users or geeks by the majority of their coworkers. Such a person will already know the truly simple stuff, have acquired bits and pieces of more advanced knowledge, but need considerable direction on the concepts and issues of server administration. On this latter point the book is, unfortunately, far too sketchy, and some things are, I feel, a bit too sketchy for this sort of audience.
I should point out, too, that the famed Macintosh ease of use is here somewhat of a hindrance. I.e., the Xserve and Mac OS X Server setup is deceptively easy, to the point that bad setups are easy to do. Was Unix administration always intentionally hard, in order to "idiot-proof" it? One has to wonder... Given this problem, the book screams out for an introductory chapter on what issues there are in setting up a server, what possible solutions are, what the implications pro and con of each of these choices are, what setups are prerequisites for others, and so forth. The wet-behind-the-ears administrator could then create a flowchart of needed tasks, which this proposed introductory chapter could then reference for details.
Furthermore, the book's organization leaves much to be desired. I should think that security issues should be set up first, not relegated to a late chapter as in this book. DNS is handled in Chapter 3 I believe, yet there are items with dependencies on DNS that are described in earlier chapters. It would make sense to describe setting up user templates before users are actually set up.
For my part, I've already read the book twice and am now proceeding with my 3rd read-through, taking notes as I'm going as to what I need to do and in what order. I'm also taking notes on the files that will be modified as I'm doing this, so that I can take care to back up their original versions. This kind of information is thankfully in the book but unfortunately not stated up front in each section. This (i.e. "read the book through before starting any work") should appear as an instruction in the first chapter.
As to detail, one example relevant to our own situation (and likely many others') should suffice. Having already set up a web site, we wanted to set up the Xserve so that web requests go to the off-site web service while email is sent to the Xserve. The basics can be accomplished with Apple's GUI tools, but the details have to be done by hand in the text-based configuration files. Granted, books can be bought on DNS and BIND; but I don't really want or need a library of 10-12 books on all aspects of Unix administration.