Windows PowerShell -Filter Parameter get-WmiObject

Windows PowerShell -Filter Parameter get-WmiObject
Get-Help Get-WmiObject -full
Get-ChildItem -Path "C:\Windows\System32\" -filter *.dll

PowerShell Get-WmiObject Filter
Get-WmiObject -class Win32_NetworkAdapterConfiguration -Filter "IpEnabled = 'True' " | 
Format-Table IPAddress, DefaultIPGateway, MACAddress -auto

c)  PowerShell Where-Object for Comparison with Above -Filter

# PowerShell Get-WmiObject -Filter replaced with where-Object
Get-WmiObject -class Win32_NetworkAdapterConfiguration |
Where-Object {$_.IpEnabled -eq 'True'} |
Format-Table IPAddress, DefaultIPGateway, MACAddress -auto

Note 7:  Where-Object achieves exactly the same result, but it needs an extra pipe (|).  My problem is remembering the $_. syntax.  I often forget the _ as in: $.IpEnabled.  PowerShell -filter output is shorter than the where-Object clause.

Read full article from Windows PowerShell -Filter Parameter get-WmiObject

Part of the Beginner's Guide to Windows PowerShell

Part of the Beginner’s Guide to Windows PowerShell
for one thing, you can use Windows PowerShell to access WMI and WMI data.

$strComputer = "."

$colItems = get-wmiobject -class "Win32_Process" -namespace "root\cimv2" -computername $strComputer

foreach ($objItem in $colItems) {
      write-host $objItem.Name, $objItem.WorkingSetSize
}

Parameter	Description
-class	The name of the WMI class we want to access. In sample script, that’s Win32_Process.
-namespace	The WMI namespace where the class resides. If the class lives in root\cimv2 then you can leave out the –namespace parameter; that’s because root\cimv2 is the default value.
-computername	The computer we want to connect to. If the –computername parameter is not present then the script will retrieve information from the local machine. Here we’re using the value stored in the variable $strComputer; we could also hard-code in a computer name like so: -computername "atl-dc-01"

$colItems = get-wmiobject -class "StdRegProv" -namespace "root\default" -computername "atl-fs-99"

foreach ($objItem in $colItems) {
      write-host $objItem.Name, $objItem.WorkingSetSize
}

Read full article from Part of the Beginner’s Guide to Windows PowerShell

PowerShell Magazine » Skipping empty CSV objects

Working with CSV files in PowerShell is a common practice. You import the file, loop on its records and you’re good to go. Sometimes however you may find yourself in a situation where you get a file that has blank lines in it, and those lines can break your script. Consider the following CSV content: ## sample.csv ## column1,column2,column3 Value1,Value2,Value3 Value1,Value2,

You might be attempted to do that with:

1 2	Import-Csv sample.csv | Where-Object {$_.column1 -ne '' -and $_.column1 -ne '' -and $_.column1 -ne ''}

But what if each record has 20 properties, or even more? This is where the PSObject property comes to rescue. In a nutshell, PSObject allows us to work with any object in the same way without really knowing its structure. PowerShell wraps the base object in a PSObject and provide us a simplified and consistent view of the object, its methods, properties, and so on. One of the properties of PSObject is Properties, and it gives us a list of properties of the base object.

For our purpose, we can process the properties list and filter out those who have a Value of null.

Import-Csv sample.csv |

Where-Object { ($_.PSObject.Properties | ForEach-Object {$_.Value}) -ne $null} |

Format-List




Read full article from PowerShell Magazine » Skipping empty CSV objects