Skip to main content

How to Extract all of the Cmdlets used in a Script

How to Extract all of the Cmdlets used in a Script
This idea actually came from a member of my class.  He compiled all of the code that we created over the past week and wanted to know every unique cmdlet that we used.  He was attempting to work with the –Match comparison operator and had a good query.  I thought this was a good idea so I wrote some code to help him out.
This is a good way to inventory your cmdlets so you can find out which modules you need to have available when running your code on other nodes.

# How to extract all of the unique cmdlets used in a script.

Function Get-UsedCommands
{
Param (
    [Switch]
    $Count,

    [String]
    $Path
)

    Try
    {

        $Data = Get-Content -Path $Path -ErrorAction Stop
        $Ary = @()
        $Output = @()

        ForEach ($D in $Data)
        {

                $Ary += Select-String "\w+-\w+" -input $D -AllMatches |
                Foreach {$_.matches}

        }

        # Verify that each cmdlet starts with a PowerShell verb.
        # This is to prevent false positives.
        $Verbs = (Get-Verb).Verb
            ForEach ($A in $Ary)
            {
                $Value = ($A.Value).Remove(($A.Value).IndexOf("-"),$A.length-($A.Value).IndexOf("-"))
                If ($Value -in $Verbs)
                {
                    $Output += $A.Value.trim()
                }
            }

        If ($Count)
        {
            $Obj = New-Object -TypeName PSObject -Property @{
                Count = ($Output | Sort-Object -Unique | Measure-Object).Count
                }
            Write-Output $Obj
        }
        Else {$Output | Sort-Object -Unique}
    }
    Catch
    {Write-Warning "File not found"}

<#
.SYNOPSIS
Reads a file and gets all of the cmdlets used.

.DESCRIPTION
Reads the contents of a file and either displays all of the unique
cmdlets used in the file or counts them.  Only cmdlets that use
approved PowerShell verbs will be counted.

.PARAMETER Count
Returns the number of unique PowerShell Commands used.

.PARAMETER Path
The path to the script.

.Example
Get-UsedCommands -Path "E:\One Drive\ChangeUsers.ps1"
Reads the ChangeUsers.ps1 file and returns the unique cmdlets used in that script.

.Example
Get-UsedCommands -Path "E:\One Drive\ChangeUsers.ps1" -Count
Reads the ChangeUsers.ps1 file and counts the unique cmdlets used in that script.

.NOTES
===============================================================================
== Cmdlet: Get-UsedCommands                                                  ==
== Author: Jason A. Yoder                                                    ==
== Company: MCTExpert of Arizona                                             ==
== Date: January 15, 2016                                                    ==
== Copyright: All rights reserved.                                           ==
== Version: 1.0.0.0                                                          ==
== Legal: The user assumes all responsibility and liability for the usage of ==
== this PowerShell code.  MCTExpert of Arizona, Its officers, shareholders,  ==
== owners, and their relatives are not liable for any damages.  As with all  ==
== code, review it and understand it prior to usage.  It is recommended that ==
== this code be fully tested and validated in a test environment prior to    ==
== usage in a production environment.                                        ==
==                                                                           ==
== Does this code make changes: NO                                           ==
===============================================================================
#>

}


Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

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.

Set up your Environment to utilize Invoke-GPUpdate

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...

Where did a User’s Account Get Locked Out?

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...