Skip to main content

How to list all PowerShell Commands with a ComputerName Parameter

By

Well, today was a fun one in class.  I completely forgot my own code to enumerate every command that has a ComputerName parameter in it.  It is no secrete that I use this blog for my own repository, so here is the code.

1

Get-Command | Where {$_.Parameters.Keys -eq "Computername"}

First I execute the cmdlet Get-Command.  Remember, the number of commands that are returned will vary depending on what you have installed on your system.  Each command is an object.  Take a look at this example.

PS C:\> $C = Get-Command -Name Invoke-Command

 

PS C:\> $C | GM

 

 

   TypeName: System.Management.Automation.CmdletInfo

 

Name                MemberType     Definition                                 

----                ----------     ----------                                 

Equals              Method         bool Equals(System.Object obj)             

GetHashCode         Method         int GetHashCode()                          

GetType             Method         type GetType()                             

ResolveParameter    Method         System.Management.Automation.ParameterMet...

ToString            Method         string ToString()                          

CommandType         Property       System.Management.Automation.CommandTypes...

DefaultParameterSet Property       string DefaultParameterSet {get;}          

Definition          Property       string Definition {get;}                   

HelpFile            Property       string HelpFile {get;}                     

ImplementingType    Property       type ImplementingType {get;}               

Module              Property       psmoduleinfo Module {get;}                 

ModuleName          Property       string ModuleName {get;}                   

Name                Property       string Name {get;}                         

Noun                Property       string Noun {get;}                         

Options             Property       System.Management.Automation.ScopedItemOp...

OutputType          Property       System.Collections.ObjectModel.ReadOnlyCo...

Parameters          Property       System.Collections.Generic.Dictionary[str...

ParameterSets       Property       System.Collections.ObjectModel.ReadOnlyCo...

PSSnapIn            Property       System.Management.Automation.PSSnapInInfo...

RemotingCapability  Property       System.Management.Automation.RemotingCapa...

Verb                Property       string Verb {get;}                         

Visibility          Property       System.Management.Automation.SessionState...

DLL                 ScriptProperty System.Object DLL {get=$this.Implementing...

HelpUri             ScriptProperty System.Object HelpUri {get=$oldProgressPr...

 

 

Notice that there is a Parameters property.  This property is an object with a Keys parameter.  It is in this parameter that you will find a list of all parameter names for this command.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

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

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