{"id":15331,"date":"2011-03-13T00:01:00","date_gmt":"2011-03-13T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/03\/13\/get-all-methods-and-writable-properties-from-all-wmi-classes\/"},"modified":"2011-03-13T00:01:00","modified_gmt":"2011-03-13T00:01:00","slug":"get-all-methods-and-writable-properties-from-all-wmi-classes","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/get-all-methods-and-writable-properties-from-all-wmi-classes\/","title":{"rendered":"Get All Methods and Writable Properties from All WMI Classes"},"content":{"rendered":"

Summary<\/b>: Use Windows PowerShell to gather all implemented methods and writable properties from all WMI namespaces.<\/p>\n

Weekend Scripter <\/h3>\n

Microsoft Scripting Guy, Ed Wilson, here. It is quiet around here on the weekends. At times, it is extremely quiet. I decided to use the time to make some serious changes to my WMI method and property discovery script I have been working on the previous several days. <\/p>\n

On Thursday<\/a>, I wrote a script that gathers implemented methods from all of the dynamic WMI classes in a single WMI namespace. By default, this WMI namespace is root\\cimv2. On Friday<\/a>, I wrote a script that retrieves all of the writable properties from all of the dynamic WMI classes in a single WMI namespace. On Saturday<\/a>, I combined these two scripts and added the ability to write to a text file. <\/p>\n

Today I thought I would modify yesterday’s script to query all WMI namespaces. Because this can take a rather long time, I also decided to implement a nested progress bar. It is a cool script. It is also rather long; therefore, I uploaded it to the Scripting Guys Script Repository<\/a>. <\/p>\n

The big change involves creating a function that generates a recursive listing of all WMI namespaces on the target computer (by default this is the local computer). A recursive listing is required because of the deeply nested structure that is used by the WMI namespaces. This structure is illustrated in the following graphic.<\/p>\n

\"Image<\/a><\/p>\n

I decided to filter out the root\\directory WMI namespace, in addition to all namespaces below this namespace. The reason is because during my testing, it was taking an extremely long time to complete the enumeration of the classes in those namespaces, and in the end, nothing was showing up that was usable. <\/p>\n

If you want to add it back, I have added a comment that will help you locate the line to remove. The technique of filtering out a namespace is useful anyway, because you may wish to create custom reports and exclude certain namespaces—therefore, it is all good. <\/p>\n

The Get-WmiNamespace<\/b> function is similar to one I wrote for the Windows 7 Resource Kit<\/a>. I added the value “SilentlyContinue” for the ErrorAction<\/i> parameter because you will not always have rights to all WMI namespaces, and I wanted to suppress the errors. The complete text for the Get-WmiNamespace<\/b> function is shown here:<\/p>\n

\n

Function Get-WmiNameSpace<\/span><\/span><\/span><\/p>\n

{<\/span><\/span><\/span><\/p>\n

 <\/span><\/span>Param(<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>$nameSpace = “root”,<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>$computer = “localhost”<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>)<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>Get-WmiObject -class __NameSpace -computer $computer `<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>-namespace $namespace -ErrorAction “SilentlyContinue” |<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>Foreach-Object `<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>-Process `<\/span><\/span><\/span><\/span><\/p>\n

   <\/span><\/span>{ <\/span><\/span><\/span><\/span><\/p>\n

     <\/span><\/span>$subns = Join-Path -Path $_.__namespace -ChildPath $_.name<\/span><\/span><\/span><\/span><\/p>\n

     <\/span><\/span>#Following line skips the root\\directory & root\\directory\\LDAP namespaces<\/span><\/span><\/span><\/span><\/p>\n

     <\/span><\/span>if($subns -notmatch ‘directory’) {$subns} <\/span><\/span><\/span><\/span><\/p>\n

     <\/span><\/span>$namespaces += $subns + “`r`n”<\/span><\/span><\/span><\/span><\/p>\n

     <\/span><\/span>Get-WmiNameSpace -namespace $subNS -computer $computer<\/span><\/span><\/span><\/span><\/p>\n

   <\/span><\/span>} <\/span><\/span><\/span><\/span><\/p>\n

} #end Get-WmiNameSpace<\/span><\/span><\/span><\/p><\/blockquote>\n

The entry point to the script sees me setting the value “SilentlyContinue” to the global $ErrorActionPreference <\/b><\/i>variable. I do this to suppress any errors that may occur while running the script. Obviously, when writing the script one wants to see the errors, and indeed most of the time I want to see the errors. Therefore, I set it back to the default value of “Continue” at the bottom of the script. <\/p>\n

Next, I set a path for the log file, display a message that states I am gathering WMI namespaces, and I call the Get-WMiNamespace<\/b> function. After the collection of namespaces is generated, I initialize the $j<\/i> variable that is used to keep track of my progress through the WMI namespaces. This portion of the script is shown here.<\/p>\n

\n

$ErrorActionPreference = “SilentlyContinue”<\/p>\n

$ErrorActionPreference = “SilentlyContinue”<\/span><\/span><\/span><\/p>\n

$path = “C:\\fso\\WMiMethodsAndPropertiesInAllNamespaces.txt”<\/span><\/span><\/span><\/p>\n

“Collecting WMI Namespaces”<\/span><\/span><\/span><\/p>\n

$CollectionOfNamespaces = Get-WmiNameSpace<\/span><\/span><\/span><\/p>\n

$j = 0<\/span><\/span><\/span><\/p>\n<\/blockquote>\n

I use the ForEach<\/i> statement to walk through the collection of WMI namespaces. I now write to the log file by using the redirection arrow. This first message provides the name of the WMI namespace. Next, I use the Write-Progress<\/b> cmdlet to track my progress through the WMI namespaces. <\/p>\n

For information about using the Write-Progress<\/b> cmdlet to create a nested progress bar, see the Provide Progress for Your Script with a PowerShell Cmdlet<\/a> Hey, Scripting Guy! blog. Basic information about the Write-Progress<\/b> cmdlet appears in the Add a Progress Bar to Your PowerShell Script<\/a> Hey, Scripting Guy! blog. <\/p>\n

This portion of the script is shown here.<\/p>\n

\n

Foreach($namespace in $collectionOfNamespaces)<\/span><\/span><\/span><\/p>\n

{<\/span><\/span><\/span><\/p>\n

 <\/span><\/span>“Checking $namespace” >> $path<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>Write-Progress -Activity “Inspecting Properties and Methods” `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-Status “Checking namespace $($namespace)” `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-PercentComplete ($j \/ $CollectionOfNamespaces.Length*100) -Id 1 `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-ErrorAction “SilentlyContinue”<\/span><\/span><\/span><\/span><\/p>\n<\/blockquote>\n

Now I initialize the $I<\/i> variable, which is used as a counter to mark progress through the collection of WMI classes. I then retrieve a listing of all the WMI classes in the namespace, and I store the resulting classes in the $classes<\/i> variable. As I walk through the collection of classes, I use a nested Write-Progress<\/b> bar to mark my progress through the collection of classes. I then call the Get-WMIClassMethods<\/b> function and the Get-WmiClassProperties<\/b> function and clean everything up. This portion of the script is shown here.<\/p>\n

\n

$i = 0<\/span><\/span><\/span><\/p>\n

$classes = Get-WmiObject -List -Namespace $namespace -EA “SilentlyContinue”<\/span><\/span><\/span><\/p>\n

Foreach($class in $classes)<\/span><\/span><\/span><\/p>\n

 <\/span><\/span>{<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>Write-Progress -Activity “Inspecting Properties and Methods” `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-Status “Checking $($class.name)” `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-PercentComplete ($i \/ $classes.count*100) -ErrorAction “SilentlyContinue” `<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>-ParentId 1<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>Get-WmiClassMethods -class $class >>$path<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>Get-WmiClassProperties -class $class >>$path<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>$i++<\/span><\/span><\/span><\/span><\/p>\n

 <\/span><\/span>} #end foreach class<\/span><\/span><\/span><\/span><\/p>\n

  <\/span><\/span>$j++<\/span><\/span><\/span><\/span><\/p>\n

} #end foreach namespace<\/span><\/span><\/span><\/p>\n

$ErrorActionPreference = “Continue”<\/span><\/span><\/span><\/p>\n<\/blockquote>\n

When the script runs, the first thing that appears in the Windows PowerShell ISE display panel (in fact the only thing that appears) is the message that states I am gathering WMI namespaces. This is shown in the following image.<\/p>\n

\"Image<\/a><\/p>\n

After all of the WMI namespaces are gathered, the nested progress bar appears. The top progress bar indicates progress through the namespaces, and the bottom bar indicates the progress through the collection of dynamic WMI classes inside the current namespace. The nested progress bar is shown in the following image.<\/p>\n

\"Image<\/a><\/p>\n

When the script completes its run, the implemented WMI methods and writable properties for each class in each namespace appear in the text file that you specified to the $path<\/i> variable. A copy of my text file is shown in the following image.<\/p>\n

\"Image<\/a><\/p>\n

That is about all there is to exploring WMI for implemented methods and writable properties. Join me tomorrow when I will talk about using a few of our newly discovered writable properties to make useful configuration changes. It is cool, and I am sure you do not want to miss it.<\/p>\n

I 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.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Use Windows PowerShell to gather all implemented methods and writable properties from all WMI namespaces. Weekend Scripter Microsoft Scripting Guy, Ed Wilson, here. It is quiet around here on the weekends. At times, it is extremely quiet. I decided to use the time to make some serious changes to my WMI method and property […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3,4,61,45,6],"class_list":["post-15331","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-scripting-guy","tag-scripting-techniques","tag-weekend-scripter","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

Summary: Use Windows PowerShell to gather all implemented methods and writable properties from all WMI namespaces. Weekend Scripter Microsoft Scripting Guy, Ed Wilson, here. It is quiet around here on the weekends. At times, it is extremely quiet. I decided to use the time to make some serious changes to my WMI method and property […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/15331","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\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=15331"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/15331\/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=15331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=15331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=15331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}