{"id":8761,"date":"2012-07-10T00:01:00","date_gmt":"2012-07-10T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2012\/07\/10\/three-easy-ways-to-use-powershell-and-wql-to-get-wmi-data\/"},"modified":"2012-07-10T00:01:00","modified_gmt":"2012-07-10T00:01:00","slug":"three-easy-ways-to-use-powershell-and-wql-to-get-wmi-data","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/three-easy-ways-to-use-powershell-and-wql-to-get-wmi-data\/","title":{"rendered":"Three Easy Ways to Use PowerShell and WQL to Get WMI Data"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, talks about using WMI Query Language and Windows PowerShell to get WMI data.\n\"Hey, Hey, Scripting Guy! What is WQL? It sounds like SQL, but that does not always mean very much. I mean, General Electric and General Motors sound alike, but they do not have much in common. So back to my question, do you know what WQL is?\n—WS\n\"Hey, Hello WS,\nMicrosoft Scripting Guy, Ed Wilson, is here. Things are all in a flutter here in Charlotte, North Carolina in the United States. Our weather has been abysmal. It has been hovering around 105 degrees Fahrenheit (40.5 degrees Celsius, according to my conversion module<\/a>). With all this heat, we began dreaming of cool places, and so we booked a trip to Germany. Unfortunately, it will not be until November, but at least we will escape the heat and get a chance to see many of our Windows PowerShell friends who we have met over the years and those who we want to meet. We already have three dates lined up in some of our favorite cities. Tonight, the best we can do is go out for dinner and a movie with Brian (one of our Charlotte Windows PowerShell User Group friends).\nWS, of course I know what WQL is—I wrote the book on WMI: Microsoft Windows Scripting with WMI: Self-Paced Learning Guide<\/a>. I am also contributing a chapter to a new book about Windows PowerShell and SQL Server 2012 written by Laerte Junior, Bob Beachumin, and Mark Broadbent.<\/p>\n

WMI Query Language<\/h2>\n

Here is one of those “bad news” things. WQL is WMI Query Language. WMI stands for Windows Management Instrumentation. So one would think that WQL really is Windows Management Instrumentation Query Language; but it probably is not. There is documentation on MSDN, for example, WQL (SQL for WMI)<\/a>, but it is more or less COM based, and while it is comprehensive, it is more extensive than a typical Net Admin or IT Pro would need to do. The basic WQL statements that you need to know are Select<\/b>, <\/i>From<\/b>, <\/i>and Where<\/b>. <\/i><\/p>\n

Using the Select statement<\/h2>\n

A typical WMI query begins by using the Select<\/b> <\/i>statement to choose everything or only a few properties from a WMI class. To choose all properties from a WMI class, you use the asterisk (“*”). After you have selected the properties (one or more properties, or all of them), you use the From<\/b> <\/i>keyword to list which WMI class to query. The following script creates a WQL query that chooses all properties from the Win32_Bios WMI class:<\/p>\n

$query = “Select * from Win32_Bios”\nTo choose a single property from the WMI class, you place the property name after the Select<\/b> keyword and before the From<\/b> <\/i>keyword. In the following query, only the name of the BIOS is selected from the Win32_Bios WMI class.<\/p>\n

$queryName = “Select Name from Win32_Bios”\nIf you want to select more than one property, you separate the property names by commas. Therefore, the following WMI query chooses the name and the version from the Win32_Bios WMI class.<\/p>\n

$queryNameVersion = “Select name, version from WIn32_Bios”<\/p>\n

Using the WQL query<\/h2>\n

So how do you use the WQL query to retrieve information from a system? In Windows PowerShell 2.0, there are two main ways to do this. The first is to use the Get-WmiObject<\/b> cmdlet, and the second is to use the [wmisearcher] type accelerator. The [wmisearcher] type accelerator creates a ManagementObjectSearcher<\/b> class. The ManagementObjectSearcher class<\/a> is documented on MSDN, but the thing you really need to know how to use is the Get<\/b> <\/i>method. This will be discussed later in this section. In Windows PowerShell 3.0, the CIM cmdlets also accept a WQL query. I will talk about using the CIM cmdlets at a later date.<\/p>\n

Query by using the Get-WmiObject cmdlet<\/h3>\n

The first way is to use the WQL query with the Get-WmiObject<\/b> cmdlet. To do this, you use the Query <\/i>parameter. The command is shown here:<\/p>\n

PS C:> $query = “Select * from Win32_Bios”<\/p>\n

PS C:> Get-WmiObject -Query $query<\/p>\n

SMBIOSBIOSVersion : 8BET56WW (1.36 )<\/p>\n

Manufacturer      : LENOVO<\/p>\n

Name              : Default System BIOS<\/p>\n

SerialNumber      : R9FPY3P<\/p>\n

Version           : LENOVO – 1360\nLet’s use our other queries to see how they fare. First, select only the name of the bios as shown here.<\/p>\n

PS C:> $queryName = “Select Name from Win32_Bios”<\/p>\n

PS C:> Get-WmiObject -Query $queryName<\/p>\n

 <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : Win32_BIOS<\/p>\n

__SUPERCLASS     :<\/p>\n

__DYNASTY        :<\/p>\n

__RELPATH        :<\/p>\n

__PROPERTY_COUNT : 1<\/p>\n

__DERIVATION     : {}<\/p>\n

__SERVER         :<\/p>\n

__NAMESPACE      :<\/p>\n

__PATH           :<\/p>\n

Name             : Default System BIOS<\/p>\n

Now, let’s choose the name and version query and use it.<\/p>\n

PS C:> $queryNameVersion = “Select name, version from WIn32_Bios”<\/p>\n

PS C:> Get-WmiObject -Query $queryNameVersion<\/p>\n

 <\/p>\n

__GENUS          : 2<\/p>\n

__CLASS          : Win32_BIOS<\/p>\n

__SUPERCLASS     :<\/p>\n

__DYNASTY        :<\/p>\n

__RELPATH        :<\/p>\n

__PROPERTY_COUNT : 2<\/p>\n

__DERIVATION     : {}<\/p>\n

__SERVER         :<\/p>\n

__NAMESPACE      :<\/p>\n

__PATH           :<\/p>\n

Name             : Default System BIOS<\/p>\n

Version          : LENOVO – 1360<\/p>\n

Query by using the [wmisearcher] type accelerator<\/h3>\n

By using the [wmisearcher], you gain easy access to the ManagementObjectSearcher<\/b> .NET Framework class. This provides you not only with the ability to query WMI for information, but also to configure the way that query is conducted. There are three basic steps to using the [wmisearcher] type accelerator.\nJust the steps…<\/b>\nTo use the [wmisearcher] type accelerator<\/p>\n

    \n
  1. Put the WQL query in a variable.<\/li>\n
  2. Use the [wmisearcher] to cast the WQL string into a ManagementObjectSearcher <\/b>object.<\/li>\n
  3. Call the Get<\/b> <\/i>method from the ManagementObjectSearcher<\/b> object.<\/li>\n<\/ol>\n

    This may sound more complicated than it is. In fact, it is very simple. Here is an example of using WQL to return all of the properties from the Win32_Bios<\/b> class.\nNote<\/b>   Not all of the properties display due to the format*XML file that specifies which properties to return.<\/p>\n

    PS C:> $query = “Select * from Win32_Bios”<\/p>\n

    PS C:> $bios = [wmisearcher]$query<\/p>\n

    PS C:> $bios.Get()<\/p>\n

     <\/p>\n

    SMBIOSBIOSVersion : 8BET56WW (1.36 )<\/p>\n

    Manufacturer      : LENOVO<\/p>\n

    Name              : Default System BIOS<\/p>\n

    SerialNumber      : R9FPY3P<\/p>\n

    Version           : LENOVO – 1360\nIn the same way that WQL reduces the properties selected for use with the Get-WmiObject<\/b> cmdlet, the same methodology can be used with the [wmisearcher] type accelerator. In the example shown here, only the Name<\/b> property returns from the query.<\/p>\n

    PS C:> $queryName = “Select Name from Win32_Bios”<\/p>\n

    PS C:> $biosname = [wmisearcher]$queryName<\/p>\n

    PS C:> $biosname.Get()<\/p>\n

     <\/p>\n

    __GENUS          : 2<\/p>\n

    __CLASS          : Win32_BIOS<\/p>\n

    __SUPERCLASS     :<\/p>\n

    __DYNASTY        :<\/p>\n

    __RELPATH        :<\/p>\n

    __PROPERTY_COUNT : 1<\/p>\n

    __DERIVATION     : {}<\/p>\n

    __SERVER         :<\/p>\n

    __NAMESPACE      :<\/p>\n

    __PATH           :<\/p>\n

    Name             : Default System BIOS\nBut, rather than storing the string in a variable, then casting the string into a ManagementObjectSearcher<\/b> type, and then calling the Get<\/b> <\/i>method, you can skip one of the steps and still have decent readability. This works because in the previous example, the WQL string was stored in a variable. The variable was then cast into the ManagementObjectSearcher<\/b> type, and then the method was called. The code shown here skips one of the steps and casts the string directly to the object, and then stores the resulting object in the variable.<\/p>\n

    PS C:> $biosname = [wmisearcher]”Select name from win32_bios”<\/p>\n

    PS C:> $biosname.Get()<\/p>\n

     <\/p>\n

    __GENUS          : 2<\/p>\n

    __CLASS          : Win32_BIOS<\/p>\n

    __SUPERCLASS     :<\/p>\n

    __DYNASTY        :<\/p>\n

    __RELPATH        :<\/p>\n

    __PROPERTY_COUNT : 1<\/p>\n

    __DERIVATION     : {}<\/p>\n

    __SERVER         :<\/p>\n

    __NAMESPACE      :<\/p>\n

    __PATH           :<\/p>\n

    Name             : Default System BIOS\nA more interesting way of doing this (and perhaps a bit more readable) is to leave the WQL string on the right side of the equality operator, and perform the cast to ManagementObjectSearcher<\/b> on the variable. This code is even cleaner, and it allows for easier modification of the WQL query.<\/p>\n

    PS C:> [wmisearcher]$biosname = “Select name from win32_bios”<\/p>\n

    PS C:> $biosname.Get()<\/p>\n

     <\/p>\n

    __GENUS          : 2<\/p>\n

    __CLASS          : Win32_BIOS<\/p>\n

    __SUPERCLASS     :<\/p>\n

    __DYNASTY        :<\/p>\n

    __RELPATH        :<\/p>\n

    __PROPERTY_COUNT : 1<\/p>\n

    __DERIVATION     : {}<\/p>\n

    __SERVER         :<\/p>\n

    __NAMESPACE      :<\/p>\n

    __PATH           :<\/p>\n

    Name             : Default System BIOS\nWe can even perform this query in a single line. This works because the [wmisearcher] casts the WQL string to a ManagementObjectSearcher<\/b>. From that object the Get<\/b> <\/i>method is available. By using the parentheses ()<\/b> to group the cast to the ManagementObjectSearcher<\/b> first, the Get<\/b> <\/i>method becomes available.<\/p>\n

    PS C:> ([wmisearcher]”Select name from win32_bios”).get()<\/p>\n

     <\/p>\n

    __GENUS          : 2<\/p>\n

    __CLASS          : Win32_BIOS<\/p>\n

    __SUPERCLASS     :<\/p>\n

    __DYNASTY        :<\/p>\n

    __RELPATH        :<\/p>\n

    __PROPERTY_COUNT : 1<\/p>\n

    __DERIVATION     : {}<\/p>\n

    __SERVER         :<\/p>\n

    __NAMESPACE      :<\/p>\n

    __PATH           :<\/p>\n

    Name             : Default System BIOS<\/p>\n

    Using the query directly<\/h2>\n

    Of course, you do not have to store your query in a variable. You can type the query directly into the Query <\/i>position in your command. Although this may have advantages in simplicity (you have one command instead of two), it also makes your code more difficult to read. This approach is shown here:<\/p>\n

    PS C:> Get-WmiObject -Query “Select * from win32_bios”<\/p>\n

     <\/p>\n

    SMBIOSBIOSVersion : 8BET56WW (1.36 )<\/p>\n

    Manufacturer      : LENOVO<\/p>\n

    Name              : Default System BIOS<\/p>\n

    SerialNumber      : R9FPY3P<\/p>\n

    Version           : LENOVO – 1360\nWS, that is all there is to using WQL. WMI Week will continue tomorrow when I will talk about limiting information that is returned by the WQL query. I will also talk about all those extra ­­system properties that were returned by WMI when we attempted to limit the properties.\nI invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.\nEd Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":"

    Summary: Microsoft Scripting Guy, Ed Wilson, talks about using WMI Query Language and Windows PowerShell to get WMI data. Hey, Scripting Guy! What is WQL? It sounds like SQL, but that does not always mean very much. I mean, General Electric and General Motors sound alike, but they do not have much in common. So […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3,4,45,6],"class_list":["post-8761","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

    Summary: Microsoft Scripting Guy, Ed Wilson, talks about using WMI Query Language and Windows PowerShell to get WMI data. Hey, Scripting Guy! What is WQL? It sounds like SQL, but that does not always mean very much. I mean, General Electric and General Motors sound alike, but they do not have much in common. So […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/8761","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=8761"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/8761\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=8761"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=8761"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=8761"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}