Skip to main content

List the Impact Level of all PowerShell Commands

By

I took a question fom an IT Professional who needed to know the Impact Level of various PowerShell commands.  The Impact Level works with the  variable $ConfirmPreference.  If a cmdlets Impact Level is equal to or higher than $ConfirmPreference , the user will be prompted to confirm the operation before proceeding. 

Cmdlets and functions store this information in two different places.  For a cmdlet, it is stored in the metadata for the cmdlet. For a function, it is stored in line 2 of the functions scriptblock.  The code below will examine all cmdlets and functions and let you know the impact level of each, if once exists.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

# Check all cmdelts

$Cmdlet = Get-Command -CommandType cmdlet |

    ForEach-Object {

    Try

    {

        $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={$_.ImplementingType.GetCustomAttributes($True).confirmimpact}}

    }

    Catch

    {

            $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={"Unknown"}}

    }

    }

 

#Check all functoins

$Function = Get-Command -CommandType Function |

    ForEach-Object {

   

        $C = $_.Definition.Split("`n")

        If ($C[1] -like "*ConfirmImpact='High'*")

        {

            $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={"High"}}

        }

        ElseIf ($C[1] -like "*ConfirmImpact='Medium'*")

        {

            $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={"High"}}

        }

        ElseIf ($C[1] -like "*ConfirmImpact='Low'*")

        {

            $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={"Low"}}

        }

         Else

        {

            $_ | Select-Object -Property @{N = "Command";E={$_.Name}},

            @{N="Impact";E={""}}

        }

    }

 

# Combine and sort the results.

$Cmdlet += $Function

$Cmdlet | Sort-Object -Property command

Labels:

Comments

Tahir Hassan said…
Thank you for the information. I wrote a function "Get-ConfirmImpact" that is based on your code:

http://tahirhassan.blogspot.co.uk/2017/01/powershell-get-confirmimpact-function.html
January 21, 2017 at 4:49 AM
Post a Comment

Popular posts from this blog

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

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