Introduction to Scripting
This is a good book to introduce an experienced IT technician into the world of VBScript. With script, you can manage the computers on your network with less work. However, do keep in mind that you have to know how to use VBScript. And, to be honest, so far it has not been easy for me. But it is worthwhile to learn because this is a skill that any aspiring network administrator will need to learn. And this book does a credible job of introducing you to scripts.
Excellent reference for the IT professional
Like most reference books from MS Press, this is the Swiss Army Knife for the professional developer and systems administrator. Everything is presented in a clear and concise manner which is easy to follow. There are many examples which can easily be adapted to your needs.
Good resource for script samples
This book does a pretty good job of starting you out in Windows scripting. I purchased it because I am a Windows server administrator and it looked like it would help - and it did. It has to be said that the entire text of the book is on Microsoft's web site in the Technet Scriptcenter, but sometimes you want the paper in your hands as well. Another recommendation is Advanced VBScript for Microsoft Windows Administrators (also MS Press, ISBN 0735622442) if you are looking for some goodies for Windows admin like me.
Arrogant behemoth achieves new level of smug conceit
Now I remember (again) why I hate Microsoft. First, they come up with a terminology all their own, then they pretend that's the standard. Like a "scripting host". Because Microsoft has a product (an add on to fix the shortcomings of DOS, as I see it) called "Windows Scripting Host", suddenly scripting hosts are standard teminology. I don't know about you, but to me a host is a machine on a network, usually a server of some kind. No, to Microsoft the Unix Boune shell is a scripting host!
The kicker is, even though they are promugating inferior products, simply by virtue of their marketing inertia, the products are sucessful and aided by all the third party software developers, consultants and writers/reviewers who bow at the altar of corporate myopia -- usually becaus eth products cannot stand on their own. But this book makes no attempt to give an overview of how everything fits together: VBScript, WSH, WMI, Active Directory, etc., etc.
This book is so inane, it doesn't even explain how to run the examples it is providing, until much later in the book (as another reviewer thankfully pointed out: chapter 3). This chapter, by the way, is written in the same style as the rest of the book: it sets up a straw man then argues against that. For example, in the first chapter the book makes the idiotic point that people hate scripts and think they are difficult. Who are they talking about? In chapter 3 they explain how difficult it is to use cmd.exe and how WSH is so much better. Who cares? Just explain what WSH does, period. My thinking is that the authors probably bashed cmd.exe but that was censored by corporate.
I only use Microsoft because I have to. But I am still hoping against all odds that Linux and Mac put them out of business. Read this book only if your have to. Everything is there, just mixed up and convoluted like the Windows OS itself.
An Excellent start on my scripting education
I'm now up to Chaper 17 (of 18) and have read, highlighted and annotated my through the book. I've learned a tremendous amount, and have impressed my boss and coworkers with the great scripts I've been able tp put together with the aid of this book.
Pros: Great in depth coverage of of many topics.
Cons: It helps that I've had some minimal programming experience in college, but without ANY programming experience, this might not be the book to start with.
I'm moving on to Advanced VBScript for Microsoft Windows Administrators Next.
http://www.amazon.com/gp/product/0735622442/qid=1143080820/sr=2-1/ref=pd_bbs_b_2_1/002-6942852-0115207?s=books&v=glance&n=283155