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

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

Set up your Environment to utilize Invoke-GPUpdate

By
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...
Post a Comment
Read more