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

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.