Skip to main content

Search a PowerShell Module’s Help Files for Key Words

This past week I have been working on a project in Windows Azure and PowerShell.  As I’m learning the Azure platform, I’m coming across the need to be able to find key words in the help files to help me discover the cmdlets that I need.  Here is the command line that I am using.

Get-Command -Module Azure | ForEach-object -process {Get-help $_.name -Detailed} | Select-ObjectProperty Name, Description | Where-Object Description -like "*blob*" | Select-ObjectProperty Name

 

The –Module parameter is used to ensure the Get-Command cmdlet only returns objects from the Azure module.

 

The ForEach-Object cmdlet will cycle through each cmdlet and call the detailed help file for each cmdlet.

 

We can filter some of our data at this point and ask for only the cmdlet’s name and description.

 

Finally, the Where-Object cmdlet is used to look for a pattern.  In this case, I am looking for any help file from the Azure module that has the work “blob” in it.

 

Optionally, I added one more Select-Object filter to give me only the name of the cmdlet.

 

PS C:\> Get-Command -Module Azure |

ForEach-object -process {Get-help $_.name -Detailed} |

Select-Object -Property Name, Description |

Where-Object Description -like "*blob*" |

Select-Object -Property Name

 

Name                                                                                                   ----

Start-AzureStorageBlobCopy

Stop-AzureStorageBlobCopy 

Add-AzureDataDisk

Add-AzureVhd

Get-AzureStorageBlob

Get-AzureStorageBlobContent

Get-AzureStorageBlobCopyState

New-AzureStorageAccount

Remove-AzureDataDisk

Remove-AzureDisk

Remove-AzureStorageBlob

Remove-AzureVMImage

Save-AzureVhd

Set-AzureStorageBlobContent

Start-AzureStorageBlobCopy

Stop-AzureStorageBlobCopy

At this point, I can now look for a verb/noun combination that looks good and investigate the individual help file.

Comments

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?

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

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

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.