This is my personal blog. The opinions and views I express are my own. The information I provide is on an as-is basis. I make no representations as to accuracy, completeness, currentness, suitability, or validity of any information on this blog and will not be liable for any errors, omissions, or delays in this information or any losses, injuries or damages arising from its use.

PowerShells Get-Command cmdlet explained.

The video below is my maiden voyage on YouTube, I would appreciate a Subscribe, Thumbs up or a Comment on YouTube or here. I plan on producing more Screen-Casts going forward relating to PowerShell, Windows Server 2012R2, Exchange 2013, System Center Configuration Manager 2012, SharePoint 2013, and other things. If you would like to request a topic, contact me via any of the methods below.

Ok… On to Get-Command.

Get-Command is a Core PowerShell CMDLet that is used for discovering cmdlets. The code below is what I used in the video, if you have questions or suggestions Comment below or see the contact info at below

# Get all Modules, Functions, Alias' ...etc 
# available on your computer
Get-Command -all

# Search for all cmdlets that contain Service 
# in the noun portion.
Get-command –noun Service

# Search for all cmdlets that contain Stop 
# in the verb portion
Get-Command -Verb Stop

# You can also use the * character as a wildcard
Get-command –noun *azure*

# Search for everything in a module, 
# in this case the Azure Module
Get-Command -Module Azure

# Search the Azure Module for all cmdlets
Get-Command -Module Azure -CommandType Cmdlet

# Search the Azure module for all Alias'
Get-Command -Module Azure -CommandType Alias

# Search the PowerShell core modules for Functions
Get-Command -Module Microsoft.PowerShell* -CommandType Function

Get-Command Code

Website: www.signalwarrant.com
Twitter: @signalwarrant
Facebook: facebook.com/signalwarrant/
Google +: plus.google.com/113307879414407675617