If you’re a sysadmin in 2020s, PowerShell is a skill you can no longer afford to ignore. Whether you’re automating a complex task, firing off a quick one-liner, or pranking your coworkers, PowerShell should be your go-to scripting language. In fact, two out of two hosts of The PowerShell Podcast agree that PowerShell is the best.
Unfortunately, jumping into a new scripting language can be challenging. To help, here are the top 10 PowerShell commands you should become familiar with on your journey to PowerShell mastery.
Tip: Commands in PowerShell are actually called cmdlets. While they function similarly, cmdlets are unique in that they are .NET classes and typically deliver objects as output.
As the name suggests,
Get-Help is the cmdlet used to interact with PowerShell’s integrated help system. It’s basically the self-help guide to PowerShell and the very first cmdlet you should familiarize yourself with. In fact, chapter 3 of “Learn PowerShell in a Month of Lunches” is dedicated to the
Get-Help cmdlet, and it goes on for 17 pages!
Get-Help provides valuable information about cmdlets, parameters, aliases, etc. It also provides helpful examples to get you started.
Here’s the syntax to use
Get-Help limits the information returned by the command. Add the
-Full parameter to view the entire help documentation about a given cmdlet, including descriptions, examples, and additional notes.
Important: If you are new to PowerShell, you need to update your local help files using the
Update-Help cmdlet. It’s also a good idea to update your PowerShell help files every couple of months to ensure they are current.
Another important PowerShell cmdlet, especially for newcomers, is
Get-Command, without additional parameters, returns all cmdlets, functions, and aliases installed on the computer.
Get-Command is a great way to see what commands you can run. However, by default, this command returns over a thousand results, which can be overwhelming. Thankfully, you can narrow down the results by using filters. For example, if I wanted to see what commands deal with certificates, I could filter for that specifically.
Most cmdlets use common sense names, so filtering is an intuitive way to track down the cmdlet you’re looking for.
One quality that makes PowerShell so versatile is that almost everything in PowerShell is an object consisting of a name, methods, and properties. We can use the
Get-Member cmdlet to inspect these objects.
In this example, I’ve piped the
Get-Date cmdlet to the
Get-Member cmdlet, which returns the object’s attributes. I’ve also added the
-Name *da* filter to narrow down the results, but you can ignore that for now. Let’s break down what’s happening in this example.
First, notice the usage of the pipeline operator.
The pipeline operator sends the results of the preceding command to the following command. In this example, the results from the
Get-Date cmdlet are passed to the
Next, pay attention to the TypeName.
The TypeName is the type of object that the command returns. In this case, the object type is System.DateTime.
Lastly, notice the MemberTypes returned for the object.
MemberTypes is where you’ll identify the methods and properties of an object. Methods are actions you can perform against the object, and properties are the object’s attributes.
Get-Member is an excellent cmdlet, especially for PowerShell beginners, to quickly identify the methods and properties of an object.
Need to save your PowerShell output to a raw text file?
Out-File is the cmdlet you’re looking for.
To use the
Out-File cmdlet, you can either use the piping operator to pass output to it or the
-InputObject parameter to specify the objects to be written to the file.
These commands provide the same results, creating a text file containing the output of the
Get-Process cmdlet. It’s important to note that the information in the text file will be formatted as if sent to the terminal window.
If you need to output your data in a more usable format, you’ll want to export it to a CSV file using the
Export-Csv does what its name implies and exports output to a CSV file. This cmdlet is extremely useful, especially when working with large data sets. However, it’s important to point out that
Export-Csv exports ALL object property values by default, so you’ll want to filter the properties to return using the
Here is the resulting CSV file:
In PowerShell, you'll often need to work with items in containers such as files, certificates, or registries.
Get-ChildItem returns all the items in one or more containers. If you only want to return specific items, you can use filtering to narrow down the results. You can also return items in subdirectories by using the
-Recurse parameter. To limit the depth of the subdirectory search, use the
This example returns all items located in the specified directory.
This example is a bit more complex and returns all TXT files containing the word “taco” in the specified directory and subdirectories.
The results show that this command returned two files, one located in the C:\Temp\Extra subdirectory and one in the C:\Temp directory.
Most of the time, PowerShell output returns to the console window. However, if you need to interact with the output, you can use the
Out-GridView sends output to a grid view GUI window.
Here’s the syntax to use
In this example, I’ve piped the
Get-Service cmdlet to the
Out-GridView cmdlet. The
Out-GridView window automatically opened, containing the
Get-Service command output, allowing me to interact with it.
If we want to take this example even further, we can use the
-PassThru parameter to send multiple items down the pipeline, essentially letting you pick what output you want to pass on. Let’s update this example with the
-PassThru parameter, and we’ll send our selected output to a TXT file.
When we run this command, the
Out-GridView window will open as usual. However, because we used the
-PassThru parameter, we can select the output we want to pipe to the next command.
Hint: Hold the SHIFT key to highlight multiple items, and hold the CTRL key to select individual items. Click OK when you’ve finished selecting items.
Once we’ve made our selection and clicked OK, the output is sent to a text file. We can open the text file to ensure it contains the items we selected.
Invoke-Item cmdlet launches items, including files, pictures, executables, etc. It can also launch more than one item at a time.
Invoke-Item uses the default file association to determine the application to launch with the corresponding file type.
Here is the basic structure of an
This example launches the indicated TXT file in Notepad.exe because of the default application assignment on my computer.
As mentioned above,
Invoke-Item can also be used to open several files at once. This command will open all TXT files in the C:\Temp folder at once.
Foreach loops iterate through a collection of items, performing actions against them.
Foreach loops are a little more complex than the other commands we’ve covered so far. However,
foreach loops become increasingly crucial as you dive into more advanced PowerShell tasks.
Here is the basic format of a
foreach command in PowerShell:
Here’s a simple example of a
foreach command that will identify files in a specified folder that are 0 KB in size.
In this example, we assign the items located at C:\Files\ to the
$files variable. Then, we use the
foreach command to loop through each item in the variable. Next, we’re using an
if statement to determine if the file is equal to 0 KB. If the file is equal to 0 KB, the file is output to the console. The loop repeats until it has processed each item in the collection assigned to the variable
We can check the folder for ourselves to ensure the data returned was accurate.
Oh, and if you’re wondering what code editor I’m using in this example and how I got it to look so rad, I’ve covered how to customize VS Code with PowerShell.
10. If statements
Capping off our top 10 list is another slightly more advanced command. Don’t worry. You were already exposed to it in the previous example and probably didn’t even realize it.
If statements are another extremely useful command in PowerShell.
If statements execute logic based on conditions being met, similar to how people make decisions. For example, if I won the lottery, I would enjoy an early retirement. If not, then I would continue to upload amazing content to the internet. PowerShell can use the same kind of logic.
Here’s what the structure of an
if statement looks like in PowerShell.
When a condition is true, the function executes. If the condition returns false, it bypasses the function and proceeds to process the remainder of the script. For example:
In this example, since the variable
$var equals 42, and the condition is met, the
Write-Host command will execute, and the message will display. If the variable equaled something different, like 24, the condition would return false, and the
Write-Host command would not execute.
Here’s one more example of an
if statement in use. This time, we’ll use the
Get-Date cmdlet and format it to return the month and day. If the date is equal to 12/25, a message will display saying, “Merry Christmas, ya filthy animal.”
If statements are really handy to utilize in your PowerShell scripts and we highlight them even more in their very own dedicated article.
On the path to PowerShell stardom
Like any scripting language, PowerShell can take a bit of getting used to. But Microsoft and the PowerShell team have worked hard to ensure that cmdlets and functionality make sense, especially once you start utilizing PowerShell regularly.
Starting with these easier commands will help you quickly progress into using more advanced commands. Then one day, you’ll become a PowerShell master and may even be invited as a guest onto the The PowerShell Podcast, the most prestigious of all PDQ-hosted PowerShell podcasts.
If you’re looking for more ways to become a sysadmin rockstar at your organization, check out PDQ Deploy and Inventory. Deploy and Inventory will handle all your patch and inventory management needs. Your coworkers will think you’re working extra hard when, in reality, you’re hardly working. Try them out with a 14-day free trial.
Born in the '80s and raised by his NES, Brock quickly fell in love with everything tech. With over 15 years of IT experience, Brock now enjoys the life of luxury as a renowned tech blogger and receiver of many Dundie Awards. In his free time, Brock enjoys adventuring with his wife, kids, and dogs, while dreaming of retirement.