My first reaction to this book is "where was the editor?" Many of my criticisms of this book are forgivable problems for an initial draft, but shouldn't show up in a book on the shelf. For example, on page 10, Mr. Wilkins says:
"Users who decide to hide software by renaming the EXE file will have no luck in their attempt to avoid detection, as the file header won't lie. Files can also be collected and then stored on the site server. (Ouch! I guess noontime game playing is out.)"
This passage has a few problems. First, it's trying to describe a nuance of software inventory that doesn't belong in the introduction. Second, the file collection idea is out of context here. Last, of course, the first person comment about games is not only silly, but in bad taste.
The book, at least the portions I got through before returning it, is filled with things like this. Cute comments can be distracting to a serious reader. Here's another (page 2):
"...SMS works tirelessly in the background, providing administrative support, and to the best of my knowledge, it will not ask for a raise or quit on you suddenly."
Get serious - SMS is simply a product; it doesn't deserve to have personality ascribed to it. These attempts at casual tone are far too overt and serve no purpose.
Another obvious problem is a relatively shallow depth of understanding. How about this quote (page xvii):
"For years, [Novell's] IPX protocol had been the standard in the computer industry."
Right there I question just about everything else in the book, which has the feel of being generated based on other documents rather than real experience. You have to dig to find hard facts, and dig further to find those facts accurately described or applied.
For this book, I'd wait for the second edition if you're looking to actually be an SMS administrator. It may be okay for non-administrators who are interested in the topic, but other titles are sure to give more concrete information to admins who are in the trenches day to day.