Skip to main content

How Many ??? is in PowerShell?

By

When I start a PowerShell class, I am often asked “How many cmdlets are there in PowerShell?”  Well, the answer is “That depends.”  Once we start looking at cmdlets, I am often asked “How many parameters does a cmdlet have?”  The answer is “that depends.”  I also get asked “How many modules are there?” Once again, “that depends.”  This is not the answer that paying clients want to here, but it is the truth.

How many cmdlets are there? It depends on what is available to the client/server you are working on. Also, did you add your own modules?

Get-Command | Measure-Object | Select-Object –ExpandProperty Count

How many modules are there?  What technologies are installed on the local client/server?  Again this is a variable that I cannot answer. 

Get-Module –ListAvailable | Measure-Object | Select-Object –ExpandProperty Count

How many parameters are there?  That depends on which cmdlet you are using.  Utilizing the Help system will expose the different parameters that are available to you for individual cmdlets.

To get a total count of them all parameters is a bit more complex.  This code below will help you out with that.  Be forewarned, this might take a while.

$Total = 0

ForEach ($C in (Get-Command))

{

    $Count++

    $Status = (($Count/($Commands.count))*100)

    $ProgHash = @{'Activity' = "Processing Commands"

                  'PercentComplete' = $Status

                  'Status' = "$Status % Completed"}

    Write-Progress @ProgHash

    Try

    {

        $Total += (Get-Command $C -ErrorAction Stop).Parameters |

            Select-Object -ExpandProperty Keys |

            Measure-Object |

            Select-Object -ExpandProperty Count

    }

    Catch

    {

        $Total += 0

    }

 

}

Write-Output $Total

Here are the stats for my client:

Cmdlets: 3837

Modules: 80

Parameters: 95405

Labels:

Comments

Post a Comment

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

By
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
Post a Comment
Read more

Return duplicate values from a collection with PowerShell

By
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
Post a Comment
Read more

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