Skip to main content

Watch those Verbs!

A good question came up in class today.  We were working with the registry and a student needed to know how to change the value of a registry property using New-PropertyItem.  Well, we can’t exactly do that.  Remember that PowerShell has different verbs that describe the intent of the cmdlet.  The Approved Verbs for Windows PowerShell list these verbs.

  • New creates
  • Set changes
  • Remove destroys

The verbs are there to help us find what we need.  For example, what if I need to change an IP address, but I do not know the cmdlet?   Try this:

Get-Command Set-*ip*.  From experience, I knew that there is a good chance that IP would be in the noun.  From the verb list, I know to look for “Set” verbs.  Here is the difference. 

PS C:\> Get-Command set-*ip* | Measure-Object | Select -ExpandProperty Count

20

 

PS C:\> Get-Command *ip* | Measure-Object | Select -ExpandProperty Count

187

The first number, 20, shows how many possible cmdlets returned when you know to use the “Set” verb.  Without it, you would have to look at 187 cmdlets.

Take the time to get to know the PowerShell verbs.  they will help make your PowerShell usage much more efficient and effective.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

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.