Windows Management Instrumentation
Project description
Windows Management Instrumentation (WMI) is Microsoft's implementation of
Web-Based Enterprise Management (WBEM), an industry initiative to provide
a Common Information Model (CIM) for pretty much any information about a
computer system.
The Python WMI module is a lightweight wrapper on top of the pywin32
extensions, and hides some of the messy plumbing needed to get Python to
talk to the WMI API. It's pure Python and should work with any version of
Python from 2.1 onwards (list comprehensions) and any recent version of pywin32.
What's new in 1.0 rc3 - Highlights
* Refactoring of WMI namespace, classes and instances means that WMI classes
are now first-class objects, which makes certain things easier -- such as
watching for changes -- and certain things possible -- such as calling .Create
on a Win32_ScheduledJob.
* Additions to WMI method signatures including the privileges necessary to
run them and the underlying Win32 API calls which they represent. Simply print
the method as an object for its signature and privs, and look at its provenance
property.
* Module-level connect method (for which wmi is an alias) allows connection
by any valid combination of machine name, username, password, security context
etc. It simply gathers into one function nearly all the parameters previously
available under the WMI () or connect_server () functions. At least in theory,
all previous examples using wmi.WMI (...) should still work.
* Sundry other small fixes, additions and accretions.
Web-Based Enterprise Management (WBEM), an industry initiative to provide
a Common Information Model (CIM) for pretty much any information about a
computer system.
The Python WMI module is a lightweight wrapper on top of the pywin32
extensions, and hides some of the messy plumbing needed to get Python to
talk to the WMI API. It's pure Python and should work with any version of
Python from 2.1 onwards (list comprehensions) and any recent version of pywin32.
What's new in 1.0 rc3 - Highlights
* Refactoring of WMI namespace, classes and instances means that WMI classes
are now first-class objects, which makes certain things easier -- such as
watching for changes -- and certain things possible -- such as calling .Create
on a Win32_ScheduledJob.
* Additions to WMI method signatures including the privileges necessary to
run them and the underlying Win32 API calls which they represent. Simply print
the method as an object for its signature and privs, and look at its provenance
property.
* Module-level connect method (for which wmi is an alias) allows connection
by any valid combination of machine name, username, password, security context
etc. It simply gathers into one function nearly all the parameters previously
available under the WMI () or connect_server () functions. At least in theory,
all previous examples using wmi.WMI (...) should still work.
* Sundry other small fixes, additions and accretions.
