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

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

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
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