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

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the