Skip to main content

How to Read Help Files (Part 7 of 7)

By
This is it!  The last in this series on how to read PowerShell Help Files.

Help files are available for more than just cmdlets.  PowerShell actually has an entire book of material to help you learn PowerShell built it.  Type this command:
Get-Help About_*

What you see are help files about various aspects of using PowerShell.  You will see help on programming constructs, PowerShell features, and different elements of the syntax. 
The help concerning programming such as About_IF and About_Switch start off very basic and adds in additional elements as you go.  I’ve used the About files many times to solve problems and discover why technologies are not working.

You also have help files for the PowerShell Providers.  The PSProviders give you easy access to data that would otherwise be difficult to access, such as the registry.  To see all of your PSProviders:

Get-PSProvider

PS C:\> Get-PSProvider

Name                 Capabilities                            Drives                                                             
----                 ------------                            ------                                                              
Registry             ShouldProcess, Transactions             {HKLM, HKCU}                                                       
Alias                ShouldProcess                           {Alias}                                                            
Environment          ShouldProcess                           {Env}                                                              
FileSystem           Filter, ShouldProcess, Credentials      {C, D, E}                                                          
Function             ShouldProcess                           {Function}                                                         
Variable             ShouldProcess                           {Variable}                                                          
Certificate          ShouldProcess                           {Cert}                                                             
WSMan                Credentials                             {WSMan}                                                            


To get help on each provider, just ask for it by name.  For example: Get-Help Registry or Get-Help FileSystem.

That is it on reading the Help Files.  I encourage you to invest in reading the help files for cmdlets as you start using them.  This initial investment will slow you down at first, but it will pay in dividends later.  Not only in saving you time because you know how to use a cmdlet, but also in extra coding.  One of the coding errors that my PowerShell students make is they write a lot of extra code to do something that is already built into a cmdlet.  By investing in reading the help files up front, you will have to code less and produce your scripts faster and more efficiently.
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

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

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