Skip to main content

Accessing the Values of Properties

By
We need to be able to access the values of properties to make decisions.  There are multiple ways to do this.
Using Select-Object
PS C:\> Get-Volume | Select-Object -ExpandProperty Size
471855104
366997504
255919648768
255919648768
515895296
116280782848
9694433280

Using dot notation
PS C:\> (Get-Volume).Size
471855104
366997504
255919648768
255919648768
515895296
116280782848
9694433280

Using a variable
PS C:\> $Data = Get-Volume

PS C:\> $Data.Size
471855104
366997504
255919648768
255919648768
515895296
116280782848
9694433280

Using array syntax
PS C:\> $Data[0].Size
471855104

You have access to all information in a property.  Just choose the method that works best for you and your situation. The important thing to remember is that Get-Member shows you the correct property name to use.  Some formatted output changes the property names.
PS C:\> Get-Process | Select-Object -First 1

Handles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id  SI ProcessName                
-------  ------    -----      ----- -----   ------     --  -- -----------                
    106      10     1564       3640    91    73.70   7080   1 ApMsgFwd 

Notice the name of the column CPU(S).  If you try to use it, you will not get good results.
PS C:\> Get-Process | Select-Object -Property "CPU(S)"

CPU(S)
------
      

Using Get-Member you will discover that the correct name of the property is actually CPU.  Now you get the correct results.
PS C:\> Get-Process | Select-Object -Property "CPU"

        CPU
        ---
  73.828125
   46.34375
   52.03125



Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more