This book helps developers and system administrators understand Windows Management Instrumentation (WMI). For the first time the Windows Operating System employs a unified technology to represent software and hardware management. The power of WMI in systems management stretches to virtually every piece of software and hardware. So regardless of whether you're a team leader, software engineer or system administrator, WMI will probably affect you.

After the introduction, the book starts covering where management technologies/frameworks were (SNMP and DMI) and roughly how they worked and the differences between them. This leads to the reasons why the Desktop Management Task Force (DMTF) defined a protocol/schema called WBEM (Web Based Enterprise Management). Microsoft adopted WBEM and WMI was born. WMI is an implementation of the WBEM standard and it is also consistent with Microsoft's Total Cost of Ownership (TCO) initiative. The book continues to explain how to understand the various class schemas and the WMI tools provided by Microsoft. The class schemas describe virtually every aspect of a network, computer and its operating system together with the installed software. The book then introduces how WMI fits together with all its different building blocks.

From a development point of view, the most important place to start in making your own software/hardware manageable through a standard management environment is learning how to develop a class schema. The book takes a whole two chapters to discuss how to do this.

Accessing the WMI management environment can be achieved a number of ways. The book covers how system administrators can develop script to access and manipulate the management environment. The next part of the book is then focused on how developers can use and access the management environment through both the C++/COM interface and the .net framework. A chapter is also included how application developers can develop their UI management tools for the Microsoft Management Console (MMC). A crucial chapter in the book describes how software and hardware developers can write their own WMI providers. WMI providers are the gateway for developers to expose their own class schema.

Finally, the book covers a very little-known subject of the WMI toolset called Event Tracing. Event Tracing is a very powerful and high performance method of instrumenting applications. It allows applications to expose very detailed information about an operation or task. The operating system uses this technology to expose activity in the Windows kernel, security subsystems and numerous other subsystems.

From the Author

Many applications written for Windows currently don't harness the power of a systems management technology (like WMI); this is what drove us to write this book. We want developers to realize that making an application manageable is a key benefit, especially to system administrators. Once system administrators and IT support departments realize what can be done with WMI, they will start demanding that applications expose WMI management interfaces. Not only will system administrators by happy, but you'll be able to harvest a wealth of information available from WMI when building your own management applications. The other side of the coin apart from making an application manageable is a 'management application'. A management application is a program (like an MMC snap-in) or web interface that can interact with the system to gather, inspect and manipulate the systems functionality or configuration. We also want system administrators to realize what they can do in !

a system equipped with a technology like WMI and how they should go about automating routine tasks. For instance, a system administrator can easily write a script that will identify what Windows service packs have been installed on all the machines in the network.

See all Editorial Reviews